Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
Intent (Augment)
Free macOS desktop workspace for multi-agent work: a Coordinator writes a living spec, Implementor agents run tasks in parallel, a Verifier checks acceptance criteria. Bring your own agents.
www.intentapp.dev/Active
Desktop release v2.234.1 on 2026-10-25 (intent-hq/cloudlands-releases); app source published Apache-2.0 under intent-hq org (created 2026-08-20); augmentcode.com/product/intent redirects to intentapp.dev (checked 2026-10-25)
In Spec-driven development
Where it stands apart
- Where do specs live? the tool's own app, database, or cloud (5% of 19 others)
- What form does it mainly ship in? a standalone app, IDE, or hosted platform (21% of 19 others)
What it shares with most of the community
- Is it actively maintained? active (74% of 19 others)
- How is the main thing licensed? permissive open source (MIT/Apache/BSD) (74% of 19 others)
- How is it mainly sustained? company with a paid product, tier, or ads (50% of 18 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (79% of 19 others)
- Do you need an account to use it? no account (74% of 19 others)
- Who is it for? developers (100% of 19 others)
- What format are specs written in? markdown from templates or free-form (67% of 18 others)
- Which coding agents does it work with? many agents (five or more) (78% of 18 others)
- How is the path from idea to code structured? a fixed sequence of phases (e.g. requirements, design, tasks) (53% of 19 others)
- Does a human approve the spec or plan before code is written? yes, the workflow waits for approval (50% of 18 others)
Not documented
The public sources we read don't say:
- What does it offer teams beyond sharing files in git? (if both, pick the paid product)
Nearest neighbors
- Spec Kitty 75% of 16 shared answers match
- GSD (Get Shit Done) / GSD Core 73% of 15 shared answers match
- Superpowers 69% of 16 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active | source 2026-10-25 |
| How is the main thing licensed? | permissive open source (MIT/Apache/BSD) Apache-2.0 (intent, intentd, cloudlands-fe). | source 2026-10-25 |
| How is it mainly sustained? | company with a paid product, tier, or ads Augment Code product (URL redirects); app is free, Augment sells agent credits. Ownership after open-sourcing unclear. | source 2026-10-25 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes Desktop app plus local daemon; daemon can also run on a remote host. | source 2026-10-25 |
| Do you need an account to use it? | no account Free app; docs say log in to an agent provider (Claude Code, Codex, etc.), not to Augment or Intent. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | none of these (its own format or interface) Specs live in Intent's own workspace. | source 2026-10-26 |
| Once code exists, what is the spec? | a living document kept current alongside the code Spec 'keeps updating as the work evolves'. | source 2026-10-25 |
| After implementation, what built-in step keeps specs and code aligned? (if several, the first that applies) | a step checks code against the spec (tests, review, or verifier) Verifier checks results against acceptance criteria. | source 2026-10-25 |
| What format are specs written in? | markdown from templates or free-form Goal, tasks, acceptance criteria, non-goals. | source 2026-10-25 |
| Where do specs live? | stands apart the tool's own app, database, or cloud Workspace spec in the app; not confirmed whether written to the repo. | source 2026-10-25 |
| Which coding agents does it work with? | many agents (five or more) Claude Code, Codex, Auggie, Antigravity, Grok Build, OpenCode, Pi. | source 2026-10-25 |
| What form does it mainly ship in? | stands apart a standalone app, IDE, or hosted platform | source 2026-10-25 |
| How is the path from idea to code structured? | a fixed sequence of phases (e.g. requirements, design, tasks) Coordinator plan -> approve -> implement -> verify -> review/merge. | source 2026-10-25 |
| Does a human approve the spec or plan before code is written? | yes, the workflow waits for approval Coordinator writes plan, 'you approve'. | source 2026-10-25 |
| By default, once a plan is approved, how is implementation run? | agents run the whole plan with automated review or verification loops | source 2026-10-25 |
| What does it offer teams beyond sharing files in git? (if both, pick the paid product) | Not documented | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/intent-hq/cloudlands-releases/releases · read 2026-10-25
- GitHub · github.com/intent-hq/intent · read 2026-10-25
- Web page · www.augmentcode.com/product/intent · read 2026-10-25
- Web page · www.intentapp.dev/ · read 2026-10-25
- Web page · www.intentapp.dev/docs · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.