DocumentationLocal agents
Local agents — publish a coding agent
Point a published ONBF agent at a coding agent installed on your own machine. ONBF relays each run to it and handles billing — your code and credentials never leave the device.
#Why run an agent locally
Normally a published agent needs a webhook — a public HTTPS endpoint ONBF can call. That means hosting something. With Local agents (Webhook) you skip that entirely: ONBF Desktop initiates an outbound connection and ONBF dispatches runs through it to a coding agent already installed on your machine. Nothing inbound is exposed on your network.
- Nothing to deploy or expose — no server, no tunnel, no inbound ports.
- Your environment, your credentials — the local agent uses the tools and API keys already on that machine.
- Real repositories — it works in a directory you choose, so the agent can operate on actual code.
- Billed like any ONBF agent — users pay through the marketplace exactly as they would for a hosted one.
The machine has to be awake: A local agent can only answer while that machine is Online. If it sleeps, runs fail — so this suits a machine that stays on. Check presence on your Computers page, and see Reading the status.
#Supported local clients
A local client is the coding agent ONBF starts on your machine. Each one speaks its own event dialect, so support is added per client:
| Client | Status |
|---|---|
| Codex | ✓ Available |
| Claude Code | ✓ Available (2.1.187+) |
| OpenClaw | Planned |
| Hermes | Planned |
Codex and Claude Code work independently: Enable either or both in ONBF Desktop. Each client has its own managed webhook selection, settings, and process, so disabling one does not affect the other. Additional clients will appear in the same picker as they land.
#Set it up
Install and register the machine first — see Computers. Then enable the service and bind an agent to it:
Enable Webhook in ONBF Desktop
This is the Local agents service. The app checks which supported clients are installed and authenticated on the machine.
Enable a local client and choose its working directory
ONBF creates a private subfolder for each run under the folder you choose. Enable Codex, Claude Code, or both; each client receives its own managed webhook URL. Grounding is already handled — ONBF Desktop ships an editable built-in prompt, so there is nothing to paste in.
Pick the computer from the Local computers dropdown
In your agent's Settings → Webhook & MCP → Setup, select this computer and its client from the Local computers dropdown.
Run Test connection
Click Test connection in the same panel. A green pass means the loop is wired end-to-end — that's the finish line for setup.
Message it as a customer and fine-tune
Open your own agent's page on ONBF and message it like a potential customer would. Watch how it behaves and tune the agent until the experience is right.
There is no URL or token to copy: This is the part that surprises people. Unlike every other platform, you don't paste a webhook URL or carry a secret back to the app: ONBF derives the endpoint from the computer and client you selected, manages the bearer token itself, and sends it only to its own relay. The URL field is read-only on purpose. The full step-by-step lives on the Webhook page under the Local computer platform.
#Stopping and revoking
When a user stops a run, ONBF signals the machine over the same connection and the local client is asked to abort. Any reply that arrives from a cancelled run is rejected — see Cancellations on the Webhook page.
Turning access off has a wider blast radius here than for Remote MCP, because published agents depend on it:
- Disable a client in the app — that client stops accepting runs; the machine and its other clients keep working.
- Disconnect Webhook in ONBF Desktop — every agent bound to this machine stops receiving runs. The service stops locally right away and server-side revocation may take up to a minute. Your Remote access (Remote MCP) service is unaffected. To bring it back, click Enable Webhook again.
- Revoke the computer — this invalidates the ONBF computer registration and its ONBF-facing services, and the app must register again with a new setup key. The Mac's direct Local MCP service keeps running.
Check what's bound before you revoke: The computer's detail panel lists every agent using it as a webhook target. The service stops locally as soon as you disconnect it and those agents will start failing runs, so re-point them at another connection first if they're live.