A native Mac window for Claude Code, Codex, Antigravity, OpenCode, and Kiro. See which one needs you and what each turn changed.
Website · Documentation · Download
English | 日本語
When several agents work at once, the hard part is not typing. It is knowing which one is blocked, what each turn changed, and what you have already read.
- One list of what needs you. Approvals, questions, stops, and unviewed turns, across every project. ⌘J goes to the next one.
- Every turn is recorded. Weir snapshots the worktree around each round of an agent's work, so you can review that turn or restore the code to before it.
- One worktree per task. Each task gets its own branch and folder, with its pull request status beside it.
- Comments go back to the agent. Comment on any line, then insert your comments into the agent's prompt. Nothing is sent until you press Return.
Weir is not an editor, and it is not an agent. The agents keep their own terminal UI in real terminals, built on libghostty, and you still type in their prompts.
Weir needs macOS 26 or later on Apple Silicon, Git, and Claude Code, Codex, the Antigravity CLI (agy), OpenCode, or the Kiro CLI (kiro-cli).
Download the DMG from the latest release and drag Weir.app to /Applications. Weir updates itself through Sparkle when you choose to. To build from source, see CONTRIBUTING.md.
- Press ⌘O and choose your repository's folder.
- Press ⌘N to make a worktree on a new or existing branch, and choose the agent to open.
- Give the agent its first instruction in its own prompt, then leave it running.
- When it needs you, press ⌘J to go to it.
- Read the turn, comment on it if you want a fix, and press ⌘⏎ to mark it as viewed.
The quick start has each step in full.
Weir has no accounts, analytics, or telemetry. It adds nothing to ~/.claude/ or ~/.codex/: wrappers in its panes pass the hooks on each launch, so agents you start elsewhere are not affected. For Antigravity and OpenCode, it places a plugin in ~/.gemini/config/plugins/weir and ~/.config/opencode/plugins/weir, and for Kiro a hook file at ~/.kiro/hooks/weir.json. Turn snapshots stay in each repository's Git directory.
Privacy and data lists what Weir sends and writes, and Uninstall how to remove it all.
For using Weir:
- Documentation: install, quick start, review, Needs Attention, shortcuts, and troubleshooting.
- User guide: every part of the window in detail.
- Known limitations: what does not work yet, and what is surprising on purpose.
- Data migration: the files Weir keeps, and how to go back one release.
For working on Weir:
- CONTRIBUTING.md: setup, build, signing, and the pull request workflow.
- ARCHITECTURE.md: the modules, load-bearing files, and invariants.
- AGENTS.md: repository conventions, for people and agents.
- Agent integration protocol: the contract between the hook helper, the approval service, and the app.
Weir is pre-alpha. Settings and data formats may change between releases.
Pull requests are welcome. See CONTRIBUTING.md, and SECURITY.md to report a vulnerability. Questions and ideas go in Discussions.
Built on Ghostty (libghostty) and Sparkle. The full list is in THIRD-PARTY-NOTICES.
MIT © 2026 nek0der