Augment Code
Augment Code – Developer AI for real work
4.6•10 reviews•811 followers
Augment Code – Developer AI for real work
4.6•10 reviews•811 followers
Experience the AI platform that truly understands your codebase. Our developer AI helps teams code faster, make smarter decisions, and unlock collective knowledge. Try free today.
This is the 3rd launch from Augment Code. View more
Intent
Launched this week
Intent is a developer workspace built for agent-driven development. Define a feature as a spec, and a team of agents coordinates the work (from implementation to verification) inside an isolated workspace with built-in code, terminal, and git.
Free
Launch Team
Excited to hunt Intent by Augment Code today.
Intent is a developer workspace where agents coordinate and execute work end-to-end.
This isn’t a coding assistant. It’s an agent-driven development system.
Instead of prompting one agent at a time, you define a spec and a coordinator breaks it into tasks, delegating to specialists (implement, verify, debug, review) running in parallel.
This adds up to:
• Specs that stay alive as work progresses
• Built-in verification loops, not just code generation
• A full workspace (editor, terminal, git)
If you’ve been exploring agentic dev but didn’t want to build the orchestration layer yourself , this is definitely worth a look.
Product Hunt
@curiouskitty Thanks for your question, it’s a good one.
Under the hood, Intent gives each task its own workspace backed by a git worktree + branch, so agents get an isolated checkout but share a single .git history for cheap branching and instant sync. The Coordinator turns your spec into a plan with explicit task dependencies, then runs specialist agents in waves: independent tasks in parallel, dependent ones after predecessors land, all staying aligned via a living spec that updates as work is done. On the back end, Intent has full git workflow built in (branching, commits, PRs, merge) plus auto-rebase/conflict surfacing, so you can stack or fan out branches without becoming the human traffic cop, you just review grouped changes per task/agent and ship.
This looks very promising! Unfortunately, I can't test it on Windows yet.
I've been working with Augment in a WebStorm environment for over a year and I'm very happy with it.
However, I have two concerns regarding this next step:
a) How high will the token consumption be? I'm already using up my developer token allowance manually quite a bit. I usually have to top it up several times a month. If I imagine multiple agents working in parallel, orchestrated by even more agents, my token pool will be empty in just a few hours...?
b) I already have to closely monitor/review the activity of my one integrated agent and guide it in the right direction. Here, too, I see the risk that my incomplete/liquid spec will lead to absurdly high token consumption.
So: I think the idea is great, and I also think it will work very well.
But: Is it still affordable?
@daniel_beuter Thanks for this question. You’re right that using coordinators and subagents can introduce some overhead at first glance and use more tokens. That’s why I prepared a detailed post on how to save as many tokens as possible using Intent! It should really help you understand what kind of workflow you might want to use. Here is the post: https://www.reddit.com/r/AugmentCodeAI/comments/1r6ckev/intent_cost_tips_and_tricks/
Another important point is that when you use coordinators + subagents + a verifier, your first prompt will indeed cost more, but it can save you time and reduce the need for reprompts (so overall you’re saving both time and tokens by not having to ask again). Our verifier agents are there to make sure everything is handled correctly on the first try. Nothing is perfect, but we’ve seen better results with this approach internally.
Otto Radio
Wrote up a post on how our teams collaborate within Intent. We've been able to effectively eliminate the designer/developer handoff. More details on the process, screenshots, etc: https://lukew.com/ff/entry.asp?2148
@tanner_beetge Yes. In Intent, agents are usually hierarchical, not a flat swarm:
A controller agent acts like a tech lead: it understands the main goal, breaks it into subtasks, runs specialist agents, and decides what to accept/merge.
Specialist agents do focused work (code, tests, analysis) and report back, they don’t “vote,” their outputs are checked against the shared spec + workspace + tests/CI, and the controller, the verifier agent (plus the human) has final say.
So they “value” each other’s work through this structure and verification, not by arguing as equal peers.
I like this. It seems very interesting. CLI code understanding and agent-driven development make a lot of sense. I'm just wondering, does it do any browser work? That's where most of my time currently gets sucked going back to the browser and seeing if everything has been implemented okay. I think that would be a great problem to tackle anyways. Love the product, and we'll give it a try. Best of luck.
@bitsandtea We know the pain of switching back and forth between your workspace and browser. That’s why we’ve made it very easy to integrate third-party tools like Playwright. With a simple installation, agents can navigate your app in real time to see if changes worked or if there are any regressions.
You can also use the integrated browser directly in Intent, so you can stay on the same page and handle both coding and testing together.
Congrats on the launch, looks great! As an Augment Code user spending most of the time in Auggie CLI, just wanted to check is there a timeline when this would be available to Linux users, or are there any plans for it?
@mate_ajdukovic Unfortunately, we don’t yet have a timeline for the Windows and Linux versions.