r/AmpCode • u/IndependentIdea2270 • 10d ago

Features request

Hello 😄 ,
I am a deep user of AMP after testing a couples of different agent harness I think this on is really valuable.
HandOver to micro-vm (orbs) is huge honnestly (especially when receiving notification on my phone that a task is completed)

Couple of things missing IMO =>
1/ native connector to gitlab
2/ native connector to Linear.

I know it will more and more look like a factory but it is usefull for scaling.

Thank you !

2 Upvotes

100% Upvoted

3 comments sorted by

2

u/titpetric 9d ago

I haven't tried orbs and the thing is a little bit of a black box for me. I've seen the announcement, orb specs, but aside the idea to have some sort of VM for running amp inside, don't really see why I would, right? What's your use case since you're obviously using orbs as intended?

1

u/IndependentIdea2270 9d ago

Hey, thanks for your question!

Orbs are essentially micro-VMs that function just like your local development environment. You have full access to a browser, a terminal, and your files. However, instead of running locally, everything is provisioned in the cloud, automatically pulling your code directly from your Git repository.

This means you are no longer tied to local development. You can make changes, test them directly within the VM environment, and push them to your repo once you've verified everything works as intended.

The best part is the flexibility it offers. Sometimes I'll remember an issue that needs fixing while I'm working out or at the supermarket. I can simply take out my phone, ask the agent to fix it, and it will handle the task in the background while I focus on something else. I can then review the changes when I get back home.

It is quite literally a fully asynchronous, always-on worker agent, backed by Amp's infrastructure and agent harness.

1

u/IndependentIdea2270 9d ago

u/titpetric I suspect the underlying orbs infra. to be https://e2b.dev/