A reason behind every state
Your manifest says what should run. Run records and observations show what does. Trace services, ports, exits and logs without guesswork.
Local first · Native macOS · Open source
Every worktree.
In its own berth.
A clearer place for parallel development. Keep each worktree’s services, Git context, terminals and agent sessions together. Less guessing. More time with your code.
One checkout. One clear context.
01 / WORKSPACEActual macOS windows, captured with an isolated demo project. Select an image to see the original.
Context stays where it belongs
Every session keeps its starting worktree. Switching checkouts never silently moves a terminal or mixes up project services.
Keep the tools you know
A native terminal hosts your shell and existing coding agents. No new chat system to migrate to. No cloud workspace required.
02 / THE WORKFLOW
Start with a manifest. Not a maze.
The app and CLI share one chain of runtime facts. You make the decisions; option-berth keeps the state and next step in view.
Connect your worktree
Choose a code directory. Read an existing manifest, or review and accept a new one. An agent can draft it, but the final choice is yours.
oberth initInspect, then start
Start declared services in dependency order and check their actual runtime and readiness. Machine dependencies remain read-only.
oberth up oberth statusGo straight to the evidence
Open logs from a service, inspect a Git diff, or continue in a terminal. Stop this project when you are done, without touching another worktree.
oberth logs oberth downGETTING STARTED
Skip it. Reopen it. Reading is not a readiness check.
03 / YOUR TOOLS, TOGETHER
Your terminal. Your agents.
Keep terminal and agent sessions beside the code they work on, without taking over their reasoning, authentication or approvals.
A prompt, then a native handoff
Use the first message to start an external agent session. Continue the conversation in its own native terminal. Return still inserts a newline.
⌘↵New session⇧⌘↵Native handoff
Bring your coding agent
Install and authenticate the tools you need. Launch explicitly and resume where supported. No automatic installs or approval bypasses.
OpenCode · Codex · Claude Code
DeepSeek Harness · Pi
04 / LESS RETRACING
Find the command. Keep your flow.
Search commands and session names across this worktree’s terminals. Keep exit results explicit. Copy the literal command without executing it. Confirm before clearing.
Enable zsh command blocks beforehand. History lives in memory and is discarded when a session closes or the app quits. Shell-history files are not imported.
05 / CLEAR BOUNDARIES
Less to take over. More to trust.
A local development workspace, not another agent platform. Each state, permission and side effect has a clear owner.
Observed, not inferred
Declarations, runs and observations come from code. Unknown is not success. A stop request is not proof of an exit.
Your code stays yours
Product Git actions are read-only; manifests need your approval. External shells and agents keep their own permissions. A worktree is not an OS sandbox.
Restore by choice
Opt in to saving essential layout metadata, not prompts, output or PIDs. Restoring a layout never resurrects a process. No cloud sync.
READY WHEN YOU ARE
A berth for your next checkout.
A native macOS app with its matching oberth engine. Or use the CLI on its own, inside the workflow you already have.
The macOS app requires Apple Silicon and macOS 14+. Current builds are ad-hoc signed, not Developer ID signed or Apple notarized.
What should I know before installing?
Get packages from the official GitHub Release and check SHA256SUMS. The macOS package includes its matching engine. Ad-hoc signing is not Apple trust or notarization. Installation and upgrades are explicit; the app does not replace itself or stop your existing services. Windows and Linux packages are CLI-only, not desktop apps.
Read the client guide ↗