@bivy/bivy 0.19.4-staging.6 → 0.20.0-staging.1

package/README.md

@@ -4,22 +4,27 @@
 [![license: AGPL-3.0-only](https://img.shields.io/badge/license-AGPL--3.0--only-2b6cb0)](LICENSE)
 [![node](https://img.shields.io/badge/node-%E2%89%A520-2b6cb0)](https://nodejs.org)
 
-**Build, try, and review apps from your phone. Your coding agent and dev
-environment stay on your own machines.**
-
-Bivy is an open-source remote development environment built around coding
-agents. Ask for a change, try the running app, and point to or draw on what
-needs fixing. Send that feedback to the agent and try again—all in the same
-session, without going back to your computer.
-
-Live previews bring your app to your phone or browser without deploying it to
-Render, building a Docker image, or setting up a separate preview server.
-Share a preview link so someone else can try it and leave notes, too.
-
-Keep Claude Code, Codex, Pi, OpenCode, or another supported agent. Keep your
-repos, tools, databases, and development environment. Bivy connects them to
-chat, a terminal, app previews, and code review wherever you are. Start work
-yourself, or let an issue, CI failure, message, schedule, or webhook start it.
+**Local coding agents that show their work. Anywhere.**
+
+Bivy is the open-source workspace for coding agents. It runs Claude Code, Codex,
+Pi, OpenCode and other agents on your own machine. Reach them from a browser or
+your phone, with the live session, its terminal, its approvals, and the app
+they're building right in the chat. Try it, mark what's wrong, and send it back.
+
+Bivy is not another coding agent and not a cloud development machine. The agent
+stays local and does the coding with your model provider. Your repos, tools,
+databases, and services stay where they are. Bivy gives you remote access to all
+of it, plus live previews, automations, and review.
+
+- **Live previews.** The running app beside the chat. Mark it, send it back,
+  share it with someone who has no Bivy account.
+- **Automations.** GitHub issues, failed CI, Linear, Slack, schedules, and
+  webhooks start the work. It comes back as a preview link or a pull request.
+- **Any agent.** Hit a usage limit? Fork the session to another agent, or let
+  Bivy retry when the limit resets.
+- **Your machine, anywhere.** Start at your desk, pick the session up on your
+  phone. The machine dials out, so there are no ports to open, and session
+  traffic is end-to-end encrypted.
 
 **[Start free on Bivy Cloud](https://app.bivy.sh)** ·
 **[Quickstart](docs/quickstart.md)** ·
@@ -47,30 +52,34 @@ agents. Connect a Mac, Linux computer, or existing server and bring your own
 agent subscription, model API key, or local model. You can also self-host the
 entire remote-access stack.
 
-> **Bivy is 0.x software.** Claude Code, Codex, Pi, and OpenCode are the
+> **Bivy is 0.x software.** Claude Code, Codex, Pi, OpenCode, and Grok are the
 > release-tested paths. Credential sync, resume, handoffs, approvals, and
 > sandboxing depend on the runtime. See the
 > [runtime support matrix](docs/runtime-support-matrix.md).
 
-## Build → preview → mark up → iterate
+## Don't just read the diff. Try the app.
 
-Remote chat lets you ask an agent for a change. Bivy also lets you **use what
-it built and show it what to fix**, without a separate deployment step.
+Bivy lets you **use what the agent built and show it what to fix**, without a
+separate deployment step.
 
 1. **Ask for a change.** The agent works in your repo with your existing tools
    and local services.
-2. **Try the app.** Open a live preview from the session. Use the running app,
-   not just a screenshot of what the agent says it finished. Bivy can discover
-   dev servers running in the session workspace; tap **Preview** to open one.
-3. **Mark up what needs work.** Point at an element or circle and draw on the
-   preview. Add a note, then send the draft to the agent with the element and
-   page context. Marked-up screenshots and before/after comparison are available
-   when agent screenshots are enabled.
-4. **Iterate and review.** Try the next version, inspect the diff, review checks,
-   and decide when the work is ready—not just when the agent stops.
-5. **Bring someone else into the review.** Copy a public preview link so they
-   can use the app without a Bivy account and leave notes on specific elements.
-   Bring their notes into the session when you're ready to act on them.
+2. **Try the app.** Bivy finds the dev server the agent starts and opens it
+   beside the chat: web apps, terminals, and desktop apps. Use the running app,
+   not a screenshot of what the agent says it finished.
+3. **Mark what needs work.** Press and hold anything in the preview to mark it,
+   or drag to circle it, then say what you want. **Mark another** keeps
+   separate notes separate. The marks go to the agent with the element and page
+   context. No screenshots to paste.
+4. **Follow each note.** Every mark stays in the chat as a pin that resolves
+   itself: **Changed** when a later run changes what you marked, **Element
+   gone** when it leaves the page, **Done** when you say so.
+5. **Review the next version.** A new version waits on the preview pill instead
+   of reloading under you. Take it when you're ready, compare before and after,
+   inspect the diff and checks, and decide when the work is done.
+6. **Get a second opinion.** Share a preview link for 1 hour, 1 day, or 7 days.
+   Teammates and clients try the running app and leave notes without a Bivy
+   account. Make it view-only, or **Stop sharing** to end every link at once.
 
 On Bivy Cloud, preview delivery is built in: no per-app domains, certificates,
 public ports, or tunnels to configure. Self-hosters configure preview delivery
@@ -79,27 +88,13 @@ build or dev-server setup, and **the machine serving it must stay awake and
 online**. These are development previews, not production hosting.
 
 **Share deliberately:** anyone with a preview link can use that app, including
-its live backend. Links expire after 24 hours and can be revoked sooner.
+its live backend, until the link expires or you stop sharing.
 Reviewer notes aren't sent to the agent automatically; you send them or explicitly
 allow agent access. Preview traffic uses HTTPS through the preview relay, not
 session end-to-end encryption; the relay operator can see it.
 
 [App previews, visual feedback, and sharing →](docs/apps.md)
 
-## Your agents and machines, one workspace
-
-| Capability | What it means for you |
-|---|---|
-| **One workspace, multiple agents** | Use different agents and models for different tasks without maintaining a separate workflow for each. |
-| **Your machines and environment** | Work beside your existing repos, dev servers, databases, private networks, toolchains, and GPUs. |
-| **Automations and triggers** | Let issues, failed CI, messages, schedules, and webhooks start work instead of copying requests into a chat. |
-| **Encrypted key and OAuth sync** | Reuse Bivy-managed provider credentials across enrolled machines and compatible runtimes, with less repeated setup. |
-| **Live sessions from anywhere** | Build and review from your phone, browser, or terminal; answer questions and approve supported actions in the same session. |
-| **Live app previews** | Try the running app without deploying it to a separate hosting service. |
-| **Visual feedback and sharing** | Point, draw, and send specific feedback to the agent; share a preview link for outside review. |
-| **Reviewable results** | Inspect the app, changes, declared checks, artifacts, and pull requests—not just an agent's claim that it finished. |
-| **Hosted convenience or self-hosting** | Use Bivy Cloud for managed remote access, or run the same open-source core yourself. |
-
 ## One workflow, from trigger to review
 
 ```text
@@ -131,34 +126,70 @@ creates runs when an event matches.
 Manual and automated work use the same kind of live session. You can join a run
 when it needs help rather than wait for a black-box job to finish.
 
-### Work in the environment you already have
+### Let events start the work
 
-A clean cloud sandbox isn't always enough. Your agent may need the database
-running on localhost, an uncommitted change, an internal API behind your VPN,
-or a model running on your GPU. Bivy runs the agent where those things already
-exist, subject to that machine's permissions and the runtime's protection.
+Automations turn recurring or incoming work into sessions you can join,
+supervise, and review. An agent picks the task up on your machine and posts
+back a preview link or a pull request, so you try the result where the task
+lives and reply in the same session. Choose the repository, machine, agent,
+model, approval mode, sandbox setting, and maximum attempts.
 
-Connect several machines to the same account: a laptop for interactive work,
-a Linux server for background jobs, or a GPU box for local inference. Choose
-the machine for each session or pin it in an automation. Repository runs can
-use isolated Git worktrees without rebuilding the whole development environment.
+| Trigger | Example workflow |
+|---|---|
+| **GitHub issues and mentions** | Label an issue `bivy` or `bivy/<machine>`, or mention your Bivy GitHub App, to work toward a pull request. |
+| **Failed CI** | Match a failed workflow, ask the agent to reproduce it, make a fix, and run the affected checks. |
+| **Linear** | Label an issue to start work without copying its description into an agent. |
+| **Slack** | Send a request from the conversation where the work came up. |
+| **Schedules** | Run a weekly dependency review, recurring maintenance, or a one-time task. |
+| **Signed webhooks** | Connect alerts, internal tools, or your own event sources. |
 
-**The execution machine must stay awake and online.** To close your laptop and
-leave work running, run the agent on a different, always-on machine.
+Configure automations in the app or version them with your repository in
+`.bivy/automations.yaml`:
 
-[Environment and multi-machine recipes →](docs/capability-recipes.md)
+```bash
+bivy automation init
+# Edit the generated definition for your repository and workflow.
+bivy automation validate
+bivy automation test --event .bivy/events/failed-ci.yaml  # supply a local event fixture
+bivy automation apply
+```
 
-### Use multiple agents, not multiple disconnected workflows
+Or delegate a one-off job without creating an automation:
 
-Run Claude Code for one task, Codex for another, and Pi or OpenCode where they
-fit. Bivy supplies the shared session, remote-access, automation, and review
-surfaces; your chosen agent still does the coding and uses your model provider.
+```bash
+bivy runs start "Review outdated dependencies and propose a small, tested update."
+bivy runs wait <id>
+```
+
+Runs keep routing and lifecycle evidence, check results, and output references
+in a reviewable Receipt. For unattended issue work, Bivy runs declared repository
+checks after the agent's turn; failed required checks fail the run even if the
+agent reports success. A completed process alone is not proof that the task
+succeeded.
 
+[Automation recipes →](docs/capability-recipes.md#let-events-start-runs) ·
+[Automations as code →](docs/automations-as-code.md) ·
+[Run outcomes and reliability limits →](docs/automation-runs.md)
+
+### Use every agent you pay for. Switch mid-task.
+
+Run Claude Code for one task, Codex for another, and Pi or OpenCode where they
+fit, side by side in one session list. Bivy supplies the shared session,
+remote-access, automation, and review surfaces; your chosen agent still does
+the coding and uses your model provider.
+
+- **Hit a usage limit? Keep going.** When a turn fails on a limit, fork the
+  session, with its code and conversation, to another agent and model, or let
+  Bivy retry when the limit resets (the provider has to report a reset time).
+- **Get a second opinion.** `bivy delegate` hands a task to another agent, on
+  the same machine or a different one, and brings back its answer, branch, and
+  PR. `--to codex,claude@linux` sends one task to several agents to compare.
 - Choose an agent and, where supported, a model for each session or run.
 - Import existing Claude Code and Codex sessions.
 - Fork or move work to another agent or machine when a different setup fits
   better. Continuation fidelity varies: some paths preserve native history,
-  while others replay portable turns or seed the destination with context.
+  while others replay portable turns or hand over a summary with the earlier
+  transcript as a local file.
 - Use agent-native logins, Bivy-managed credentials, or local inference.
   Bivy's custom OpenAI-compatible endpoint registry currently feeds Pi;
   other agents may need their own provider configuration.
@@ -199,48 +230,22 @@ hosted-provisioning custody grants are separate from ordinary encrypted sync.
 [Credentials guide →](docs/credentials-guide.md) ·
 [Key storage →](docs/key-management.md)
 
-### Let events start the work
-
-Automations turn recurring or incoming work into sessions you can join,
-supervise, and review. Choose the repository, machine, agent, model, approval
-mode, sandbox setting, and maximum attempts.
-
-| Trigger | Example workflow |
-|---|---|
-| **GitHub issues and mentions** | Label an issue `bivy` or `bivy/<machine>`, or mention your Bivy GitHub App, to work toward a pull request. |
-| **Failed CI** | Match a failed workflow, ask the agent to reproduce it, make a fix, and run the affected checks. |
-| **Linear** | Label an issue to start work without copying its description into an agent. |
-| **Slack** | Send a request from the conversation where the work came up. |
-| **Schedules** | Run a weekly dependency review, recurring maintenance, or a one-time task. |
-| **Signed webhooks** | Connect alerts, internal tools, or your own event sources. |
-
-Configure automations in the app or version them with your repository in
-`.bivy/automations.yaml`:
-
-```bash
-bivy automation init
-# Edit the generated definition for your repository and workflow.
-bivy automation validate
-bivy automation test --event .bivy/events/failed-ci.yaml  # supply a local event fixture
-bivy automation apply
-```
+### Work in the environment you already have
 
-Or delegate a one-off job without creating an automation:
+A clean cloud sandbox isn't always enough. Your agent may need the database
+running on localhost, an uncommitted change, an internal API behind your VPN,
+or a model running on your GPU. Bivy runs the agent where those things already
+exist, subject to that machine's permissions and the runtime's protection.
 
-```bash
-bivy runs start "Review outdated dependencies and propose a small, tested update."
-bivy runs wait <id>
-```
+Connect several machines to the same account: a laptop for interactive work,
+a Linux server for background jobs, or a GPU box for local inference. Choose
+the machine for each session or pin it in an automation. Repository runs can
+use isolated Git worktrees without rebuilding the whole development environment.
 
-Runs keep routing and lifecycle evidence, check results, and output references
-in a reviewable Receipt. For unattended issue work, Bivy runs declared repository
-checks after the agent's turn; failed required checks fail the run even if the
-agent reports success. A completed process alone is not proof that the task
-succeeded.
+**The execution machine must stay awake and online.** To close your laptop and
+leave work running, run the agent on a different, always-on machine.
 
-[Automation recipes →](docs/capability-recipes.md#let-events-start-runs) ·
-[Automations as code →](docs/automations-as-code.md) ·
-[Run outcomes and reliability limits →](docs/automation-runs.md)
+[Environment and multi-machine recipes →](docs/capability-recipes.md)
 
 ### Start at your desk. Continue anywhere.
 
@@ -269,6 +274,29 @@ in your browser; adding it to your home screen is optional.
 [Remote access →](docs/remote-access.md) ·
 [Voice, files, and terminal recipes →](docs/capability-recipes.md)
 
+### Agents can reach you, too
+
+Every session gets the `bivy` CLI, so any agent with a shell can talk back
+through the app, not only agents with their own built-in tools:
+
+```bash
+bivy notify "Tests are green, PR is up"     # chat card + phone push when you're away
+bivy ask "Ship to staging?" --option Yes --option No  # waits for your answer
+bivy attach report.png --caption "Before/after"       # show a file in the chat
+bivy suggest "Add a dark theme to settings"           # a next task you start in one tap
+bivy context --json                                   # session, workspace, machine, apps
+```
+
+`bivy help --json` lists every command, and with `BIVY_OUTPUT=json` failures
+come back as structured errors with distinct exit codes, so an agent can tell
+what went wrong and what to run next. `bivy guide` prints short playbooks for
+agents, and the same commands are served as MCP tools for agents that prefer
+them. Add your own standing instructions for
+every session in **Settings → Agent instructions**.
+
+[Commands for agents inside a session →](docs/cli-reference.md#inside-an-agent-session) ·
+[Agent instructions →](docs/agent-instructions.md)
+
 ## Get started
 
 ### Install
@@ -404,9 +432,9 @@ for the task, especially before enabling unattended work.
 
 ## Agents and everyday commands
 
-**Claude Code, Codex, Pi, and OpenCode are release-tested.** Additional adapters
-include Gemini CLI, Qwen Code, Goose, Aider, Cline, Crush, Cursor, GitHub Copilot,
-Grok, Amp, Auggie, Droid, Continue, Kilo Code, and Rovo Dev. Installation,
+**Claude Code, Codex, Pi, OpenCode, and Grok are release-tested.** Additional
+adapters include Gemini CLI, Qwen Code, Goose, Aider, Cline, Crush, Cursor, GitHub
+Copilot, Amp, Auggie, Droid, Continue, Kilo Code, and Rovo Dev. Installation,
 resume, model selection, and tool protection vary—see the
 [support matrix](docs/runtime-support-matrix.md) and [agent guides](docs/agents/README.md).
 

package/bin/bivy.mjs

@@ -2826,6 +2826,62 @@ async function cmdInstructions(args = []) {
   fail({ code: "usage", message: usage, exit: EXIT.usage });
 }
 
+// `bivy automation apply` inside an agent session: the node shows the user what
+// would change as an approval card and applies it only once they approve, with
+// this machine's account credential. `proposal <id> [--wait]` follows one.
+async function cmdAutomationProposal(args = []) {
+  const usage = "Usage (in an agent session): bivy automation apply [path] [--prune] [--timeout 90] [--json]\n       bivy automation proposal <id> [--wait] [--timeout 90] [--json]";
+  if (args.includes("-h") || args.includes("--help")) {
+    console.log(`${usage}\n\nInside an agent session, apply goes through this machine's approval mode: usually the user gets an approval card listing what would change and decides; with "never ask" it applies at once. The chat records what was applied. Waits up to --timeout seconds (default 90) for the answer; if it hasn't come, prints the proposal id to check later with 'bivy automation proposal <id> --wait'. The card stays open for 30 minutes. Validate and plan first ('bivy automation validate', 'plan').`);
+    return;
+  }
+  const json = wantsJson(args);
+  const fail = (error) => cliError(error, { json, paint: c.red });
+  const parsed = parseSessionArgs(args, ["--timeout", "--session"]);
+  if (parsed.error) return fail({ code: "usage", message: parsed.error, exit: EXIT.usage });
+  const sessionId = resolveAttachSessionId({ sessionFlag: parsed.one("--session"), env: process.env });
+  if (!sessionId) return fail({ code: "no_session", message: "No session id.", next: "bivy sessions --json", exit: EXIT.usage });
+  const timeout = parsed.one("--timeout") === undefined ? 90 : durationSeconds(parsed.one("--timeout"));
+  if (!Number.isFinite(timeout) || timeout < 0) return fail({ code: "usage", message: "--timeout takes seconds or a duration like 90s or 10m.", exit: EXIT.usage });
+  const base = `/api/session/${encodeURIComponent(sessionId)}/automations/apply`;
+  const [action, target] = parsed.positional;
+  let proposal;
+  if (action === "proposal") {
+    if (!target) return fail({ code: "usage", message: usage, exit: EXIT.usage });
+    const { status, body } = await nodeRequest("GET", `${base}/${encodeURIComponent(target)}`, undefined, { json, sessionId });
+    if (status >= 400) return fail({ code: status === 404 ? "not_found" : "failed", message: body.error || `HTTP ${status}`, exit: status === 404 ? EXIT.notFound : EXIT.failed });
+    proposal = body;
+    if (!parsed.has("--wait")) { if (json) console.log(JSON.stringify(proposal)); else console.log(`Proposal ${proposal.id}: ${proposal.status}`); return; }
+  } else {
+    const file = path.resolve(process.cwd(), target ?? ".bivy/automations.yaml");
+    const { status, body } = await nodeRequest("POST", base, { file, prune: parsed.has("--prune") }, { json, sessionId });
+    if (status === 404 && !body.error?.includes("Session")) return fail({ code: "node_outdated", message: "This node is older than proposing automations from a session.", next: "bivy update", exit: EXIT.unavailable });
+    if (status >= 400) return fail(sessionHttpError("Proposing the automations", status, body));
+    proposal = body;
+    if (!json) {
+      console.error(`Changes to apply (${proposal.file}):`);
+      for (const change of proposal.changes) console.error(`  ${change.action === "create" ? "+" : change.action === "remove" ? "-" : "~"} ${change.id}`);
+    }
+  }
+  const deadline = Date.now() + timeout * 1000;
+  let polls = 0;
+  while (proposal.status === "pending" && Date.now() < deadline) {
+    await new Promise((resolve) => setTimeout(resolve, polls === 0 ? 500 : 2000));
+    if (polls++ === 1 && !json) console.error("Waiting for the user to approve them…");
+    const { status, body } = await nodeRequest("GET", `${base}/${encodeURIComponent(proposal.id)}`, undefined, { json, sessionId });
+    if (status < 400) proposal = body;
+  }
+  if (json) console.log(JSON.stringify(proposal));
+  if (proposal.status === "applied") { if (!json) console.log(proposal.output || "Applied."); return; }
+  if (proposal.status === "pending") {
+    if (!json) console.log(`The user hasn't answered yet. Check later with: bivy automation proposal ${proposal.id} --wait`);
+    process.exit(EXIT.timeout);
+  }
+  const message = { rejected: "The user declined these automation changes.", expired: "Nobody answered within 30 minutes; nothing was applied.", failed: `Approved, but applying failed: ${proposal.error || "unknown error"}` }[proposal.status] ?? proposal.status;
+  if (!json) console.error(message);
+  process.exit(proposal.status === "expired" ? EXIT.timeout : EXIT.failed);
+}
+
 // Cross-agent / cross-machine delegation (docs/agent-delegation.md): hand a
 // self-contained task from this session to another agent, optionally on another
 // account machine, and get its answer back. Agent-agnostic — any agent with a
@@ -6081,6 +6137,11 @@ Unlike 'bivy run', these commands operate on governed background Runs with check
       break;
     }
     case "automation": {
+      // An agent's apply is a proposal the user approves (see cmdAutomationProposal).
+      if ((args[0] === "apply" && !args.includes("--dry-run") && !process.env.BIVY_AUTOMATION_DIRECT && resolveAttachSessionId({ env: process.env })) || args[0] === "proposal") {
+        await cmdAutomationProposal(args);
+        break;
+      }
       if (!(await ensureDeps())) process.exit(1);
       process.exit(await run(nodeBin, [...nodeScriptArgs(automationEntry), ...args], { cwd: process.cwd(), env: process.env }));
       break;

package/bin/cli-commands.mjs

@@ -78,7 +78,11 @@ export const COMMANDS = [
 
   // Runs and automations
   { name: "runs", group: "runs", scope: "account", json: true, usage: 'runs <start|list|status|wait>', summary: "Unattended Runs with checks, evidence and a Receipt", subcommands: ["start", "list", "status", "wait"] },
-  { name: "automation", aliases: ["automations"], group: "runs", scope: "account", json: true, usage: "automation <list|trigger|init|validate|plan|test|apply>", summary: "Automations as code: validate, plan, apply, trigger", subcommands: ["list", "trigger", "init", "validate", "plan", "test", "test-filter", "apply"] },
+  { name: "automation", aliases: ["automations"], group: "runs", scope: "account", json: true, usage: "automation <list|trigger|init|validate|plan|test|apply>", summary: "Automations as code: validate, plan, apply, trigger", subcommands: ["list", "trigger", "init", "validate", "plan", "test", "test-filter", "apply", "proposal"],
+    tools: [
+      { name: "automation_plan", description: "Check an automations file (.bivy/automations.yaml) and show what each automation would do: trigger, routing, effective safety. Run it before automation_apply.", input: { path: { type: "string", description: "The automations file (default .bivy/automations.yaml)." } }, argv: ["automation", "plan", { arg: "path" }] },
+      { name: "automation_apply", description: "Propose applying an automations file to the user's account. They get an approval card listing each change; nothing is applied unless they approve. Returns the proposal: status applied, rejected, expired, failed, or pending (check later with bivy automation proposal <id> --wait).", input: { path: { type: "string", description: "The automations file (default .bivy/automations.yaml)." }, prune: { type: "boolean", description: "Also remove automations this file no longer has." } }, argv: ["automation", "apply", { arg: "path" }, { when: "prune", flag: "--prune" }] },
+    ] },
 
   // This node
   { name: "setup", aliases: ["init"], group: "node", scope: "node", usage: "setup", summary: "First-run wizard: agent, model login, remote sign-in, background service" },

package/bin/guides/automate.md

@@ -9,11 +9,35 @@ infrastructure code:
     bivy automation validate                       # check it
     bivy automation plan --json                    # triggers, routing, effective safety
     bivy automation test --event event.json        # which automation an event would start
-    bivy automation apply                          # reconcile the account with the file
+    bivy automation apply                          # ask the user, then apply
     bivy automation list --json
     bivy automation trigger <id-or-key>            # run one now
 
+A scheduled one (triggers: schedule, github, linear, webhook, manual; the
+format is in docs/automations-as-code.md):
+
+    version: 1
+    automations:
+      - id: nightly-tests
+        name: Nightly tests
+        trigger: schedule
+        schedule: { cron: "0 2 * * *", timezone: UTC }   # or { at: "2026-10-01T09:00:00Z" }
+        repo: owner/name                                  # required for schedules
+        instructions: |
+          Run the test suite. If it fails, open an issue with the failing tests.
+        safety:
+          approval: risky
+          sandbox: workspace-write
+
+From a session, `apply` goes through the machine's approval mode. Usually the
+user gets a card listing every change and decides. With "never ask" it applies
+at once, and the chat records what changed either way. The command waits up to
+90 seconds for an answer and prints apply's output once it's applied (exit 0). Exit 1 means they declined
+(don't retry the same thing), and exit 5 means they haven't answered yet: carry
+on, and check later with `bivy automation proposal <id> --wait`.
+`apply --dry-run` shows the changes without asking anyone.
+
 To pause one, set `enabled: false` on it and apply. Always `validate` and
-`plan` before `apply`, and show the user the plan when it
-changes something they didn't ask for. `apply --prune` also removes automations
-the file no longer has. `bivy automation --help` has every flag.
+`plan` first, and say in the chat what the automation will do and when.
+`apply --prune` also removes automations the file no longer has.
+`bivy automation --help` has every flag.

package/dist/agent-instructions.js

@@ -49,6 +49,8 @@ export const BIVY_AGENT_NOTE = [
         '`bivy delegate "<self-contained task>" --agent <id> [--machine <name>] --wait` runs it there and prints ' +
         "its answer and any branch/PR; `--to codex,grok@<machine>` asks several to compare, `bivy delegate machines` " +
         "lists machines and their agents. Use your own sub-agents for everything else.",
+    "- Work that should run on its own later (on a schedule, or when CI fails or an issue arrives) is a Bivy automation: " +
+        "`bivy guide automate`. Applying one may ask the user first.",
     "- `bivy context` shows your session, workspace and published apps; `bivy guide` has short playbooks; " +
         "`bivy help` lists every command (`--json` for all).",
 ].join("\n");

package/dist/approval.js

@@ -30,7 +30,7 @@ export class ApprovalManager {
     }
     async request(input) {
         const request = {
-            id: randomUUID(),
+            id: input.id ?? randomUUID(),
             sessionId: input.sessionId,
             toolName: input.toolName,
             input: input.toolInput,

package/dist/apps/styles.css

@@ -727,7 +727,7 @@ input, textarea, select { font-family: inherit; font-size: 16px; }
 }
 .approval-fields { display: grid; gap: 6px; margin-bottom: 8px; }
 .approval-field-label { font-size: 11px; text-transform: uppercase; letter-spacing: 0.04em; color: var(--muted); }
-.approval-field-value { font-family: ui-monospace, SFMono-Regular, Menlo, monospace; font-size: 12.5px; overflow-wrap: anywhere; word-break: break-word; }
+.approval-field-value { font-family: ui-monospace, SFMono-Regular, Menlo, monospace; font-size: 12.5px; overflow-wrap: anywhere; word-break: break-word; white-space: pre-line; }
 .approval-raw-toggle { border: 0; background: transparent; color: var(--muted); font-size: 12px; padding: 0; margin-bottom: 8px; text-decoration: underline; }
 .approval-raw-toggle:hover { color: var(--ink); }
 .approval-summary { margin: 0 0 10px; background: var(--surface-2); border-radius: var(--radius-sm); padding: 8px 10px; overflow-x: auto; font-size: 12px; }

package/dist/automation-cli.js

@@ -32,7 +32,8 @@ Commands:
   plan [path] [--json]        Show triggers, routing, and effective safety
   test [path] --event <file>  Simulate an event and explain the first match
   test-filter [path] --id <key> --event <json>  Execute a trusted filter locally
-  apply [path] [--prune]      Encrypt instructions and reconcile the control plane
+  apply [path] [--prune] [--dry-run]  Encrypt instructions and reconcile the control plane
+                              (inside an agent session: proposed to the user first)
 
 Run commands (normally invoked as 'bivy runs ...'):
   start <instructions>          Queue definition-free unattended work
@@ -482,6 +483,27 @@ async function main() {
         const pairing = PairingStore.load(appDir, relay.e2eKey);
         const current = await request(relay, "/node/automation-config");
         const wanted = new Set(config.automations.map((a) => a.id));
+        // --dry-run: what apply would change, and nothing more. The node shows this
+        // on the approval card when an agent proposes automations.
+        if (args.includes("--dry-run")) {
+            const changes = [
+                ...config.automations.map((entry) => {
+                    const safety = effectiveSafety(entry, file);
+                    return {
+                        id: entry.id, action: current.automations.some((a) => a.configKey === entry.id) ? "update" : "create", name: entry.name, enabled: entry.enabled, trigger: entry.trigger,
+                        schedule: entry.schedule, workspace: entry.repo ?? (entry.repos?.length ? entry.repos.join(", ") : undefined),
+                        agent: entry.routing.agent ?? "node default", sandbox: safety.sandbox, approval: safety.approval,
+                    };
+                }),
+                ...(args.includes("--prune") ? current.automations.filter((a) => a.configKey && !wanted.has(a.configKey)).map((a) => ({ id: a.configKey, action: "remove" })) : []),
+            ];
+            if (args.includes("--json"))
+                console.log(JSON.stringify({ version: 1, changes }, null, 2));
+            else
+                for (const change of changes)
+                    console.log(`${change.action === "create" ? "+" : change.action === "remove" ? "-" : "~"} ${change.id}`);
+            return;
+        }
         let created = 0, updated = 0, removed = 0;
         for (const [configOrder, entry] of config.automations.entries()) {
             const exists = current.automations.some((a) => a.configKey === entry.id);

package/dist/certification/agent-ux.js

@@ -19,6 +19,8 @@ export function scoreAgentUx(expect, seen, vars = {}) {
         }
         if ("asked" in rule)
             return { expectation: "asked a question", passed: seen.asked };
+        if ("approval" in rule)
+            return { expectation: `asked to approve ${rule.approval}`, passed: seen.approvals.includes(rule.approval) };
         if ("reply" in rule) {
             const text = fill(rule.reply);
             return { expectation: `reply mentions "${text}"`, passed: seen.reply.toLowerCase().includes(text.toLowerCase()) };

package/dist/server.js

@@ -128,6 +128,7 @@ import { createArtifactCommands } from "./controllers/artifact-commands.js";
 import { PresenceBook, deviceFrom } from "./session/presence.js";
 import { buildAgentContext } from "./session/agent-context.js";
 import { AgentQuestions, askQuestionsFrom } from "./session/agent-questions.js";
+import { AutomationProposals, describeChange } from "./session/automation-proposals.js";
 import { createSessionTokenCodec, isSessionToken, sessionTokenAllows } from "./session/session-tokens.js";
 import { setSessionTokenSigner } from "./runtime/session-env.js";
 import { MAX_NOTICE_TEXT, isAgentNotice, noticePush } from "./session/notices.js";
@@ -412,6 +413,46 @@ setSessionTokenSigner(sessionTokens.sign);
 // them, and session.question(.resolved) is broadcast from its listeners.
 const questionManager = new QuestionManager();
 const agentQuestions = new AgentQuestions(questionManager);
+// `bivy automation apply` from an agent: an approval request like any other, so
+// the node's approval mode decides whether the user is asked ("never" applies
+// at once; autonomous asks, as for deploys). Either way the result lands in the
+// chat, and pushes when nobody was asked.
+const automationProposals = new AutomationProposals({
+    runCli: (args, cwd) => new Promise((resolve) => {
+        const cli = process.env.BIVY_NODE_CLI ?? path.join(repoRoot, "bin", "bivy.mjs");
+        const child = spawn(process.execPath, [cli, ...args], { cwd, env: { ...process.env, BIVY_DATA_DIR: appDir, BIVY_AUTOMATION_DIRECT: "1", NO_COLOR: "1" }, stdio: ["ignore", "pipe", "pipe"] });
+        let stdout = "";
+        let stderr = "";
+        child.stdout.on("data", (chunk) => { stdout += chunk; });
+        child.stderr.on("data", (chunk) => { stderr += chunk; });
+        child.on("error", (error) => resolve({ code: 1, stdout, stderr: error.message }));
+        child.on("close", (code) => resolve({ code: code ?? 1, stdout, stderr }));
+    }),
+    requestApproval: async ({ id, sessionId, file, changes, prune }) => {
+        const approved = await approvals.request({
+            id, sessionId, toolName: "apply_automations", timeoutMs: 30 * 60_000,
+            toolInput: { file, prune, changes: changes.map(describeChange) },
+            reason: "Automations run on their own, on your machines, until you turn them off.",
+        });
+        if (approved)
+            return "approved";
+        return approvals.list().find((request) => request.id === id)?.status === "expired" ? "expired" : "rejected";
+    },
+    applied: (proposal) => {
+        const record = openSessions.get(proposal.sessionId);
+        if (!record)
+            return;
+        const lines = proposal.changes.map(describeChange);
+        const text = `Applied automations from ${proposal.file}:\n${lines.join("\n")}`.slice(0, MAX_NOTICE_TEXT);
+        const notice = { id: `notice-${randomBytes(8).toString("hex")}`, text };
+        eventLog.appendNotice(record.id, { afterMessageCount: record.session.getMessages().length, notice });
+        broadcast(stampSessionEvent({ type: "session.event", sessionId: record.id, event: { type: "notice", id: notice.id, notice } }));
+        // Nobody was asked: make sure the user hears about it.
+        if (approvalMode === "never") {
+            void sendNotificationHint({ kind: "agent_notice", sessionId: record.id, targetSessionId: record.id, title: sessionNotifyLabel(record), body: `Changed ${lines.length} automation${lines.length === 1 ? "" : "s"} on your account — tap to see what.` });
+        }
+    },
+});
 questionManager.onRequest((request) => {
     scheduleAdvertise();
     broadcast({ type: "session.question", sessionId: request.sessionId, requestId: request.id, questions: request.questions, createdAt: request.createdAt });
@@ -11607,6 +11648,23 @@ app.post("/api/session/:id/ask/:askId/wait", async (req, res) => {
         return res.status(404).json({ error: "Question not found" });
     res.json(result);
 });
+// `bivy automation apply` inside a session: propose, and follow the proposal.
+app.post("/api/session/:id/automations/apply", async (req, res) => {
+    const record = openSessions.get(String(req.params.id));
+    if (!record)
+        return res.status(404).json({ error: "Session not found" });
+    const file = typeof req.body?.file === "string" && req.body.file.trim() ? req.body.file.trim() : ".bivy/automations.yaml";
+    const result = await automationProposals.propose(record.id, harnessDirFor(record), file, req.body?.prune === true);
+    if ("error" in result)
+        return res.status(400).json({ error: result.error });
+    res.status(201).json(result);
+});
+app.get("/api/session/:id/automations/apply/:proposalId", (req, res) => {
+    const proposal = automationProposals.get(String(req.params.id), String(req.params.proposalId));
+    if (!proposal)
+        return res.status(404).json({ error: "Proposal not found" });
+    res.json(proposal);
+});
 // `bivy suggest "<task>"`: the agent proposes a task the user can start in one
 // tap, here or in a parallel session (see packages/web SuggestionCard).
 app.post("/api/session/:id/suggest", (req, res) => {

package/dist/session/automation-proposals.js

@@ -0,0 +1,87 @@
+// SPDX-License-Identifier: AGPL-3.0-only
+// Copyright (c) 2026 Petter André Sjulstad
+import fs from "node:fs";
+import path from "node:path";
+import { randomUUID } from "node:crypto";
+/** One line per change, for the card and the CLI. */
+export function describeChange(change) {
+    if (change.action === "remove")
+        return `Remove ${change.id}`;
+    const when = change.schedule?.kind === "cron" ? `${change.schedule.expression} (${change.schedule.timezone})` : change.schedule?.kind === "once" ? `once at ${change.schedule.at}` : change.trigger ?? "";
+    const verb = change.action === "create" ? "Add" : "Update";
+    return `${verb} ${change.name ?? change.id}${change.enabled === false ? " (off)" : ""}: ${when}${change.workspace ? ` in ${change.workspace}` : ""}, ${change.agent}, ${change.sandbox}, approvals ${change.approval}`;
+}
+/** `file` resolved inside `workspace`, or an error: an agent can only propose its own workspace's files. */
+export function confinedFile(workspace, file) {
+    let root;
+    let abs;
+    try {
+        root = fs.realpathSync(workspace);
+        abs = fs.realpathSync(path.resolve(workspace, file));
+    }
+    catch {
+        return { error: `No such file: ${file}` };
+    }
+    const rel = path.relative(root, abs);
+    if (!rel || rel.startsWith("..") || path.isAbsolute(rel))
+        return { error: "The automations file must be inside the session workspace." };
+    return { abs, rel };
+}
+const KEEP_MS = 24 * 60 * 60 * 1000;
+export class AutomationProposals {
+    deps;
+    now;
+    proposals = new Map();
+    constructor(deps, now = Date.now) {
+        this.deps = deps;
+        this.now = now;
+    }
+    /** Check the file, work out the changes, and put the card in front of the user. */
+    async propose(sessionId, workspace, file, prune) {
+        this.prune();
+        const target = confinedFile(workspace, file);
+        if ("error" in target)
+            return target;
+        const dry = await this.deps.runCli(["automation", "apply", target.abs, "--dry-run", "--json", ...(prune ? ["--prune"] : [])], workspace);
+        if (dry.code !== 0)
+            return { error: (dry.stderr || dry.stdout).trim().replace(/^Automation error: /, "") || "The automations file could not be checked." };
+        let changes;
+        try {
+            changes = JSON.parse(dry.stdout).changes;
+        }
+        catch {
+            return { error: "Unexpected output from automation apply --dry-run." };
+        }
+        if (!changes.length)
+            return { error: "The file has no automations to apply." };
+        const proposal = { id: randomUUID(), sessionId, status: "pending", file: target.rel, changes };
+        this.proposals.set(proposal.id, proposal);
+        void this.deps.requestApproval({ id: proposal.id, sessionId, file: target.rel, changes, prune }).then(async (decision) => {
+            if (decision === "approved") {
+                const run = await this.deps.runCli(["automation", "apply", target.abs, ...(prune ? ["--prune"] : [])], workspace);
+                proposal.status = run.code === 0 ? "applied" : "failed";
+                proposal.output = run.stdout.trim();
+                if (run.code !== 0)
+                    proposal.error = run.stderr.trim().replace(/^Automation error: /, "");
+                else
+                    this.deps.applied?.(this.view(proposal));
+            }
+            else
+                proposal.status = decision;
+            proposal.settledAt = this.now();
+        });
+        return this.view(proposal);
+    }
+    get(sessionId, id) {
+        const proposal = this.proposals.get(id);
+        return proposal && proposal.sessionId === sessionId ? this.view(proposal) : undefined;
+    }
+    view({ settledAt: _settledAt, ...proposal }) {
+        return structuredClone(proposal);
+    }
+    prune() {
+        for (const [id, proposal] of this.proposals)
+            if (proposal.settledAt !== undefined && this.now() - proposal.settledAt > KEEP_MS)
+                this.proposals.delete(id);
+    }
+}

package/dist/session/session-tokens.js

@@ -51,6 +51,8 @@ export const SESSION_TOKEN_ROUTES = [
     { method: "POST", path: /^\/api\/session\/([^/]+)\/delegated-runs$/, session: "path" },
     { method: "GET", path: /^\/api\/session\/([^/]+)\/delegated-runs\/[^/]+$/, session: "path" },
     { method: "POST", path: /^\/api\/session\/([^/]+)\/delegated-runs\/[^/]+\/wait$/, session: "path" },
+    { method: "POST", path: /^\/api\/session\/([^/]+)\/automations\/apply$/, session: "path" },
+    { method: "GET", path: /^\/api\/session\/([^/]+)\/automations\/apply\/[^/]+$/, session: "path" },
     { method: "POST", path: /^\/api\/apps\/[a-zA-Z]+$/, session: "body" },
     { method: "POST", path: /^\/api\/session\/fork$/, session: "body" },
     { method: "GET", path: /^\/api\/machines$/, session: "none" },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bivy/bivy",
-  "version": "0.19.4-staging.6",
+  "version": "0.20.0-staging.1",
   "type": "module",
   "license": "AGPL-3.0-only",
   "description": "Run coding agents on machines you own. Open-source, self-hostable agent workspace.",
@@ -65,7 +65,7 @@
     "lodash-es": "4.18.1",
     "undici": "8.11.2"
   },
-  "readme": "# Bivy\n\n[![npm](https://img.shields.io/npm/v/@bivy/bivy?color=2b6cb0&label=%40bivy%2Fbivy)](https://www.npmjs.com/package/@bivy/bivy)\n[![license: AGPL-3.0-only](https://img.shields.io/badge/license-AGPL--3.0--only-2b6cb0)](LICENSE)\n[![node](https://img.shields.io/badge/node-%E2%89%A520-2b6cb0)](https://nodejs.org)\n\n**Build, try, and review apps from your phone. Your coding agent and dev\nenvironment stay on your own machines.**\n\nBivy is an open-source remote development environment built around coding\nagents. Ask for a change, try the running app, and point to or draw on what\nneeds fixing. Send that feedback to the agent and try again—all in the same\nsession, without going back to your computer.\n\nLive previews bring your app to your phone or browser without deploying it to\nRender, building a Docker image, or setting up a separate preview server.\nShare a preview link so someone else can try it and leave notes, too.\n\nKeep Claude Code, Codex, Pi, OpenCode, or another supported agent. Keep your\nrepos, tools, databases, and development environment. Bivy connects them to\nchat, a terminal, app previews, and code review wherever you are. Start work\nyourself, or let an issue, CI failure, message, schedule, or webhook start it.\n\n**[Start free on Bivy Cloud](https://app.bivy.sh)** ·\n**[Quickstart](docs/quickstart.md)** ·\n**[Documentation](docs/README.md)** ·\n**[Self-host](docs/deploy-images.md)** ·\n**[Website](https://bivy.sh)**\n\n**Recommended:** sign in at [app.bivy.sh](https://app.bivy.sh), then copy your\npersonalized **Connect a Machine** command into a terminal on your Mac or Linux\ncomputer. It installs and enrolls the machine without another Bivy login. The\nbrowser connects automatically; choose a repository and send your first task\nright there.\n\nPrefer starting from the terminal?\n\n```bash\ncurl -fsSL https://bivy.sh/install.sh | bash  # install + guided setup\ncd your-repo\nbivy run claude                            # or codex, pi, opencode\nbivy open                                  # continue in the web app (needs remote setup)\n```\n\nBivy Cloud hosts the app, control plane, and relay—not the machines running your\nagents. Connect a Mac, Linux computer, or existing server and bring your own\nagent subscription, model API key, or local model. You can also self-host the\nentire remote-access stack.\n\n> **Bivy is 0.x software.** Claude Code, Codex, Pi, and OpenCode are the\n> release-tested paths. Credential sync, resume, handoffs, approvals, and\n> sandboxing depend on the runtime. See the\n> [runtime support matrix](docs/runtime-support-matrix.md).\n\n## Build → preview → mark up → iterate\n\nRemote chat lets you ask an agent for a change. Bivy also lets you **use what\nit built and show it what to fix**, without a separate deployment step.\n\n1. **Ask for a change.** The agent works in your repo with your existing tools\n   and local services.\n2. **Try the app.** Open a live preview from the session. Use the running app,\n   not just a screenshot of what the agent says it finished. Bivy can discover\n   dev servers running in the session workspace; tap **Preview** to open one.\n3. **Mark up what needs work.** Point at an element or circle and draw on the\n   preview. Add a note, then send the draft to the agent with the element and\n   page context. Marked-up screenshots and before/after comparison are available\n   when agent screenshots are enabled.\n4. **Iterate and review.** Try the next version, inspect the diff, review checks,\n   and decide when the work is ready—not just when the agent stops.\n5. **Bring someone else into the review.** Copy a public preview link so they\n   can use the app without a Bivy account and leave notes on specific elements.\n   Bring their notes into the session when you're ready to act on them.\n\nOn Bivy Cloud, preview delivery is built in: no per-app domains, certificates,\npublic ports, or tunnels to configure. Self-hosters configure preview delivery\nonce for their Bivy deployment, not for every app. The app still needs its normal\nbuild or dev-server setup, and **the machine serving it must stay awake and\nonline**. These are development previews, not production hosting.\n\n**Share deliberately:** anyone with a preview link can use that app, including\nits live backend. Links expire after 24 hours and can be revoked sooner.\nReviewer notes aren't sent to the agent automatically; you send them or explicitly\nallow agent access. Preview traffic uses HTTPS through the preview relay, not\nsession end-to-end encryption; the relay operator can see it.\n\n[App previews, visual feedback, and sharing →](docs/apps.md)\n\n## Your agents and machines, one workspace\n\n| Capability | What it means for you |\n|---|---|\n| **One workspace, multiple agents** | Use different agents and models for different tasks without maintaining a separate workflow for each. |\n| **Your machines and environment** | Work beside your existing repos, dev servers, databases, private networks, toolchains, and GPUs. |\n| **Automations and triggers** | Let issues, failed CI, messages, schedules, and webhooks start work instead of copying requests into a chat. |\n| **Encrypted key and OAuth sync** | Reuse Bivy-managed provider credentials across enrolled machines and compatible runtimes, with less repeated setup. |\n| **Live sessions from anywhere** | Build and review from your phone, browser, or terminal; answer questions and approve supported actions in the same session. |\n| **Live app previews** | Try the running app without deploying it to a separate hosting service. |\n| **Visual feedback and sharing** | Point, draw, and send specific feedback to the agent; share a preview link for outside review. |\n| **Reviewable results** | Inspect the app, changes, declared checks, artifacts, and pull requests—not just an agent's claim that it finished. |\n| **Hosted convenience or self-hosting** | Use Bivy Cloud for managed remote access, or run the same open-source core yourself. |\n\n## One workflow, from trigger to review\n\n```text\nPrompt · GitHub issue · CI failure · Linear · Slack · Schedule · Webhook\n                                 │\n                                 ▼\n                   Choose machine + agent + model\n                     + supported credentials\n                                 │\n                                 ▼\n                         Live agent session\n                     Join · steer · approve · stop\n                                 │\n                                 ▼\n                  Try app · inspect changes · checks\n                                 │\n                                 ▼\n                  Mark up · send feedback · iterate\n                                 │\n                                 ▼\n                      Share preview · review PR\n```\n\nA **Machine** is a computer or server you connect. A **Session** is live agent\nwork on that machine. A **Run** is delegated background work that creates a\nsession and tracks its outcome. An **Automation** is a reusable definition that\ncreates runs when an event matches.\n\nManual and automated work use the same kind of live session. You can join a run\nwhen it needs help rather than wait for a black-box job to finish.\n\n### Work in the environment you already have\n\nA clean cloud sandbox isn't always enough. Your agent may need the database\nrunning on localhost, an uncommitted change, an internal API behind your VPN,\nor a model running on your GPU. Bivy runs the agent where those things already\nexist, subject to that machine's permissions and the runtime's protection.\n\nConnect several machines to the same account: a laptop for interactive work,\na Linux server for background jobs, or a GPU box for local inference. Choose\nthe machine for each session or pin it in an automation. Repository runs can\nuse isolated Git worktrees without rebuilding the whole development environment.\n\n**The execution machine must stay awake and online.** To close your laptop and\nleave work running, run the agent on a different, always-on machine.\n\n[Environment and multi-machine recipes →](docs/capability-recipes.md)\n\n### Use multiple agents, not multiple disconnected workflows\n\nRun Claude Code for one task, Codex for another, and Pi or OpenCode where they\nfit. Bivy supplies the shared session, remote-access, automation, and review\nsurfaces; your chosen agent still does the coding and uses your model provider.\n\n- Choose an agent and, where supported, a model for each session or run.\n- Import existing Claude Code and Codex sessions.\n- Fork or move work to another agent or machine when a different setup fits\n  better. Continuation fidelity varies: some paths preserve native history,\n  while others replay portable turns or seed the destination with context.\n- Use agent-native logins, Bivy-managed credentials, or local inference.\n  Bivy's custom OpenAI-compatible endpoint registry currently feeds Pi;\n  other agents may need their own provider configuration.\n- Register your own ACP or headless process agent with `bivy agent add`.\n\nBivy does not replace your agent, provide model inference, or make every agent's\nfeatures identical. Consult the [support matrix](docs/runtime-support-matrix.md)\nand [handoff recipes](docs/capability-recipes.md#fork-or-move-a-session).\n\n### Less signing in. Less copying secrets.\n\nBivy syncs **Bivy-managed API keys and supported OAuth credentials** across\nenrolled machines for compatible runtimes. Connect supported credentials once\nand reuse them where you run work, rather than manually distributing keys to\neach machine.\n\nFor ordinary account sync, credentials are encrypted on the node before upload.\nThe control plane stores ciphertext and wrapped-key metadata; enrolled nodes\nshare access by wrapping the vault key to one another. Bivy Cloud does not\nreceive plaintext credentials through this sync path.\n\nYou can also keep credentials local, use labeled keys and project presets, or\nreference environment variables and 1Password instead of embedding secrets in\nconfiguration:\n\n```bash\nbivy provider login\nbivy credentials add anthropic work\nbivy secrets ref github.repo-token op://Bivy/GitHub/repo-token\n```\n\n**Not every CLI login syncs.** Native agent logins may still be per-machine;\nGitHub App private-key sync is separately opt-in. If you lose every node and\ndevice able to unwrap a vault, you must sign in to providers again. Explicit\nhosted-provisioning custody grants are separate from ordinary encrypted sync.\n\n[Credential sync and runtime coverage →](docs/credential-sync.md) ·\n[Credentials guide →](docs/credentials-guide.md) ·\n[Key storage →](docs/key-management.md)\n\n### Let events start the work\n\nAutomations turn recurring or incoming work into sessions you can join,\nsupervise, and review. Choose the repository, machine, agent, model, approval\nmode, sandbox setting, and maximum attempts.\n\n| Trigger | Example workflow |\n|---|---|\n| **GitHub issues and mentions** | Label an issue `bivy` or `bivy/<machine>`, or mention your Bivy GitHub App, to work toward a pull request. |\n| **Failed CI** | Match a failed workflow, ask the agent to reproduce it, make a fix, and run the affected checks. |\n| **Linear** | Label an issue to start work without copying its description into an agent. |\n| **Slack** | Send a request from the conversation where the work came up. |\n| **Schedules** | Run a weekly dependency review, recurring maintenance, or a one-time task. |\n| **Signed webhooks** | Connect alerts, internal tools, or your own event sources. |\n\nConfigure automations in the app or version them with your repository in\n`.bivy/automations.yaml`:\n\n```bash\nbivy automation init\n# Edit the generated definition for your repository and workflow.\nbivy automation validate\nbivy automation test --event .bivy/events/failed-ci.yaml  # supply a local event fixture\nbivy automation apply\n```\n\nOr delegate a one-off job without creating an automation:\n\n```bash\nbivy runs start \"Review outdated dependencies and propose a small, tested update.\"\nbivy runs wait <id>\n```\n\nRuns keep routing and lifecycle evidence, check results, and output references\nin a reviewable Receipt. For unattended issue work, Bivy runs declared repository\nchecks after the agent's turn; failed required checks fail the run even if the\nagent reports success. A completed process alone is not proof that the task\nsucceeded.\n\n[Automation recipes →](docs/capability-recipes.md#let-events-start-runs) ·\n[Automations as code →](docs/automations-as-code.md) ·\n[Run outcomes and reliability limits →](docs/automation-runs.md)\n\n### Start at your desk. Continue anywhere.\n\nOpen the same session in the browser, phone PWA, or terminal. Watch work live,\nanswer questions, approve supported tool calls, or stop the agent.\n\n- Send screenshots, images, logs, and other files from your phone.\n- Download reports and artifacts the agent creates.\n- Open [session apps](docs/apps.md) from chat or the **Apps** menu: live web\n  previews, desktop app views, and CLI/TUI tools. Agents can publish views with\n  `bivy app publish bivy.app.json` and create share links with `bivy app share`.\n- Use voice input and read-aloud where supported; provider-backed voice may\n  send audio or text to the selected provider.\n- Keep a native terminal workflow or use structured chat, depending on the agent.\n\n```bash\nbivy run claude --no-follow  # start without attaching\nbivy open                    # open the web app\nbivy resume                  # return to the session in your terminal\nbivy link                    # pair a device directly via QR\n```\n\nNo phone app installation is required. Open [app.bivy.sh](https://app.bivy.sh)\nin your browser; adding it to your home screen is optional.\n\n[Remote access →](docs/remote-access.md) ·\n[Voice, files, and terminal recipes →](docs/capability-recipes.md)\n\n## Get started\n\n### Install\n\nBivy supports **macOS and Linux with Node.js 20+**. The installer installs the\n`@bivy/bivy` package, runs guided setup, and starts a launchd or systemd service:\n\n```bash\ncurl -fsSL https://bivy.sh/install.sh | bash\n```\n\nSetup helps you choose an agent and configure remote access. Existing agents\nkeep their command, login, and configuration. The installer may use `sudo` to\ninstall a missing Node.js, but never for `npm install`. To inspect it first,\ndownload it with `curl -fsSL https://bivy.sh/install.sh -o install.sh`.\n\nAlready have Node.js and want to avoid sudo?\n\n```bash\nnpm install -g @bivy/bivy\nbivy setup\n```\n\nThen try one small task:\n\n```bash\ncd your-repo\nbivy run claude\n# Ask: \"Explain this repo and make one small, safe improvement. Run the relevant checks.\"\nbivy open\n```\n\nOpen that same session on your phone while it runs. For a web app, ask the agent\nto start its dev server, then open **Apps → Running in this workspace → Preview**.\nTry a page, point to something you'd change, and send the feedback back to the\nagent. No separate preview deployment needed.\n\nOnce that works, share a preview for review, connect another machine, or add\nyour first automation.\n\n**Local-only works too.** `bivy run`, `bivy resume`, and `bivy sessions` need no\naccount or server. Choose **local only for now** during setup; use `bivy login`\nlater. Browser and phone access need a hosted or self-hosted control plane;\nthe node itself does not serve a web UI.\n\n[Full quickstart →](docs/quickstart.md) ·\n[Installer options, service management, and uninstall →](docs/install.md)\n\n### Choose hosted or self-hosted\n\n| Option | What you get |\n|---|---|\n| **Free Cloud — $0** | Every launch feature, including automations; 10 new remote sessions per rolling seven days. No credit card required. |\n| **Cloud — $15/month** | The same features with unlimited remote sessions. |\n| **Self-hosted Core** | Operate the app, control plane, and relay yourself, with no Bivy usage limits. |\n\nManual and automated sessions share the Cloud allowance. Resuming existing\nsessions and viewing history do not consume it. Agent subscriptions and model\nprovider charges are separate. See [current pricing](https://bivy.sh#pricing).\n\n**Self-host anywhere:** deploy the public control-plane (including the web app)\nand relay images with Postgres and [a small set of environment variables](docs/deploy-images.md).\nYour server or container platform handles HTTPS. Set up owner access in the\nbrowser—no SSH, external authentication provider, or Bivy Cloud account required.\nFor a bare VPS, the [Compose installer](docs/self-host-quickstart.md) automates the\nsame stack. These onboarding features require a release containing them.\n\nStart on Cloud and self-host later if you prefer. Deploy the stack, reconnect\nmachines with `bivy relay:setup`, and pair devices to your server. This is not a\none-click migration of your Cloud account; your local repos and agent\nconfiguration stay in place.\n\n```bash\nbivy relay:setup \\\n  --control-plane https://bivy.example.com \\\n  --relay wss://relay.example.com\n```\n\nSelf-hosting is community-supported: you own TLS, backups, upgrades, and\nhardening. Public multi-architecture images are available as\n`ghcr.io/bivysh/bivy-control-plane` and `ghcr.io/bivysh/bivy-relay`; pin a release\nversion or full commit SHA.\n\n[Deploy the images anywhere →](docs/deploy-images.md) ·\n[Optional VPS installer →](docs/self-host-quickstart.md) ·\n[Operations reference →](docs/self-host.md)\n\n## Architecture\n\nYour environment, with clear security boundaries:\n\n```text\nYour machine                         Hosted or self-hosted\n┌──────────────────────┐             ┌──────────────────────┐\n│ Node daemon          │──outbound──▶│ Relay                │\n│ Agents, repos, tools │             │ Encrypted frames     │\n│ Local credentials    │             └──────────┬───────────┘\n└──────────────────────┘                        │\n                                    Browser / phone\n                                    + control plane\n                                    (app, accounts, metadata)\n```\n\n- **Execution stays on your machine.** Bivy Cloud does not run your agents.\n  Your model provider still sees whatever the agent sends it.\n- **Interactive session traffic is end-to-end encrypted** between the node and\n  paired devices. The relay forwards opaque session frames; your node dials out,\n  so no inbound public port is required.\n- **App previews have a separate security boundary.** Preview traffic uses HTTPS\n  and an outbound tunnel, not session E2E encryption. The preview ingress/relay\n  operator can see it. Public preview links grant anyone holding them access to\n  that view and its live backend until expiry or revocation. See\n  [preview security and sharing](docs/apps.md#runtime-and-security-boundaries).\n- **Ordinary credential sync uploads ciphertext, not plaintext keys.**\n  Supported credentials and recovery limits are documented separately.\n- **Encryption is not universal across integrations.** Slack commands and\n  generic webhook instructions reach the control plane in plaintext. Do not\n  put secrets in them. Routing and bounded run metadata are also visible there.\n- **Device authorization matters.** QR pairing authorizes a device directly\n  through the node. Hosted account pairing trusts the control plane to authorize\n  devices and serve the web app that holds client keys.\n- **Bivy is not an OS-level sandbox.** The default approval mode is\n  `autonomous`; protection depends on the runtime. Some agents enforce sandbox\n  tiers, while process agents may run with your full user permissions.\n  Heuristic tool checks help prevent accidents but are not isolation.\n\nReview the runtime's Protection label and configure approval/sandbox settings\nfor the task, especially before enabling unattended work.\n\n[Security model and known limitations →](docs/security-model.md) ·\n[Runtime protection matrix →](docs/runtime-support-matrix.md) ·\n[Configuration →](docs/configuration.md)\n\n## Agents and everyday commands\n\n**Claude Code, Codex, Pi, and OpenCode are release-tested.** Additional adapters\ninclude Gemini CLI, Qwen Code, Goose, Aider, Cline, Crush, Cursor, GitHub Copilot,\nGrok, Amp, Auggie, Droid, Continue, Kilo Code, and Rovo Dev. Installation,\nresume, model selection, and tool protection vary—see the\n[support matrix](docs/runtime-support-matrix.md) and [agent guides](docs/agents/README.md).\n\nRun an arbitrary command with `bivy run -- ./your-agent --flags`, register a\nreusable entry with `bivy agent add`, or package a declarative integration with\nexperimental [plugins](docs/plugins.md).\n\n```bash\nbivy run claude       # launch a durable session; also codex, pi, opencode\nbivy sessions         # list live and saved sessions\nbivy resume           # resume the most recent session\nbivy open             # open the web app (requires remote setup)\nbivy nodes            # list connected account machines\nbivy runs list        # inspect delegated work\nbivy automation init  # scaffold repo-owned automations\nbivy provider login   # connect supported model credentials\nbivy agent add        # register an ACP or process agent\nbivy doctor           # check installation and connectivity\nbivy logs -f          # follow node logs\nbivy update           # update and restart the service\n```\n\n`bivy update` uses your original installation method and waits for an active\nturn to finish before restarting. Use `--force` to skip that wait.\n\n[CLI reference →](docs/cli-reference.md) ·\n[Node and project configuration →](docs/config-as-code.md) ·\n[GitHub setup →](docs/github-setup.md) ·\n[Linear setup →](docs/linear-work-queue.md)\n\n## Development and contributions\n\n```bash\npnpm install\npnpm run dev          # node daemon on http://localhost:4317\npnpm run dev:web      # web client dev server\n```\n\n| Directory | Contents |\n|---|---|\n| `src/`, `bin/` | Node daemon, CLI, runtime adapters, sessions, approvals, secrets |\n| `packages/core/` | Shared protocol, pairing, and wire format |\n| `packages/web/`, `packages/ui/` | React PWA and shared design system |\n| `services/relay/` | Self-hostable encrypted relay |\n| `services/control-plane/` | Self-hostable control plane |\n| `deploy/` | Deployment examples |\n\n```bash\npnpm run typecheck\npnpm run typecheck:web\npnpm run lint\npnpm run test:unit\npnpm run test:core\npnpm run check:licenses\npnpm run check:secrets\n```\n\nSee [CONTRIBUTING.md](CONTRIBUTING.md) for the development workflow. Releases\nare published from CI with provenance attestations; see\n[release verification](docs/releasing.md).\n\n**Found a security issue?** Use\n[GitHub private vulnerability reporting](https://github.com/bivysh/bivy/security/advisories/new),\nnot a public issue. See [SECURITY.md](SECURITY.md).\n\n### In development—not available at launch\n\nAutomatically provisioned, short-lived **ephemeral machines** are in development\nfor hosted and bring-your-own-cloud deployments. Neither path is ready or\nsupported for this launch. Use an existing computer or server you operate.\nExperimental provisioning has different credential-custody and encryption\nboundaries; see the [provisioning trust model](docs/hosted-provisioning-trust-model.md).\n\n## License\n\nEverything in this repository—node, CLI, web/PWA, relay, and control plane—is\nfree and open-source **AGPL-3.0-only Core**, with no Bivy usage limits. You may\nuse, modify, and self-host it under that license. If users interact with your\nmodified version over a network, section 13 requires you to offer its\ncorresponding source. See [LICENSE](LICENSE).\n\nBivy Cloud is the hosted operation of that stack plus billing and plans, in a\nseparate private repository. Contributions use the\n[DCO](CONTRIBUTING.md#certificate-of-origin); there is no CLA.\n",
+  "readme": "# Bivy\n\n[![npm](https://img.shields.io/npm/v/@bivy/bivy?color=2b6cb0&label=%40bivy%2Fbivy)](https://www.npmjs.com/package/@bivy/bivy)\n[![license: AGPL-3.0-only](https://img.shields.io/badge/license-AGPL--3.0--only-2b6cb0)](LICENSE)\n[![node](https://img.shields.io/badge/node-%E2%89%A520-2b6cb0)](https://nodejs.org)\n\n**Local coding agents that show their work. Anywhere.**\n\nBivy is the open-source workspace for coding agents. It runs Claude Code, Codex,\nPi, OpenCode and other agents on your own machine. Reach them from a browser or\nyour phone, with the live session, its terminal, its approvals, and the app\nthey're building right in the chat. Try it, mark what's wrong, and send it back.\n\nBivy is not another coding agent and not a cloud development machine. The agent\nstays local and does the coding with your model provider. Your repos, tools,\ndatabases, and services stay where they are. Bivy gives you remote access to all\nof it, plus live previews, automations, and review.\n\n- **Live previews.** The running app beside the chat. Mark it, send it back,\n  share it with someone who has no Bivy account.\n- **Automations.** GitHub issues, failed CI, Linear, Slack, schedules, and\n  webhooks start the work. It comes back as a preview link or a pull request.\n- **Any agent.** Hit a usage limit? Fork the session to another agent, or let\n  Bivy retry when the limit resets.\n- **Your machine, anywhere.** Start at your desk, pick the session up on your\n  phone. The machine dials out, so there are no ports to open, and session\n  traffic is end-to-end encrypted.\n\n**[Start free on Bivy Cloud](https://app.bivy.sh)** ·\n**[Quickstart](docs/quickstart.md)** ·\n**[Documentation](docs/README.md)** ·\n**[Self-host](docs/deploy-images.md)** ·\n**[Website](https://bivy.sh)**\n\n**Recommended:** sign in at [app.bivy.sh](https://app.bivy.sh), then copy your\npersonalized **Connect a Machine** command into a terminal on your Mac or Linux\ncomputer. It installs and enrolls the machine without another Bivy login. The\nbrowser connects automatically; choose a repository and send your first task\nright there.\n\nPrefer starting from the terminal?\n\n```bash\ncurl -fsSL https://bivy.sh/install.sh | bash  # install + guided setup\ncd your-repo\nbivy run claude                            # or codex, pi, opencode\nbivy open                                  # continue in the web app (needs remote setup)\n```\n\nBivy Cloud hosts the app, control plane, and relay—not the machines running your\nagents. Connect a Mac, Linux computer, or existing server and bring your own\nagent subscription, model API key, or local model. You can also self-host the\nentire remote-access stack.\n\n> **Bivy is 0.x software.** Claude Code, Codex, Pi, OpenCode, and Grok are the\n> release-tested paths. Credential sync, resume, handoffs, approvals, and\n> sandboxing depend on the runtime. See the\n> [runtime support matrix](docs/runtime-support-matrix.md).\n\n## Don't just read the diff. Try the app.\n\nBivy lets you **use what the agent built and show it what to fix**, without a\nseparate deployment step.\n\n1. **Ask for a change.** The agent works in your repo with your existing tools\n   and local services.\n2. **Try the app.** Bivy finds the dev server the agent starts and opens it\n   beside the chat: web apps, terminals, and desktop apps. Use the running app,\n   not a screenshot of what the agent says it finished.\n3. **Mark what needs work.** Press and hold anything in the preview to mark it,\n   or drag to circle it, then say what you want. **Mark another** keeps\n   separate notes separate. The marks go to the agent with the element and page\n   context. No screenshots to paste.\n4. **Follow each note.** Every mark stays in the chat as a pin that resolves\n   itself: **Changed** when a later run changes what you marked, **Element\n   gone** when it leaves the page, **Done** when you say so.\n5. **Review the next version.** A new version waits on the preview pill instead\n   of reloading under you. Take it when you're ready, compare before and after,\n   inspect the diff and checks, and decide when the work is done.\n6. **Get a second opinion.** Share a preview link for 1 hour, 1 day, or 7 days.\n   Teammates and clients try the running app and leave notes without a Bivy\n   account. Make it view-only, or **Stop sharing** to end every link at once.\n\nOn Bivy Cloud, preview delivery is built in: no per-app domains, certificates,\npublic ports, or tunnels to configure. Self-hosters configure preview delivery\nonce for their Bivy deployment, not for every app. The app still needs its normal\nbuild or dev-server setup, and **the machine serving it must stay awake and\nonline**. These are development previews, not production hosting.\n\n**Share deliberately:** anyone with a preview link can use that app, including\nits live backend, until the link expires or you stop sharing.\nReviewer notes aren't sent to the agent automatically; you send them or explicitly\nallow agent access. Preview traffic uses HTTPS through the preview relay, not\nsession end-to-end encryption; the relay operator can see it.\n\n[App previews, visual feedback, and sharing →](docs/apps.md)\n\n## One workflow, from trigger to review\n\n```text\nPrompt · GitHub issue · CI failure · Linear · Slack · Schedule · Webhook\n                                 │\n                                 ▼\n                   Choose machine + agent + model\n                     + supported credentials\n                                 │\n                                 ▼\n                         Live agent session\n                     Join · steer · approve · stop\n                                 │\n                                 ▼\n                  Try app · inspect changes · checks\n                                 │\n                                 ▼\n                  Mark up · send feedback · iterate\n                                 │\n                                 ▼\n                      Share preview · review PR\n```\n\nA **Machine** is a computer or server you connect. A **Session** is live agent\nwork on that machine. A **Run** is delegated background work that creates a\nsession and tracks its outcome. An **Automation** is a reusable definition that\ncreates runs when an event matches.\n\nManual and automated work use the same kind of live session. You can join a run\nwhen it needs help rather than wait for a black-box job to finish.\n\n### Let events start the work\n\nAutomations turn recurring or incoming work into sessions you can join,\nsupervise, and review. An agent picks the task up on your machine and posts\nback a preview link or a pull request, so you try the result where the task\nlives and reply in the same session. Choose the repository, machine, agent,\nmodel, approval mode, sandbox setting, and maximum attempts.\n\n| Trigger | Example workflow |\n|---|---|\n| **GitHub issues and mentions** | Label an issue `bivy` or `bivy/<machine>`, or mention your Bivy GitHub App, to work toward a pull request. |\n| **Failed CI** | Match a failed workflow, ask the agent to reproduce it, make a fix, and run the affected checks. |\n| **Linear** | Label an issue to start work without copying its description into an agent. |\n| **Slack** | Send a request from the conversation where the work came up. |\n| **Schedules** | Run a weekly dependency review, recurring maintenance, or a one-time task. |\n| **Signed webhooks** | Connect alerts, internal tools, or your own event sources. |\n\nConfigure automations in the app or version them with your repository in\n`.bivy/automations.yaml`:\n\n```bash\nbivy automation init\n# Edit the generated definition for your repository and workflow.\nbivy automation validate\nbivy automation test --event .bivy/events/failed-ci.yaml  # supply a local event fixture\nbivy automation apply\n```\n\nOr delegate a one-off job without creating an automation:\n\n```bash\nbivy runs start \"Review outdated dependencies and propose a small, tested update.\"\nbivy runs wait <id>\n```\n\nRuns keep routing and lifecycle evidence, check results, and output references\nin a reviewable Receipt. For unattended issue work, Bivy runs declared repository\nchecks after the agent's turn; failed required checks fail the run even if the\nagent reports success. A completed process alone is not proof that the task\nsucceeded.\n\n[Automation recipes →](docs/capability-recipes.md#let-events-start-runs) ·\n[Automations as code →](docs/automations-as-code.md) ·\n[Run outcomes and reliability limits →](docs/automation-runs.md)\n\n### Use every agent you pay for. Switch mid-task.\n\nRun Claude Code for one task, Codex for another, and Pi or OpenCode where they\nfit, side by side in one session list. Bivy supplies the shared session,\nremote-access, automation, and review surfaces; your chosen agent still does\nthe coding and uses your model provider.\n\n- **Hit a usage limit? Keep going.** When a turn fails on a limit, fork the\n  session, with its code and conversation, to another agent and model, or let\n  Bivy retry when the limit resets (the provider has to report a reset time).\n- **Get a second opinion.** `bivy delegate` hands a task to another agent, on\n  the same machine or a different one, and brings back its answer, branch, and\n  PR. `--to codex,claude@linux` sends one task to several agents to compare.\n- Choose an agent and, where supported, a model for each session or run.\n- Import existing Claude Code and Codex sessions.\n- Fork or move work to another agent or machine when a different setup fits\n  better. Continuation fidelity varies: some paths preserve native history,\n  while others replay portable turns or hand over a summary with the earlier\n  transcript as a local file.\n- Use agent-native logins, Bivy-managed credentials, or local inference.\n  Bivy's custom OpenAI-compatible endpoint registry currently feeds Pi;\n  other agents may need their own provider configuration.\n- Register your own ACP or headless process agent with `bivy agent add`.\n\nBivy does not replace your agent, provide model inference, or make every agent's\nfeatures identical. Consult the [support matrix](docs/runtime-support-matrix.md)\nand [handoff recipes](docs/capability-recipes.md#fork-or-move-a-session).\n\n### Less signing in. Less copying secrets.\n\nBivy syncs **Bivy-managed API keys and supported OAuth credentials** across\nenrolled machines for compatible runtimes. Connect supported credentials once\nand reuse them where you run work, rather than manually distributing keys to\neach machine.\n\nFor ordinary account sync, credentials are encrypted on the node before upload.\nThe control plane stores ciphertext and wrapped-key metadata; enrolled nodes\nshare access by wrapping the vault key to one another. Bivy Cloud does not\nreceive plaintext credentials through this sync path.\n\nYou can also keep credentials local, use labeled keys and project presets, or\nreference environment variables and 1Password instead of embedding secrets in\nconfiguration:\n\n```bash\nbivy provider login\nbivy credentials add anthropic work\nbivy secrets ref github.repo-token op://Bivy/GitHub/repo-token\n```\n\n**Not every CLI login syncs.** Native agent logins may still be per-machine;\nGitHub App private-key sync is separately opt-in. If you lose every node and\ndevice able to unwrap a vault, you must sign in to providers again. Explicit\nhosted-provisioning custody grants are separate from ordinary encrypted sync.\n\n[Credential sync and runtime coverage →](docs/credential-sync.md) ·\n[Credentials guide →](docs/credentials-guide.md) ·\n[Key storage →](docs/key-management.md)\n\n### Work in the environment you already have\n\nA clean cloud sandbox isn't always enough. Your agent may need the database\nrunning on localhost, an uncommitted change, an internal API behind your VPN,\nor a model running on your GPU. Bivy runs the agent where those things already\nexist, subject to that machine's permissions and the runtime's protection.\n\nConnect several machines to the same account: a laptop for interactive work,\na Linux server for background jobs, or a GPU box for local inference. Choose\nthe machine for each session or pin it in an automation. Repository runs can\nuse isolated Git worktrees without rebuilding the whole development environment.\n\n**The execution machine must stay awake and online.** To close your laptop and\nleave work running, run the agent on a different, always-on machine.\n\n[Environment and multi-machine recipes →](docs/capability-recipes.md)\n\n### Start at your desk. Continue anywhere.\n\nOpen the same session in the browser, phone PWA, or terminal. Watch work live,\nanswer questions, approve supported tool calls, or stop the agent.\n\n- Send screenshots, images, logs, and other files from your phone.\n- Download reports and artifacts the agent creates.\n- Open [session apps](docs/apps.md) from chat or the **Apps** menu: live web\n  previews, desktop app views, and CLI/TUI tools. Agents can publish views with\n  `bivy app publish bivy.app.json` and create share links with `bivy app share`.\n- Use voice input and read-aloud where supported; provider-backed voice may\n  send audio or text to the selected provider.\n- Keep a native terminal workflow or use structured chat, depending on the agent.\n\n```bash\nbivy run claude --no-follow  # start without attaching\nbivy open                    # open the web app\nbivy resume                  # return to the session in your terminal\nbivy link                    # pair a device directly via QR\n```\n\nNo phone app installation is required. Open [app.bivy.sh](https://app.bivy.sh)\nin your browser; adding it to your home screen is optional.\n\n[Remote access →](docs/remote-access.md) ·\n[Voice, files, and terminal recipes →](docs/capability-recipes.md)\n\n### Agents can reach you, too\n\nEvery session gets the `bivy` CLI, so any agent with a shell can talk back\nthrough the app, not only agents with their own built-in tools:\n\n```bash\nbivy notify \"Tests are green, PR is up\"     # chat card + phone push when you're away\nbivy ask \"Ship to staging?\" --option Yes --option No  # waits for your answer\nbivy attach report.png --caption \"Before/after\"       # show a file in the chat\nbivy suggest \"Add a dark theme to settings\"           # a next task you start in one tap\nbivy context --json                                   # session, workspace, machine, apps\n```\n\n`bivy help --json` lists every command, and with `BIVY_OUTPUT=json` failures\ncome back as structured errors with distinct exit codes, so an agent can tell\nwhat went wrong and what to run next. `bivy guide` prints short playbooks for\nagents, and the same commands are served as MCP tools for agents that prefer\nthem. Add your own standing instructions for\nevery session in **Settings → Agent instructions**.\n\n[Commands for agents inside a session →](docs/cli-reference.md#inside-an-agent-session) ·\n[Agent instructions →](docs/agent-instructions.md)\n\n## Get started\n\n### Install\n\nBivy supports **macOS and Linux with Node.js 20+**. The installer installs the\n`@bivy/bivy` package, runs guided setup, and starts a launchd or systemd service:\n\n```bash\ncurl -fsSL https://bivy.sh/install.sh | bash\n```\n\nSetup helps you choose an agent and configure remote access. Existing agents\nkeep their command, login, and configuration. The installer may use `sudo` to\ninstall a missing Node.js, but never for `npm install`. To inspect it first,\ndownload it with `curl -fsSL https://bivy.sh/install.sh -o install.sh`.\n\nAlready have Node.js and want to avoid sudo?\n\n```bash\nnpm install -g @bivy/bivy\nbivy setup\n```\n\nThen try one small task:\n\n```bash\ncd your-repo\nbivy run claude\n# Ask: \"Explain this repo and make one small, safe improvement. Run the relevant checks.\"\nbivy open\n```\n\nOpen that same session on your phone while it runs. For a web app, ask the agent\nto start its dev server, then open **Apps → Running in this workspace → Preview**.\nTry a page, point to something you'd change, and send the feedback back to the\nagent. No separate preview deployment needed.\n\nOnce that works, share a preview for review, connect another machine, or add\nyour first automation.\n\n**Local-only works too.** `bivy run`, `bivy resume`, and `bivy sessions` need no\naccount or server. Choose **local only for now** during setup; use `bivy login`\nlater. Browser and phone access need a hosted or self-hosted control plane;\nthe node itself does not serve a web UI.\n\n[Full quickstart →](docs/quickstart.md) ·\n[Installer options, service management, and uninstall →](docs/install.md)\n\n### Choose hosted or self-hosted\n\n| Option | What you get |\n|---|---|\n| **Free Cloud — $0** | Every launch feature, including automations; 10 new remote sessions per rolling seven days. No credit card required. |\n| **Cloud — $15/month** | The same features with unlimited remote sessions. |\n| **Self-hosted Core** | Operate the app, control plane, and relay yourself, with no Bivy usage limits. |\n\nManual and automated sessions share the Cloud allowance. Resuming existing\nsessions and viewing history do not consume it. Agent subscriptions and model\nprovider charges are separate. See [current pricing](https://bivy.sh#pricing).\n\n**Self-host anywhere:** deploy the public control-plane (including the web app)\nand relay images with Postgres and [a small set of environment variables](docs/deploy-images.md).\nYour server or container platform handles HTTPS. Set up owner access in the\nbrowser—no SSH, external authentication provider, or Bivy Cloud account required.\nFor a bare VPS, the [Compose installer](docs/self-host-quickstart.md) automates the\nsame stack. These onboarding features require a release containing them.\n\nStart on Cloud and self-host later if you prefer. Deploy the stack, reconnect\nmachines with `bivy relay:setup`, and pair devices to your server. This is not a\none-click migration of your Cloud account; your local repos and agent\nconfiguration stay in place.\n\n```bash\nbivy relay:setup \\\n  --control-plane https://bivy.example.com \\\n  --relay wss://relay.example.com\n```\n\nSelf-hosting is community-supported: you own TLS, backups, upgrades, and\nhardening. Public multi-architecture images are available as\n`ghcr.io/bivysh/bivy-control-plane` and `ghcr.io/bivysh/bivy-relay`; pin a release\nversion or full commit SHA.\n\n[Deploy the images anywhere →](docs/deploy-images.md) ·\n[Optional VPS installer →](docs/self-host-quickstart.md) ·\n[Operations reference →](docs/self-host.md)\n\n## Architecture\n\nYour environment, with clear security boundaries:\n\n```text\nYour machine                         Hosted or self-hosted\n┌──────────────────────┐             ┌──────────────────────┐\n│ Node daemon          │──outbound──▶│ Relay                │\n│ Agents, repos, tools │             │ Encrypted frames     │\n│ Local credentials    │             └──────────┬───────────┘\n└──────────────────────┘                        │\n                                    Browser / phone\n                                    + control plane\n                                    (app, accounts, metadata)\n```\n\n- **Execution stays on your machine.** Bivy Cloud does not run your agents.\n  Your model provider still sees whatever the agent sends it.\n- **Interactive session traffic is end-to-end encrypted** between the node and\n  paired devices. The relay forwards opaque session frames; your node dials out,\n  so no inbound public port is required.\n- **App previews have a separate security boundary.** Preview traffic uses HTTPS\n  and an outbound tunnel, not session E2E encryption. The preview ingress/relay\n  operator can see it. Public preview links grant anyone holding them access to\n  that view and its live backend until expiry or revocation. See\n  [preview security and sharing](docs/apps.md#runtime-and-security-boundaries).\n- **Ordinary credential sync uploads ciphertext, not plaintext keys.**\n  Supported credentials and recovery limits are documented separately.\n- **Encryption is not universal across integrations.** Slack commands and\n  generic webhook instructions reach the control plane in plaintext. Do not\n  put secrets in them. Routing and bounded run metadata are also visible there.\n- **Device authorization matters.** QR pairing authorizes a device directly\n  through the node. Hosted account pairing trusts the control plane to authorize\n  devices and serve the web app that holds client keys.\n- **Bivy is not an OS-level sandbox.** The default approval mode is\n  `autonomous`; protection depends on the runtime. Some agents enforce sandbox\n  tiers, while process agents may run with your full user permissions.\n  Heuristic tool checks help prevent accidents but are not isolation.\n\nReview the runtime's Protection label and configure approval/sandbox settings\nfor the task, especially before enabling unattended work.\n\n[Security model and known limitations →](docs/security-model.md) ·\n[Runtime protection matrix →](docs/runtime-support-matrix.md) ·\n[Configuration →](docs/configuration.md)\n\n## Agents and everyday commands\n\n**Claude Code, Codex, Pi, OpenCode, and Grok are release-tested.** Additional\nadapters include Gemini CLI, Qwen Code, Goose, Aider, Cline, Crush, Cursor, GitHub\nCopilot, Amp, Auggie, Droid, Continue, Kilo Code, and Rovo Dev. Installation,\nresume, model selection, and tool protection vary—see the\n[support matrix](docs/runtime-support-matrix.md) and [agent guides](docs/agents/README.md).\n\nRun an arbitrary command with `bivy run -- ./your-agent --flags`, register a\nreusable entry with `bivy agent add`, or package a declarative integration with\nexperimental [plugins](docs/plugins.md).\n\n```bash\nbivy run claude       # launch a durable session; also codex, pi, opencode\nbivy sessions         # list live and saved sessions\nbivy resume           # resume the most recent session\nbivy open             # open the web app (requires remote setup)\nbivy nodes            # list connected account machines\nbivy runs list        # inspect delegated work\nbivy automation init  # scaffold repo-owned automations\nbivy provider login   # connect supported model credentials\nbivy agent add        # register an ACP or process agent\nbivy doctor           # check installation and connectivity\nbivy logs -f          # follow node logs\nbivy update           # update and restart the service\n```\n\n`bivy update` uses your original installation method and waits for an active\nturn to finish before restarting. Use `--force` to skip that wait.\n\n[CLI reference →](docs/cli-reference.md) ·\n[Node and project configuration →](docs/config-as-code.md) ·\n[GitHub setup →](docs/github-setup.md) ·\n[Linear setup →](docs/linear-work-queue.md)\n\n## Development and contributions\n\n```bash\npnpm install\npnpm run dev          # node daemon on http://localhost:4317\npnpm run dev:web      # web client dev server\n```\n\n| Directory | Contents |\n|---|---|\n| `src/`, `bin/` | Node daemon, CLI, runtime adapters, sessions, approvals, secrets |\n| `packages/core/` | Shared protocol, pairing, and wire format |\n| `packages/web/`, `packages/ui/` | React PWA and shared design system |\n| `services/relay/` | Self-hostable encrypted relay |\n| `services/control-plane/` | Self-hostable control plane |\n| `deploy/` | Deployment examples |\n\n```bash\npnpm run typecheck\npnpm run typecheck:web\npnpm run lint\npnpm run test:unit\npnpm run test:core\npnpm run check:licenses\npnpm run check:secrets\n```\n\nSee [CONTRIBUTING.md](CONTRIBUTING.md) for the development workflow. Releases\nare published from CI with provenance attestations; see\n[release verification](docs/releasing.md).\n\n**Found a security issue?** Use\n[GitHub private vulnerability reporting](https://github.com/bivysh/bivy/security/advisories/new),\nnot a public issue. See [SECURITY.md](SECURITY.md).\n\n### In development—not available at launch\n\nAutomatically provisioned, short-lived **ephemeral machines** are in development\nfor hosted and bring-your-own-cloud deployments. Neither path is ready or\nsupported for this launch. Use an existing computer or server you operate.\nExperimental provisioning has different credential-custody and encryption\nboundaries; see the [provisioning trust model](docs/hosted-provisioning-trust-model.md).\n\n## License\n\nEverything in this repository—node, CLI, web/PWA, relay, and control plane—is\nfree and open-source **AGPL-3.0-only Core**, with no Bivy usage limits. You may\nuse, modify, and self-host it under that license. If users interact with your\nmodified version over a network, section 13 requires you to offer its\ncorresponding source. See [LICENSE](LICENSE).\n\nBivy Cloud is the hosted operation of that stack plus billing and plans, in a\nseparate private repository. Contributions use the\n[DCO](CONTRIBUTING.md#certificate-of-origin); there is no CLA.\n",
   "readmeFilename": "README.md",
   "agentBridges": {
     "@anthropic-ai/claude-agent-sdk": "0.3.285",