Overview

blueclaw is a self-hosted Go daemon that runs an AI agent on behalf of the several people who share one machine. It executes each requester's tool calls as that person's own unprivileged POSIX user, holds side-effecting calls at an approval gate, and writes every step of every task to a durable event ledger in Postgres.

Why it exists

A company that runs one agent on one machine usually runs it as one Unix account. Every person who talks to it then shares one home directory, one set of files and one view of every secret, and nothing records which person authorized which side effect. blueclaw makes those people different people to the operating system. The harness decides what to call; blueclaw decides who the call runs as, whether it runs at all, and what is written down.

What it is

• A host. It owns connectors, identity, POSIX isolation, the task store, approvals, the tool catalog, capabilities, memory and delivery.
• A harness socket. The agent loop sits behind one Go method, agentcontract.Harness.RunTurn. The bundled loop is bluecollar; an ACP agent, Claude Code, Codex or Antigravity can take its place.
• POSIX as the boundary. Ownership and mode bits decide what a tool call may touch. There is no executable allowlist, no denied path prefix and no prompt telling the model what it may not do.

What it is not

It is not an agent, a model or a chat client. It does not sandbox the agent from the machine; it separates the people using the machine from each other, and a container or VM around it composes with that. There are no binary releases: you build it from source.

blueclaw is the agent host inside InternKim.

Where to go next

• Quickstart builds the daemon and drives a task over HTTP.
• Architecture shows how host, harness and contract divide the work.
• Concepts defines tasks, approvals, policy, skills and memory.
• Boundaries states the security model in detail.
• Operations covers configuration, the database and deployment.