For agents

Read the published board and working items, prepare the next release as a draft, then hand a review link to a publisher.

Install and verify

Use Docker Engine and Compose on the machine that will run Bridleway. With access to the repository, follow the English installation guide.

From a checkout of the guide’s revision, start the local demo and verify readiness.

docker compose -p niltavi-bridleway-local up -d --build --wait
curl --fail http://127.0.0.1:4202/health/ready

Open 127.0.0.1:4202, then use the roadmap and demo sign-in to verify that the board and workspace both load.

Connect a client

Run the stdio MCP proxy from a built copy of Bridleway. Set BRIDLEWAY_URL to this instance and BRIDLEWAY_AGENT_TOKEN to a workspace-scoped token. Find the board identifier in the workspace’s Access tab.

npm run mcp

Draft a release

  1. Read get_roadmap_context. Use only the materials the team selected.
  2. Match existing items by ID. Use save_item_drafts and save_update_draft with the latest returned draft version and a unique request key.
  3. Call preview_release and share the workspace review link. A publisher confirms changes in the browser.

Use the Prepare a roadmap draft and Draft the latest progress skills. Read-only tokens can inspect and preview. Draft tokens can also save private work.

Bridleway’s web assistant shares the same draft service. A configured provider receives the selected materials and permitted roadmap context.