GodTerm
Coming soon for macOS
Native terminal app for macOS
Every agent. Every account. One command center. GodTerm runs many Claude Code and Grok Build sessions side by side, shows how much each account has left, and lets you drive all of them by voice or a click.
>_ hey god, open a tab on the account with the most left and build a calculator
What it is
GodTerm is a terminal app written in Rust. Each pane is one account, signed in with its own Claude Code subscription login (or Grok Build), and each account holds as many tabs as you like. Every tab is the real agent CLI in its own terminal, nothing re-implemented.
Around them GodTerm adds what the agents don't: live quota per account, moving a conversation to an account with more left, one queue for every approval, a sessions browser, and an assistant you can talk to that operates all of it.
Features
As many Claude Code accounts as you have, each in its own isolated config and keychain login, with any number of tabs per account. Layouts: auto grid, fixed grid, columns, rows, or focus. Panes page when they don't fit, and you drag borders to resize.
Under every pane: the 5 hour and weekly limits left, colored on a gradient, with reset countdowns. The dashboard lists every bucket. Set the assistant to "best", or ask for "the best account", and it picks the one with the most left.
Account running low? Double click the tab. The picker sorts your other accounts by 5 hour quota left, copies the session over, resumes it there, and only then closes the original. Undo for 10 seconds.
whisper.cpp speech recognition on your Mac (or Apple's on-device recognizer), push to talk, a "hey god" wake word, or open mic. Kokoro, a neural voice running inside GodTerm, talks back.
Say or type what you want: "open a tab on the account with the most left and build a calculator". It reads every tab's state and acts with GodTerm's own tools. Batches of destructive actions resolve to one exact plan and one question.
Every tab waiting for permission, across all accounts, longest first, with what it wants: the command, the file, the folder. Approve, always allow, deny or jump. Bypass or any permission mode per account, plus automatic folder trust.
Past sessions from every account and from your main ~/.claude, searchable, with token totals. Copy or move sessions between accounts, with checks and undo, then resume one in a tab.
Any account can run Grok Build instead of Claude Code, with its own isolated home and login. Its permission modes, approvals, weekly credits and sessions show up the same way.
A loops view for scheduled prompts, a memory saver that pauses idle background tabs, a full settings screen, a command palette, privacy mode for screen sharing, and window position memory. Everything is clickable.
Voice
No command grammar to learn. Everything you say goes to the assistant, which works out what you mean and does it across your sessions. Short words like "yes", "deny" and "next tab" run instantly, without it.
WAKE "hey god" heard "hey god, anything need me?"
→ Personal tab two wants Bash command: npm test
How it works
godterm install puts GodTerm.app in ~/Applications and the godterm command on your PATH. Open it from Finder, Spotlight or the Dock.
The first run asks how many accounts you want. Each pane shows the agent's own login; sign in once per account and the banner moves to the next.
Click anything, use Ctrl-a keys, or say "hey god" and ask. The assistant handles the rest across every account.
The grid
An illustration of the GodTerm grid: each pane is an account, with its quota underneath.
● Reading src/parser.rs
● Editing tests/parse.rs
❯ add tests for the parser
5 hour 77% left 1h 46m
Weekly 39% left 3d 15h
Bash command: npm test
Do you want to proceed?
❯ 1. Yes 2. Yes, and don't ask again
5 hour 29% left 3h 02m
Weekly 64% left 5d 01h
Moved 'web' to Client (91% left)
❯
5 hour 91% left 4h 20m
Weekly 72% left 6d 02h
zz paused by memory saver
opening it resumes the conversation
Credits 58% left weekly
Grok Build · weekly credits
FAQ
No audio does. Recognition runs on your Mac with whisper.cpp (or Apple's on-device recognizer), and talk-back runs with Kokoro inside GodTerm, falling back to macOS say. When you ask the assistant to do something, the transcribed text goes to Claude on the account you chose for the assistant, like any prompt you type.
Every account gets its own config folder, so its settings, transcripts and login are separate from the others and from your normal ~/.claude. Logins are stored by Claude Code itself in the macOS Keychain. GodTerm only reads an account's token to fetch its usage, never touches your default login, and never logs tokens.
Claude Code with subscription logins, and Grok Build. Each tab runs the real CLI. The assistant itself always runs on one of your Claude Code accounts.
Batch and destructive actions (closing tabs, stopping loops, sending one prompt to many tabs, denying, approving things like rm or git push) turn into one exact plan and one question. Your yes runs exactly that set. It has no tool to change permission modes, logins or settings.
GodTerm itself is a native Rust app with little overhead. Most memory goes to the agent processes it runs (each claude takes about 530 MB). The memory saver pauses idle background tabs, freeing that memory, and resumes the same conversation when you open the tab again.
macOS and the agent CLIs you use. Voice also needs ffmpeg, whisper.cpp and a model; Kokoro talk-back needs espeak-ng and its model files. godterm doctor checks all of it.
GodTerm is coming soon for macOS. There is no public download yet.
