stop checking every tab. vord tells you which agent needs you.

session hosting

vord owns every session as a real terminal

vord doesn't connect to your sessions from the outside. It hosts each one itself as a real PTY through SwiftTerm — which is why it can see every byte, and why its status detection works at all. In the same window you can run Claude Code sessions (with resume), Codex sessions, and plain shell or SSH sessions managed through a connection manager with an encrypted secret vault for your keys and credentials. Every session keeps running whether it's on screen or not. There's terminal search, and you can paste an image straight into a session with Cmd+V. Need a fresh start? Clone a repo into a new project without ever leaving vord.

• Claude Code sessions, with resume.
• Codex sessions.
• Plain shell and SSH sessions, managed through a connection manager with an encrypted secret vault for your keys and credentials.

the cockpit

three densities, one fleet

The grid pulls every session from every project into one view, sorted with anything waiting on you at the top. Switch density to match what you're doing. There's a gallery view for the wider look, plus the small controls that keep a busy fleet honest: mark a card done, or park one to deal with later. vord also drops a peer hint into each agent that tells it how many others are working in the same project — so they're aware they're not alone in the repo.

• Compact — pure status cards. The right view when you have a lot running and just need to scan.
• Normal — the grid with a live terminal slice in each card, so you can read what's going on without opening anything.
• Focus — one session at full size, fully typeable, for when you drop in to answer or steer.

the git inspector

read the work before you trust it

An agent finishing is not the same as an agent being right. The inspector slides in from the right so you can check the diff without breaking your flow. You get light editing for the small fixes — bracket matching, multi-cursor, find and replace — but it stops there, on purpose. This is a review surface, not an editor. For real work, "Open in VS Code" or "Open in Finder" is one click away. On the branch side you can see, switch, and create branches; worktrees are shown read-only and vord never creates them. The honest limits: no rebase, merge, or blame UI. No automatic worktree management. If you need those, you need git proper — vord gets you to the point where you can trust the change, then hands off.

• Diff tab — additions and deletions in green and red, tree-sitter highlighting, inline or side-by-side.
• File tab — the complete file with search and a symbol outline.
• Commit tab — stage by file or by individual hunk, with a commit message drafted by `claude -p` that you can edit before committing.

vendor-agnostic

two vendors, one fleet, managed MCP

Claude Code and Codex both run in vord, each with its own detector feeding the same status grid. You're not locked into one provider's tooling to get a unified view. The built-in MCP manager handles servers for both Claude and Codex, with live health checks, and it works only through the official CLIs — it doesn't reach behind the tools to edit their config. vord also ships its own MCP server, including a `show_to_user` tool: when an agent wants to put an image or a webpage in front of you, it appears wherever you're working, instead of getting buried in terminal output.