# Agent Bay — full digest for LLM ingestion

> Native desktop terminal + agent Mission Control. Real PTY first (scrollback restore, prefix history). Gatekeeper for non-human writes. AI optional.

Site: https://agentbay.hazeljs.ai/
Downloads: https://downloads.agentbay.hazeljs.com/
License: Apache-2.0
Platforms: macOS, Linux, Windows
Stack: Tauri 2, Rust PTY (portable-pty), React UI, optional Node sidecar (HazelJS Agent OS)
V1 foundation (M0–M9): shipped

## One-line definition

Agent Bay is a GPU-accelerated developer terminal that keeps a real shell in front and runs coding agents (HazelJS, Codex, Claude Code, and similar CLIs) under deny-by-default Gatekeeper approvals.

## Core facts

1. Human keystrokes in the PTY are never blocked by Gatekeeper.
2. Agent, MCP, plugin, and AI-suggested tool writes are evaluated outside the webview (Rust / trusted Node sidecar). Default decision: deny until approved.
3. Command palette (Cmd+K) suggestions never auto-run. HIGH/CRITICAL risk prompts ask twice when the user chooses to run.
4. Local-only Ollama is supported for command suggestions (Test connection, model tags, Open Ollama.app, user-initiated pull); cloud AI is optional.
5. If the Agent OS sidecar is down, the terminal still works — keystrokes reach bash/zsh.
6. Mission Control can create git worktrees for agent tasks so agents do not stomp the primary checkout.
7. Inspect panels cover Git (status, diffs, remotes, worktrees) and infrastructure (Docker, kubectl, SSH config) with Propose-in-Agents hooks.
8. Product branding: Agent Bay (agent-terminal monorepo). Marketing site is separate from the desktop binary source.
9. Session restore replays scrollback like iTerm (layout + cwd + VT buffer); prefix history search (type a stem, then ↑).
10. Cmd+Shift+F searches command history + memory notes; right rail holds Gatekeeper approvals (⌘⇧\\).
11. M8 History time-travel snapshots + evidence compare; M9 local plugins/MCP registry (no cloud marketplace).
12. Pane titles encode folder · adapter · occupancy for parallel agent sessions.

## Architecture (high level)

- Desktop shell: Tauri + React (iterm-dark density, xterm WebGL)
- Core: Rust crates for PTY/session, storage (SQLite), command risk, secret scanning
- Sidecar: Node Agent OS / Gatekeeper (optional; embedded Node runtime in release builds)
- Releases: git tag → GitHub Actions → GitHub Release + Cloudflare R2 CDN
- Auto-update: Tauri updater reads https://downloads.agentbay.hazeljs.com/releases/latest/latest.json (signed)

## Pages

- / — product overview and use cases (features M1–M9 + V1.x polish)
- /start — install / build instructions
- /compare — differentiation vs Ghostty/iTerm, Warp, IDE terminals, standalone agent CLIs
- /security — security model and ADR-aligned Gatekeeper boundary
- /from-hazeljs — relationship to HazelJS Agent OS

## Typical use cases

- SRE: Infra tab → kubectl context → Propose command → Gatekeeper approval
- Tech lead: Missions + git worktrees for parallel agent tasks
- App developer: Git inspect before commit; Cmd+K for suggested commands
- Security-conscious teams: local Ollama only; no cloud for suggestions
- Agent OS users: run HazelJS DNA packages with HITL tool approvals (right rail)
- New hire: Memory discover + Cmd+Shift+F across history and notes

## FAQ

Q: What is Agent Bay?
A: A native desktop terminal and operating environment for developer agents — real PTY plus Mission Control and Gatekeeper. AI is optional.

Q: Does it auto-run AI commands?
A: No. Suggestions never auto-run. Agent PTY writes require Gatekeeper approval (deny by default).

Q: Do I need HazelJS Agent OS?
A: No. The shell works alone. Agent OS enables Mission Control adapters when present.

Q: Where do I download?
A: https://downloads.agentbay.hazeljs.com/dl/mac | /dl/linux | /dl/windows

## Contact / ecosystem

- Agent OS docs: https://hazeljs.ai/agent-os
- Parent: https://hazeljs.ai/
- Compact index: https://agentbay.hazeljs.ai/llms.txt