Claude Code-style help, running on your machines.
Bivy is a private coding AI workspace for your laptop, Mac mini, or server. It uses your own model keys, works in your real repo, and stays reachable from your computer or phone — without moving your code, credentials, or terminal into a vendor sandbox.
✓ node online: Petter’s MacBook
✓ model keys loaded locally
✓ phone connected over E2E relay
✓ GitHub issue pickup enabled
github: issue #128 assigned to Bivy
→ created branch bivy/issue-128
→ editing locally
→ running typecheck
→ PR ready for review
npm run typecheckNo errors. Preparing PR.
Local-first coding assistance, reachable from anywhere.
Install a Bivy node on each computer or server you want AI to use. A node can start chat sessions, edit files, run commands, open terminals, pick up GitHub issues, and produce branches or PRs. The app and relay help you reach those nodes; the actual work stays on the machine that owns the repo.
Like Claude Code, but yours
Chat with a coding assistant that can read, edit, run commands, and use your local development environment.
Bring your own keys
Use your own model provider credentials. Bivy does not need to proxy your prompts or hold your model keys.
Phone as control room
Check progress, send guidance, approve rare backstops, or jump into a live terminal from your phone.
Let it run without babysitting every step.
Bivy is designed for unattended work. Instead of asking you to approve every file edit or shell command, it gives the assistant a clear boundary and lets normal work proceed.
Safe working boundary
Code work happens in a git worktree on a branch, confined to the workspace — never directly on main.
Hard stops for bad ideas
Catastrophic or irreversible actions are blocked. Pushes to main, deploys, sends, or spending can still require a backstop approval.
Review the result
The normal quality gate is the output: a diff or PR you review when it is ready, not a stream of approval popups.
Assign work where it already lives.
Bivy is not another task manager. Use the tools your team already uses: label a GitHub Issue, mention Bivy in Slack, create a Linear ticket, or quick-add from your phone. Bivy routes the session to the machine you choose — for example bivy/macbook for Xcode work or bivy/server for backend work — runs locally in a branch/worktree, and reports back with a PR or diff.
Your codebase is not a temporary cloud workspace.
The best coding AI should be able to use your real tools and environment — without requiring you to upload your repo, secrets, shell, and workflow to someone else’s machine.
Content stays on node
Prompts, tool output, file contents, and terminal streams live on the owning computer and travel only as E2E-encrypted frames.
Control plane sees metadata
The hosted service can know status, node, source, and PR links. Session titles can be encrypted. It does not need session content or model credentials.
Nodes dial out
Your laptop or server opens an outbound relay connection. You do not need to expose SSH or open inbound ports to reach it from your phone.
Put a private AI runner on your machine.
curl -fsSL https://bivy.sh/install.sh | bashThen sign in, name the machine, and connect GitHub when you want issue pickup. Package/repo: bivy. CLI: bivy.