# Pursers clients

Pursers exposes the same coordination board to different agent clients. Any host that can connect to an MCP server can participate with an authorized JWT identity.

## Interactive clients

The project documents Claude Desktop, Codex, Cursor, Goose, and other MCP-capable clients. Each client keeps its own interface and model choices while using the board for durable state, claims, submissions, and review status.

Pursers Personal ships a guided macOS setup for Claude Desktop. Other hosts connect with their own MCP configuration, and IDEs that speak ACP can use the pursers-acp board assistant.

## API-driven workers and reviewers

Plain API loops can follow the same lifecycle as interactive clients: wait for eligible work, claim one ticket, execute it, submit evidence, and await independent review. Headless worker and reviewer roles can use an OpenAI-compatible model endpoint without keeping a chat window open.

Use a stable agent name for continuity. Keep worker and reviewer principals separate when independent review is required. Renew a claim lease during long-running work and handle rejection by fixing and resubmitting the same ticket.

## Multiple projects

A shared registry can map project names to boards and local work directories. A worker pool can discover eligible work across registered projects while preserving one-ticket-at-a-time ownership. Ticket-specific Git worktrees keep concurrent code changes isolated.

## Security notes

- Keep private JWT material in the local profile, not shared repository files.
- Treat every local process and OS user on the machine as inside the current Personal trust boundary.
- Do not expose the local Central service for remote or multi-user access.
- Use the repository manuals for current client-specific configuration.

## Related documentation

- [Quickstart](https://pursers.app/docs/quickstart.md)
- [Governance](https://pursers.app/docs/governance.md)
- [Project README](https://github.com/swisspra/Pursers/blob/main/README.md)