Create as many agents as you want, each with its own name, identity, and workspace folder. ·Per-agent settings for engine, model, capabilities, channels, skills, voice, active hours, and language. ·Every agent runs sandboxed, with its own files kept separate from the others. ·Live status for each agent — idle, thinking, awaiting approval, or error. ·Delete an agent and everything it owns in a single action. ·Pick an engine per agent: Pi (built-in), Claude Code CLI, or Codex CLI. ·With a coding-agent engine the model is your CLI account; with Pi, choose any provider and model. ·Cloud providers: Anthropic, OpenAI, Google Gemini, xAI (Grok), Groq, DeepSeek, Mistral, OpenRouter, Together, Fireworks, Cerebras. ·Separate model tiers for the main agent, the public/DM agent, subagents, and a secondary model. ·Override the model for a single session from a quick picker. ·Multiple Claude Code / Codex accounts per agent — they auto-rotate when one hits a usage limit, and fall back to the other CLI mid-task. ·Bring your own endpoint: add any OpenAI-compatible provider (base URL + key) and its models become pickable like the built-in ones. ·Install Claude Code or Codex from inside the app, with a guided login. ·Run entirely on your machine via Ollama, LM Studio, or Jan — no cloud calls. ·Local servers are auto-detected while running and their models registered automatically. ·Auto-launch a local app (hidden in the background, or visible) when an agent needs it. ·Point at custom base URLs for your local servers. ·Signal, iMessage, WhatsApp, Telegram, Slack, and Discord. ·Signal and iMessage run on your own device, with no middleman. ·Read and reply to DMs, and send from the agent's own identity. ·Social inboxes via Overblast: Instagram, X, TikTok, Facebook, LinkedIn, YouTube, Threads, Reddit, Pinterest, Bluesky, Snapchat, Google Business. ·An email inbox the agent sends and replies from. ·A web-chat widget for your site, and agentic phone calls. ·Connect a workspace once and reuse a saved key across agents. ·Per-channel auto-reply, toggled independently. ·An active-hours window so agents only run when you want them to. ·Outgoing quarantine — review and approve messages before they send. ·Group-chat engagement controls. ·A warning before enabling a channel already used elsewhere, to avoid double replies. ·An isolated, sandboxed public agent handles strangers, kept away from your private workspace. ·Per-thread file isolation for every inbound conversation. ·Reply quarantine for untrusted contacts. ·Tool execution is sandboxed, and secret values are scrubbed from the environment. ·Per-tool secret scoping: each shell command, skill, or custom tool only receives the vault keys you granted it — everything else is withheld, so a leaky tool has nothing to leak. ·A blocked command fails with a missing $VAR and the agent asks for access; a code scanner suggests which keys a skill actually reads, and curated store skills auto-grant their declared keys on install. ·Every remote request is signed with the device's own key — nothing bearer-token-like to steal. ·Local-first: run everything on a local model and nothing leaves your machine. ·No account required, and no telemetry unless you turn it on. ·Your data lives in a folder on your machine (~/Documents/00). ·Provider requests go directly from your machine using your own keys. ·Encrypted vault (AES-256-GCM) for API keys and channel tokens. ·Write-only — agents can see key names, never their values. ·Per-agent secret overrides, so one agent can bill a separate account. ·Bulk-import keys from a pasted .env file. ·Agents can request a key from you securely, entered outside the chat. ·Open the engine to your Wi-Fi and control it from any browser or phone — no app needed on the other device. ·Explicit pairing for every device: compare an 8-digit code and accept; nothing connects silently. ·Decide per device which agents it can see and use. ·Pairing requests surface at the Mac's notch and in the engine log, with accept/reject in place. ·HTTPS on the LAN so meeting capture works from another device's browser. ·Pairing floods are rate-limited per-IP and globally; stale requests expire on their own. ·A guided pairing flow: one step at a time, and it advances on its own when the device shows up. ·The browser's certificate warning is explained before you hit it — named screen and button for Safari, Chrome and Firefox. ·Link engines on your network as peers — their agents join your list, tagged with their host. ·A guided flow for linking: pick the kind of machine, and the transport, install and approval follow from that. ·Chat, dispatch, and the notch drive remote agents exactly like local ones. ·Share a single agent with a URL you can paste on another machine. ·Remote agents are told who is driving them — operator name, hub, network, and timezone. ·The host machine always decides which of its agents each peer or device gets. ·A peer that goes offline is detected, shown grayed in your list, and rechecked automatically until it's back. ·Peer a headless server over an SSH tunnel: the server stays loopback-only with zero exposed ports, auth is your SSH keys, and pairing, proxy, and relay all ride the tunnel — with supervised auto-reconnect. ·One-click remote install: connecting over SSH probes the server and, if 00 isn't there, installs the headless engine over the same connection and pairs automatically. ·App tunnels: see a dev server or API on the remote's localhost in your own browser — add a port from the peer card, or let it open when a remote agent's output mentions a localhost URL. ·Guided setup a non-technical person can finish: type user@server, we detect whether it needs a password, offer one-time passwordless setup (your key installed, password never stored), install the engine, and create the server agent — with a plain warning when the machine is shared. ·Work ON any server you can SSH into with nothing installed there: the agent runs on your machine, its changes land on the server. ·Pick the server folder as the work folder straight from the chat's folder menu (⇅ entries) — browse its real folders live, preview files read-only. ·The agent connects by NAME and never sees a credential: passwords stay in the encrypted vault, used only engine-side, with one-time passwordless key setup on offer. ·Everything follows the folder: run buttons derive from — and execute in — the remote project, the terminal button opens a shell ON the server, and workspace search runs over there. ·App tunnels with auto-detection, plus a port scan that lists what's already listening on the server — every running app one click from your browser. ·Add a location app-wide or per-agent, from Settings → Network or right inside the folder menu. ·The same engine runs headless on Linux, Windows, and servers — install with one command. ·An auto-start service (launchd, systemd, or a Windows task) with install/start/stop/status from the CLI. ·Create and run agents from the shell — the current folder becomes the agent's working folder. ·Scaffold a project folder (TODOS.md, files/) with one command. ·Approve device pairings and open/close LAN access from the terminal. ·One-command self-update to the latest build. ·Dispatch a command to any agent from the top of your screen (⌃⌥Space). ·Replies play as a teleprompter; long ones expand and scroll. ·Approve or reject outgoing messages right at the notch, with the destination shown. ·Agent questions render as interactive cards — answer with the 1–9 keys. ·Files an agent shares arrive as a quiet pill that expands into thumbnails with a reply box. ·Voice messages with live level feedback, transcribed in the agent's language. ·Live activity while an agent works: tools, subagent count, and todo progress. ·A recording dot while a meeting is being captured; the live transcript plays as a resizable teleprompter with timestamps and elapsed time. ·Choose what surfaces there: all agent activity, or only what you start at the notch itself. ·Mute a single agent — its notch pills and macOS notifications stay quiet. ·A curated library across SEO, content, email, growth, sales, ads, analytics, and automation. ·Install a skill into any agent in one click; required keys are prompted up front. ·Ask an agent to create its own skill — it writes a SKILL.md in its workspace. ·Browse a skill's files and export or download it for other agent tools. ·Speech-to-text via Mistral Voxtral, Deepgram, ElevenLabs, or OpenAI. ·Text-to-speech via ElevenLabs or OpenAI. ·A realtime voice mode for back-and-forth conversation. ·Choose a voice per agent. ·Record a window or tab's audio into an agent as a live meeting. ·Record from a microphone instead — in-person meetings, a call on speaker, any input device. ·Automatic transcription streamed into the agent as it happens — optionally in real time, with the in-progress sentence shown as a tentative tail. ·Pick the local transcription model: Whisper tiny → large-v3 (gated to what your machine can run) or Parakeet TDT v3 (25 languages), with installed vs downloads-on-first-use shown. ·Trigger words: say an agent's mention words in a meeting and it pings you at the notch with the surrounding context — reply with the live transcript attached (⌃⌥R). ·Pause, resume, and stop from the notch or the capture tab — always in sync. ·When a meeting ends, the next thing you dispatch from the notch carries the transcript automatically. ·Crash-proof capture: audio is saved before transcription, uploads retry, and an interrupted meeting is recovered and finalized on restart. ·Capture from another device's browser over the LAN (HTTPS). ·Run agents on a cron — daily briefings, recurring jobs, timed follow-ups. ·One-time scheduled runs. ·Dispatch one command to many agents at once, each running it as its own task. ·Agents keep a live TODOS.md checklist — a panel under each session shows it in real time, done items on top, and collapses to a count when everything's checked. ·An idle agent with open todos gets nudged to finish them; when every item is checked the work is recorded as done and the originating thread gets a reply. ·Define a finish condition per agent — "when is this work actually done?" — verified by the agent itself before it declares completion, with a per-session override from the composer. ·Subagents: an agent spawns focused helpers for parts of a task. ·Team members, so agents know who they're talking to. ·Per-agent capabilities and explicit tool grants. ·Cross-channel contact profiles, built quietly in the background. ·A private per-conversation memory that grows over time. ·A day-by-day timeline of each agent's activity. ·Session history you can revisit any time — every session streams live, even ones started elsewhere. ·Custom pixel-art faces — generated deterministically or drawn by a model. ·Per-agent colour, emoji, and display name. ·A language per agent. ·An active-hours schedule per agent. ·Sandboxed file tools: read, write, edit, list, grep, find. ·Shell tools for the trusted main agent, with vault keys available in its environment. ·Browser tools for web tasks. ·A configurable working folder per agent that holds its TODOs and actions — with a searchable picker, and each session keeping its own folder. ·Workspace-wide search over file names and contents — a hit reveals the file in Finder on the same machine, or downloads it from a remote one. ·Locked files: mark files or folders (by glob or a one-click picker) as read-and-run but never edit — enforced in the file tools and mirrored into Claude CLI deny rules that hold even in skip-permissions mode. ·Header run buttons are derived from the folder's own files — package.json, deno, composer, pyproject, Makefile, justfile, Taskfile, Rakefile, Cargo, Go, Gradle, Maven, and docker-compose — with your most-used options first, no ACTIONS.json to maintain. ·A tabbed terminal in the session: several real shells at once, minimize to just the tabs while they keep running, each opening in the folder you picked. ·Command autocomplete as you type — installed commands and their subcommands, the folder's package.json/Makefile/justfile targets, following you as you cd; Tab to accept. ·Select terminal text to attach it to the composer as context, so you can ask the agent about an error without copy-paste. ·File previews open full-screen from anywhere — a message, the Files panel, the Media grid, or the in-app file explorer. ·Drive an iOS Simulator or an Android emulator inside the session — one live phone you and the agent share, with a floating toolbar for home, app switcher, back, lock, screenshot, screen-record, reload and power. ·Boot a device headlessly, tap/swipe/type, read its accessibility tree or view hierarchy, install and launch a build, and open deep links — as a skill the agent can use, or by hand. ·iOS runs through the bundled driver; Android needs only adb — install the skill and it appears as its own tab. ·Record the screen or grab a screenshot straight into the agent's files/ folder, so a repro and the question about it are the same artifact. ·Your taps and the agent's map to the same coordinates, so a human tap and an agent tap mean the same thing. ·Plug in a real Android phone and it joins the same tab as your emulators — live screen, tap it from the panel, no separate mode. ·On real hardware agents are look-only: they can screenshot your phone and read the screen, but tapping, typing and installing stay off until you enable that specific device. Your own taps are never restricted. ·Drive a device that's plugged into another machine in your fleet — the panel asks the engine that actually owns the phone. ·A media model store: install an image, video, music or speech model with one click and it runs on this Mac — free, offline, nothing sent anywhere. ·Local image models (Z-Image Turbo, FLUX.2 klein, ERNIE-Image, Juggernaut XL, Qwen-Image), video (Wan 2.2, LTX-2), and audio (Stable Audio 3, ACE-Step for full songs with vocals). ·Every card is checked against your Mac before you install it — memory, free disk and chip — so a model that can't run says what it needs instead of failing later. ·Real samples on every card, generated by that exact model: enlarge images and video in a lightbox, play audio inline. ·Install to an external drive when the internal one is tight. ·LoRAs: add one by URL or local file and your agents can pick it per generation. ·API models in the same grid — one card per model listing every provider that serves it (fal, Replicate, OpenRouter) with each one's price; add a key to enable. ·One tool per job (image, video, music, sound effects, speech) with the model as a parameter — agents don't learn a new tool per provider. ·A model order per agent, so it reaches for your local one first and only falls back to the cloud if you allow it. ·Speech models for transcription and voice, installed the same way, with what each is good at and which languages it covers. ·Web search (Tavily, Exa). ·Maps and places search. ·Marketing tools for common go-to-market work. ·A native macOS app with a self-contained runtime — nothing else to install. ·A bundled engine, so it runs offline for local models. ·Real-time updates everywhere over WebSocket — status, replies, approvals, activity. ·Keep-awake and power controls while agents are working. ·A self-hosted update check that flags new versions — you choose when to download. ·