pitbridge (daemon)

Python 3.12 daemon that sits between AI agents (MCP / REST / WS) and the NinjaTrader 8 AddOn (outbound WebSocket, port 8873). Binding spec: ../docs/architecture.md.

Dev setup

cd daemon
uv venv --python 3.12
uv pip install -e ".[dev]"
uv run pytest
uv run ruff check .

Status: M2 daemon-core — protocol models (14 message types, schema-mirrored), guardrail engine (M1), the AddOn WS link (hello/auth/heartbeat/snapshot/ reconnect-reconcile, reconcile-first hard), executor (idempotent pending-order table + ack timeouts), the frozen pipeline (schema -> permission -> guardrails -> confirm gate -> submit -> audit) as the single order path, the /v1 REST + WS surfaces, and tools/fake_addon.py for chaos tests. pitbridge run --config serves it. MCP surface + C# AddOn land in M3/M4.

Agent surface (0.2.0)

One uvicorn server, one port (default 127.0.0.1:8873), three transports over the same guardrail pipeline:

• REST /v1/* and the WS /v1/ws event feed;
• MCP over streamable HTTP at /mcp ([daemon] mcp_http, default true), for HTTP-native MCP clients; served by both pitbridge run and pitbridge mcp;
• MCP over stdio via pitbridge mcp (Claude Desktop / Claude Code).

Bearer auth ([daemon] agent_token)

Generate a token with pitbridge token new and set it in the config yourself (the CLI never writes it for you). With it set, every /v1/* call, the /v1/ws stream and /mcp require Authorization: Bearer <agent_token> (401 otherwise, constant-time compare). The WS /v1/addon leg keeps its own pairing_token hello auth.

Fail-closed rule: a non-localhost bind REFUSES to start without an agent_token (on top of the existing paired_mode + pairing_token requirement). On a 127.0.0.1 bind the token is optional and off by default (backwards compatible). pitbridge status and pitbridge doctor report the auth state.