Auggie in NeuroSquadAuggie,with a canvas around it
Run Augment’s CLI in as many cards as you need, each with a real terminal. Its hooks and its own screen tell NeuroSquad when it works, asks or finishes; arrows hand it terminals, browsers and notes; its tokens are counted per card.
Official siteaugmentcode.com/product/cli- The real
auggieCLI, your own Augment account - Nothing written to
~/.augment - Free, for Windows 10 and 11
It knows when Auggie is done — and when it’s asking
Auggie’s hooks report the start and end of each turn. Its approval box fires no hook, so the card reads that one from Auggie’s own screen.
PromptSubmitsignalYou press Enter (PromptSubmit). The card’s icon spins, the Squad status card counts it as working, and a waiting toast is taken down.
Tool Approval RequiredsignalAuggie shows its “Tool Approval Required” box — only for tools your own rules set to ask. The card pulses and the toast names the tool and command from the last PreToolUse.
StopsignalThe turn is over (Stop). The next queued prompt goes out, the journal gets the answer, and a toast says it’s done.
Works without hooks, too
Hooks are a setting of your Augment account. Without them, Auggie’s own idle marker on the screen ends the turn, so the card still knows.
Failed requests close the turn
A request that gives up on a rate limit sends no Stop. The idle marker closes the turn anyway, and the limit chip appears.
Click, and you’re there
A toast click switches to the workspace, flies the camera to that card and flashes it — even among dozens of agents.
Three things you’ll do with Auggie
Replicas of the app, played step by step. Auggie’s questions — including whether to index your code — are yours to answer.
A first open: Auggie asks whether to index the workspace, and NeuroSquad leaves that to you. Then a fix, an approval box for a command, and the journal.
Everything Auggie can do in NeuroSquad
Most of what Claude Code gets, built on Auggie’s hooks, its plugin folder and its own screen. Where Augment’s design rules something out, the card says so.
- 01
Knows its state
Hooks where Auggie has them, its own screen where it doesn’t — nothing is guessed from a quiet terminal.
Hooks from a card-only plugin
Each card loads a one-plugin folder with
Docs: Hooks from a card-only plugin--plugin-dir, enabled for that run only:PromptSubmitmeans working,Stop— finished. Your installed plugins are not touched.- Built by NeuroSquad
Its own screen fills the gaps
The approval box and the indexing question fire no hook, and hooks can be off for an account — so the card also reads Auggie’s screen and its private idle marker.
Docs: Its own screen fills the gaps A notification that says what it needs
The toast leads with the tool and command Auggie waits on — “launch-process — rm -rf dist” — or its own question. A click flies to the card.
Docs: A notification that says what it needsEvery card keeps its session
The hooks report Auggie’s session id and the next launch runs
Docs: Every card keeps its sessionauggie --resume <id>. A session Auggie no longer has starts a fresh one by itself.Indexing is your call
Auggie asks, per folder, whether to upload the code to Augment’s index. NeuroSquad never answers that for you: the card waits with “Auggie asks whether to index this workspace”.
Docs: Indexing is your call
- 02
Works through the canvas
An arrow from the card is a set of tools. Draw it, and Auggie can use what is at the other end.
Arrows are tools
An arrow to a browser, terminal, note or another agent gives Auggie
Docs: Arrows are toolsbrowser_*,terminal_*,note_*oragent_*(as<tool>_neurosquad) — in its very next request.It can add cards itself
Docs: It can add cards itselfcanvas_spawn_cardopens a terminal, a browser, a note or a helper agent — another Auggie included — next to it, already joined by an arrow.Canvas mode, enforced
The card starts Auggie with
Docs: Canvas mode, enforced--remove-toolfor its process tools,web-fetchandweb-search. Removed tools are not offered at all, so no permission mode brings them back.- Built by NeuroSquad
MCP servers from the registry
Auggie runs any tool without asking unless your rules say otherwise, so for servers installed in NeuroSquad the app itself asks before each call: once, until restart, or never.
Docs: MCP servers from the registry Skills from skills.sh
An arrow to a skill card gives Auggie
Docs: Skills from skills.shskill_loadwith each skill and when to use it — live, in the next request.
- 03
Built for long runs
Context, rate limits and queued prompts, handled on the card.
Context meter
The ring fills from the last request’s tokens in Auggie’s session file, against the window Auggie reports.
Docs: Context meter- Not possible
No Compact button
Auggie summarizes its history by itself when the window fills, and has no command for it — so the card shows the meter, but no Compact button.
Docs: No Compact button - Built by NeuroSquad
Rate limits don’t hang the card
Auggie retries a rate limit for up to five minutes, then gives up without a
Docs: Rate limits don’t hang the cardStop. The card catches that line, shows the limit chip and closes the turn. Prompt queue
Line up the next messages: each goes out when the turn is finished. Daily prompts too.
Docs: Prompt queueJournal and hand-off
Each finished answer, read from Auggie’s session file, goes to a connected note; a full session hands off to a new agent on any CLI.
Docs: Journal and hand-off
- 04
Works in a team
Several Auggie cards — or a mix of CLIs — on one project without stepping on each other.
Isolated worktrees
Give an Auggie card its own git worktree, so parallel agents never edit the same files. Each new worktree folder gets its own indexing question.
Docs: Isolated worktreesAdd a reviewer
One click starts an agent on a different CLI in the same worktree, with an arrow from the author and a prompt to review without editing anything.
Docs: Add a reviewer- Built by NeuroSquad
Dangerous mode, per card
Auggie has no such flag. The card reads your own “ask-user” rules and passes
Docs: Dangerous mode, per card--permission <tool>:allowfor each — and skips the app’s question for third-party tools. - Built by NeuroSquad
Instructions, delivered
Auggie reads AGENTS.md, CLAUDE.md and
Docs: Instructions, delivered.augment/rules. NeuroSquad’s session instructions go in with--rules, since Auggie doesn’t read MCP instructions. The Squad status card
Every AI agent of the workspace on one card, with its status, the model of its latest request and the live time of its turn.
Docs: The Squad status card
- 05
Cost, control and access
What NeuroSquad can count, and what only your Augment account knows.
Tokens per card, cost when it’s dollars
Tokens come from Auggie’s session files, subagents and history summaries included. A turn billed in credits has no dollar price, so it shows “no price” — never $0.
Docs: Tokens per card, cost when it’s dollarsBudget brake
A limit per workspace. Past it, each agent is stopped with Escape (a Ctrl+C at Auggie’s empty prompt would quit it), and automatic prompts stop.
Docs: Budget brake- Not possible
No OpenRouter for Auggie
Every Auggie request goes to Augment’s server. Its custom-provider flags put the key in the command line and send it to Augment — against NeuroSquad’s rule for keys — so there is no OpenRouter recipe.
Docs: No OpenRouter for Auggie Dictation into the prompt
Hold a hotkey and speak. Speech is recognised on your machine and typed into the active agent’s prompt.
Docs: Dictation into the promptFrom your phone
Scan a QR code and the whole canvas opens in the phone’s browser: read Auggie’s terminal, answer its question, send the next prompt.
Docs: From your phone
Who’s waiting, and what it used
Two cards that answer the questions you ask most when several Auggie sessions run at once.
The Squad status card
Every agent of the workspace with its status, model and turn time. The ones waiting on you come first — a command to approve, or the indexing question.
- date-fixAuggieDefault modellaunch-process — rm -rf distNeeds you1:17
- plan-limitsAuggieDefault modelEnforce seat limitsWorking12:24
- new-serviceAuggieDefault modelAuggie asks whether to index this workspaceNeeds you0:00
- docs-passAuggieDefault modelUpdate the READMEFinished5 min. ago
Usage & cost
Read from Auggie’s own session files on your disk and matched to the card by session id. Tokens are exact; credits are not dollars.
| Agent | Tokens | Cost | ||
|---|---|---|---|---|
| date-fix | 402,318 | no price | ||
| plan-limits | 688,140 | no price | ||
| docs-pass | 97,265 | no price | ||
| Total | 43 | 1,187,723 | no price |
The real Auggie, plus a few files
NeuroSquad starts the same `auggie` you run yourself, in a real terminal in the card. This is everything it adds:
Nothing written to ~/.augment
The card’s files are rewritten for each launch in NeuroSquad’s data folder. Your settings are read, never changed.
Your account, your index
Auggie uses your Augment login. Whether it indexes a folder is your answer, in the card, once per folder.
Found where you installed it
npm’s auggie — PATH is read fresh, so a CLI installed while the app is open is found by the next card.
Auggie in NeuroSquad, answered
Give Auggie a canvas
Free for Windows 10 and 11. Your code and your Augment login stay yours.