Agree who operates it.
The operator maintains the runtime, tool access, dependencies, model credentials, resource limits, and project instructions. For software work, a reviewer also checks the code and release readiness. Your team or a service provider can cover these roles.
Business users can direct tasks from the board after this environment is in place. They should know who to contact when a task needs technical help.
Three parts of the setup
- Kardbrd workspace
- The hosted board stores requests, comments, attachments, and working records.
- Agent runtime
- The Go daemon runs where the operator provides project access. It invokes an installed executor such as Claude, Codex, Goose, or Pi.
- Model provider and tools
- The executor uses its configured AI provider and tools. Selected code or task material can leave the runtime for model processing, even when you host the runtime yourself.
Define access and account ownership for all three parts. Keep production credentials out of ordinary task comments and use a development or preview environment appropriate to the work.
Start with the maintained operator documentation
The current agent is a single Go binary. Build prerequisites, installation, configuration, and executor options are maintained with the agent.
kardbrd agent validate
kardbrd agent startConfigure the board ID, agent identity, project working directory, and executor credentials before starting. Project rules control how events initiate work; release authority depends on your configured process.
MCP is another connection path.
An MCP-compatible client can access Kardbrd’s board tools without running the agent daemon. This provides board access; the client still needs the tools and access to carry out work beyond the board.