VibeForge 2.11.0

2.11.0: a lead hands parts of the work to the agents best suited to them, and you decide whether those tasks wait for you or start on their own.

Added

• A lead for your team. Pick a Lead in Code in Settings → Agents together, such as Claude Code. When a Code pane starts it, it's told your team: the agents allowed in that workspace, what each is good at and what it costs. It hands them parts of the work with vibeforge task when another agent is better or cheaper for a part, or when parts can run at the same time, and does the rest itself. Its Claude Code runs vibeforge without asking each time.
• Good at, and cost. Each agent's Settings tab has a one-line Good at and a Cost (Cheap, Everyday or Strong) for the lead to choose by. vibeforge who lists them too, and only the agents allowed in the asking CLI's workspace.
• Ask first, or Go ahead. Under Ask first, the default, a task a CLI hands out waits for you: its title bar shows "N to start", to start them or discard them. Under Go ahead tasks start at once, up to how many work at the same time and how many a CLI hands out between two of your messages; past those limits they wait for you the same way.
• The lead can apply its helpers' work with vibeforge apply <task>, if you turn that on. It ends the helper's session and brings its changes into your folder as uncommitted edits. Otherwise you apply them from the task, as before.

Changed

• Handed-out tasks wait for you by default. Since 2.7, vibeforge task started a task at once. It now waits for your Start unless Settings → Agents together says Go ahead.

Fixed

• A helper stuck on a question says so. A handed-out task's CLI that stops at a question for a person (Grok Build 1.0.70 asks whether to trust a new folder) used to be reported as finished, with its screen as the answer. The report now says it may be waiting for you and shows the end of its screen, and its real answer follows as a second report once it carries on.
• A CLI that never moves is still checked. A task whose CLI showed one screen and never changed it was never looked at again, so its report never came.

VibeForge 2.10.0

2.10.0: CLIs in Code know about each other, and a task you hand out reports back when it's done.

Added

• Handed-out tasks report back. When an agent finishes its turn on a task another CLI handed it with vibeforge task, that CLI gets a report as a message: what the agent said, its changes as a patch with the files listed, and where its copy is. If the task ends before the agent answers, the report says so. The task's terminal shows "Reports to …" until then, and its stop button cancels the report. --wait still prints the first answer right away instead.
• CLIs in Code know about each other. Claude Code, Codex and Grok Build started in a Code pane are now told about vibeforge who, tell and task, added to their own instructions, so they use them without being shown how. Codex is left alone when its own config sets developer instructions. Turning off Settings → Agents together turns this off too.

Fixed

• vibeforge task takes the names vibeforge who prints. who listed agents by a shortened name, which task didn't accept for agents with long names ("No agent called vibeforge-github-repo-ma"). who now prints each agent's id, and task still takes the shortened names too.
• Task titles are cut at a word. A long first line was cut at 80 characters mid-word, so "…containing the single word: hi" became a title without the "hi". It now ends at a whole word with "…".

VibeForge 2.9.0

2.9.0: pick any theme in Settings, and keep it when the desktop switches.

Added

• Pick any theme in Settings. Settings → Appearance → Colours still follows your Omarchy theme by default, and now lists every theme next to it: the ones installed on your machine, your own included, and Omarchy's 22 stock themes, which VibeForge now ships so they work without Omarchy too. Click one, or move with the arrow keys, and the whole window changes at once. A pinned theme stays when the desktop switches to another; if it is removed, VibeForge goes back to following Omarchy and says so. Ctrl+K finds them too: type "tokyo" and press Enter.

VibeForge 2.8.1

2.8.1: Start at login shows VibeForge in the tray again.

Fixed

• Start at login shows the tray icon. At login VibeForge could start before Omarchy's bar was ready to take tray icons. It started, hidden as it should be, but with no icon there was nothing to open it from, so it looked as if it hadn't started at all. It now watches for the bar's tray and adds its icon whenever one appears, including after the bar restarts.

VibeForge 2.8.0

2.8.0: the Tokens tab counts OpenCode and Copilot CLI, and Antigravity's tokens show while its session is still open.

Added

• Tokens from OpenCode and Copilot CLI. The Tokens tab now counts OpenCode, from its opencode.db (1.x and 2.x), and Copilot CLI from 1.0.95 on, from the usage record it writes for each model call. A forked session's copies of earlier calls are counted once. Cursor Agent keeps no token counts on disk, and Crush keeps only each session's latest context size, so neither appears.

Fixed

• Antigravity's tokens show while its session is still open. Its conversation databases hold new writes in a side file (-wal) until the CLI closes, and the Tokens tab only noticed them after that. It now sees them on the next refresh.

VibeForge 2.7.2

2.7.2: Send to… and review stay in the workspace you meant, a review sees only the changes it was asked about, and answers between CLIs no longer get lost.

Fixed

• Send to… and Review with… never pick a CLI in another workspace unseen. With one other CLI open somewhere else, the menu went straight to what to send, so "Ask Claude Code to review" pasted the review into a Claude Code in a different workspace (and Send to… jumped there). The menu now lists that CLI with the workspace (or task, chat or routine) it is in, and only skips the choice when the one other CLI is in the same workspace.
• Review with a new CLI here. The send menu can start a CLI in a new pane beside this one to do the review, so reviewing doesn't need a second CLI open first.
• "Its changes" are only its changes. A review or Send to… → Its changes included every file that was already changed or untracked when the CLI started. Files that were already changed then, and that it hasn't touched since, are now left out; when nothing is left, the review says so and waits for a turn that changes something.
• Messages to a CLI that has just started wait until it has drawn its first screen and gone quiet, instead of landing while it is still starting.
• Handles stay put. vibeforge who names (claude, claude-2) no longer shift when a CLI closes, so an answer addressed to one can't reach another CLI that started later.
• An answer isn't lost when the asking CLI stops waiting. Claude Code's shell tool gives up on a command after two minutes, while vibeforge tell --wait waits up to nine. An answer that came after the tool hung up was dropped; it now arrives as a message.
• The plan meter no longer freezes the window. Looking for a Gemini (Antigravity) sign-in in the desktop keyring ran on the window's main thread, and a locked or slow keyring held everything up for as long as a second and a half on every plan refresh. It now runs in the background.
• Writing from the phone or a chat counts as you stepping in, as typing in the terminal already did: it starts the message count between two CLIs again and lifts a Stop.
• Stop while a message is going in no longer drops another message waiting in the queue, a delivery asked for at the end of a pass is no longer put off by a second, and a waited-for answer that never comes stops showing as waiting after half an hour.

VibeForge 2.7.1

2.7.1: clicking a terminal no longer interrupts two CLIs talking, and vibeforge who reads like your prompt.

Fixed

• Clicking a terminal no longer counts as typing. CLIs such as Claude Code ask the terminal to report focus, and those reports reset the message count between two CLIs and lifted a Stop. Focus and mouse reports are now ignored; keys still count.
• vibeforge who shows folders under your home as ~/…, as a shell prompt does, instead of the full path.

VibeForge 2.7.0

2.7.0: your CLIs can talk to each other, review each other's changes and hand out tasks.

Added

• Agents together. A coding CLI in any VibeForge terminal can now talk to the others: vibeforge who lists them, vibeforge tell <name> "…" pastes a message into another CLI once it is free (labelled with who sent it and how to answer), and vibeforge tell --wait brings the answer back, from the session logs of Claude Code, Codex, Grok Build and Kimi Code, or from the screen for other CLIs. An answer that takes longer than the wait arrives later as a message.
• Hand out tasks. vibeforge task <agent> "…" gives a VibeForge agent a task that runs in its own git copy of the workspace, never in the asking CLI's folder. The task says who asked for it, a person still applies its changes, and a task handed out this way can't hand out more. Agents that VibeForge starts are told about these commands.
• Send to… and review. The send button on a Code terminal's title bar puts that CLI's last answer, the selected text or its changes into another CLI's prompt as a draft, and Ask … to review its changes has another CLI review the diff when this one's turn ends, then sends the review back.
• Limits you can see. Two CLIs can trade 8 messages before the next one waits in the prompt for you to press Enter, and typing in either terminal starts the count again. A chip on the title bar shows who a CLI is talking with, and its stop button ends it. Settings → Agents together turns it all off or changes the message limit and the review rounds.
• Ctrl+K finds what things say. Typing three letters or more also finds a task by its details, a routine by its prompt and a skill by its procedure, with the words around the match.

Changed

• New tasks work in their own copy. A new task in a git workspace starts with Work in a separate copy on, so its agent never edits the folder you or another agent are in. Switch it off on the task to work in the workspace itself; existing tasks keep their setting.
• Everything in your language. The tray menu, the quit question, the "still running in the tray" notice, desktop notifications for tasks and routines, plan alerts, schedule descriptions (on your language's clock) and git's change summaries ("2 files +10 −1") now follow VibeForge's language.

Fixed

• A routine that can't start says so. When a scheduled routine fails before its CLI runs (its folder or CLI is gone, or the CLI won't spawn), you now get the same desktop notification as a run that ended, with the reason, and the third failure in a row still says so once.
• A routine waiting its turn says so. A due routine that waits for another coding CLI in its folder sends one notification for that slot, naming who it is waiting for.
• A task or routine on a trust or sign-in question keeps its folder. Until it has started working, other waiting work doesn't start in the same folder, so nothing lands while the question is still up.
• Applying a copy with no changes tidies it away. The copy is removed and the task is marked done, instead of staying until you discard it.

VibeForge 2.6.2

2.6.2: Gemini and Gemini 4 Argon plan limits, and Antigravity CLI token counts.

Added

• Gemini plan limits, including Gemini 4 Argon. When you are signed in to Antigravity CLI (agy) and plan limits are on in Settings → Usage and activity, VibeForge now shows your Gemini 5-hour, 7-day and Gemini 4 Argon windows alongside Claude, Codex, Grok, Kimi and Muse, with the four-point Gemini spark on the desktop and the phone page. The sign-in is read from Antigravity's token file or the system keyring (gemini / antigravity).
• Antigravity CLI token counts. The Tokens tab now reads Antigravity's SQLite conversation databases (~/.gemini/antigravity-cli/conversations/*.db and ~/.gemini/antigravity/conversations/*.db), counting fresh input, cache reads and writes, thinking and output per model (gemini-4-argon-trial, gemini-3.8-flash-n…) once per model call.

VibeForge 2.6.1

2.6.1: CLIs behind a mise wrapper start again, and the GitHub graph loads.

Fixed

• CLIs installed through mise wrappers run again, and the GitHub graph loads. Some setups put small scripts in ~/.local/bin (gh, codex, crush…) that install a CLI through mise on first use and then run mise x <tool> -- <tool>. When mise's own folder for that tool is also on PATH, behind ~/.local/bin, the script finds itself again and loops until something kills it. That is how the login shell's PATH looks, so the GitHub contribution graph timed out with "Command failed: gh api graphql…". VibeForge now runs the program behind such a script when it is on PATH, and uses the script only when nothing else is there. When gh does time out, the message says so.