The ADE for humans.
Your agents run the work. hide reads every session and brings you only what needs a person.

Download · Website · Docs · Discord · Discussions · Contributing

You run several coding agents at once, and someone has to keep track of them. hide puts every agent, task and pull request in one view, lets the agents start, watch and write to each other, and brings up only what needs a person. Close the laptop and the work keeps going.

It works with the agent CLIs you already signed in to: no new API key, no hosted service.

Claude Code Codex Antigravity OpenCode Grok Pi omp

Hide AI does the reading Hide AI reads what each agent did and writes what a person needs: a title, why it stopped, what you asked and what you missed. Agents sort themselves into Needs You, Unread, Working and Seen, and the ones waiting on you sit on top of every screen. Hide AI runs on the agent CLI you already signed in to, and every status still works with it switched off.
Every agent at a glance The sidebar shows the same work three ways: Projects as a tree of checkouts and the agents in them, Tasks grouped by who acts next, and Pull requests sorted by what waits on you. The Overview draws the whole night as one map: which agent started which, the letters between them, and who is waiting on you.
Agents start, watch and write to each other A lead starts workers, a worker starts a helper, on this machine or another, and they write to each other in letters. Mix vendors freely: one agent writes, another checks. The agent that started a child watches it: it hears within a minute when the child stops on a question, and after 20 quiet minutes when it stalls. For a set of pull requests, a Conductor agent runs a mission: it plans the work, starts the workers and reports back.
Memory every agent shares Project Memory turns what you decide in a session into a card, checks it against the repository and hands it to the next agent, whichever vendor runs it. Tell Codex once on Monday; Antigravity already knows on Thursday. A rule worth keeping comes back as one pull request to your docs.
Your agent drives the browser An agent opens the page it changed beside its pane, clicks through it and reads what it shows, so it checks its own work before it asks you. A file or diff it names opens next to it too. hide browser open localhost:5173/invoices hide browser click browser-1 --text "Export CSV" hide file open src/export/csv.ts
Pull requests, waiting on you first The ones waiting on you come first, with their checks; the ones an agent is still working on sit below. One click hands a pull request to an agent.
One core, any screen Put hide's core on a machine that never sleeps. Projects, letters and titles live there; your laptop becomes a screen, so closing it stops nothing. Add any machine by its SSH alias and its agents join the same lists, and pair your phone by QR to answer the one that needs you, over your own Tailscale.

Give an agent more than one account: a work and a personal Claude Code, or a model gateway behind a wrapper program. Each profile is its own account folder with hide's hooks installed there; pick one in the start panel, per project, for a mission's workers or for Hide AI.

• Real terminals. Agents run in real terminal panes with their layout, scrollback and focus, drawn in place.
• Files and diffs. An editor with a VS Code style Explorer, and each checkout's changes one click from its tab.
• A worktree per task. GitHub issues and local notes sit in one backlog; starting one opens a worktree, an agent and its first prompt.
• Keyboard first. ⌘K goes to any agent, task, issue or pull request, and ⌘P opens any file.
• Guardrails. Guard the base branch, working folders, files and risky Git commands, per project.
• Limits and cost in view. How much of each agent's week is left, and each project's last seven days at API prices.

All three run the agent CLIs you already use, side by side, across more than one machine. hide is built for the part after that: knowing which of them needs you, and why.

_{The Orca and Herdr columns come from each project's README on 2026-11-10; an empty cell means its README does not describe the feature, not that it cannot be done. Something wrong? Tell us. Parts of hide's terminal layer come from Herdr, and NOTICE names each file.}

hide installs a skill and hooks into each agent, so an agent can do from its pane what you do from the window.

hide agent spawn --parent here --name export-csv --intent export-csv --kind codex \
  --repo ~/billing-app --branch feat/export-csv --brief "Export invoices as CSV"   # a worker it watches
hide request send <agent> --intent review --body "Check #431 before I merge"   # a letter to another agent
hide mission help                                                     # plan and run a set of pull requests
hide device add workbox                                               # another machine, by SSH alias

hide guide prints how an agent works inside hide, and hide --help lists every command.

withhide.dev picks the installer for your system, or download it from the latest release:

Check the installer against its .sha256 file before you open it. After that one install, hide updates itself. Install and sign in to the agent CLIs you want hide to start; hide never asks for their credentials. hide runs its own terminals: each pane lives in a small holder process that keeps running across an app restart.

Install hide covers checksums, Gatekeeper, each system's steps, updates, uninstalling and troubleshooting, and What each system supports records where each system stands.

git clone https://github.com/with-hide/hide.git
cd hide
pnpm install --frozen-lockfile
pnpm --dir desktop package

sudo /usr/bin/ditto --rsrc --extattr --qtn desktop/out/hide-darwin-arm64/hide.app /Applications/hide.app
open /Applications/hide.app

1. Install hide from withhide.dev or the latest release, and sign in to the agent CLIs you use.
2. Add a project, start an agent and give it a task; ask it to split the work across a few workers.
3. Watch the sidebar's Tasks list and the Overview map, and answer only what reaches Needs You.

• Nothing hosted. The app, the core and Hide AI run on machines you own, so your code goes only where your agent CLIs already send it.
• Credentials stay with their tools. Agent CLIs and SSH keep their own sign-in state. The one thing hide reads is Codex's auth.json access token and account ID, which it sends to Codex's usage endpoint to show your usage.
• Your phone stays in your tailnet. It reaches your machines over your own Tailscale.

pane holders ─ one per pane: its PTY, program and parsed terminal
     │  terminal output + process facts
     ▼
hide-core (Rust) ─ the one owner of hide's state, with its own engine over the holders
     │  typed events in, snapshot deltas out
     ▼
hided ─ the daemon and the `hide` CLI: loopback HTTP + a token WebSocket
     │
     ▼
web shell (React) ─ in the Electron app, or a browser on the same machine

The core owns the state behind one snapshot boundary, and the shell only renders it and sends user events back, so the screen never keeps a competing model of the session. ARCHITECTURE.md explains the boundaries and their reasons.

hide is built in the open. Report a bug you reproduced with the bug form, ask for a feature with the feature request form, and bring open-ended ideas to Discussions. Pull requests are open to anyone who follows the template; a maintainer reads every one. CONTRIBUTING.md owns that policy and lists the verify gates and their local commands, and AGENTS.md holds the rules every change follows.

pnpm install --frozen-lockfile
bash scripts/verify-cargo.sh test   # Rust suites
bash scripts/verify-web.sh          # web and desktop typecheck, lint, test and build
pnpm --dir desktop dev              # the desktop app, unpackaged, against this checkout's build

• Chat with the team and other users: Discord
• Questions: Discussions Q&A
• Feature requests: the feature request form
• Open-ended ideas: Discussions Ideas
• Bugs you reproduced: the bug form
• Security: report privately as SECURITY.md describes, never in a public issue
• Teams and everything else: [email protected]

hide is fair source under the Functional Source License 1.1, ALv2 Future License (FSL-1.1-ALv2). You may use, change and redistribute it for any purpose except offering others a commercial product or service that competes with hide, and using it in your own work, including at a company, is always allowed. Each release becomes available under the Apache License 2.0 two years after it is published, and releases up to and including 1.1.1 remain under the Apache License 2.0. NOTICE carries the copyright notice and the files derived from other projects, which keep their own licenses. Third-party components keep their own licenses, listed in THIRD_PARTY_NOTICES.