Documentation
Read the instrument, then press it.
These pages live in the repository. This hub is the map. Source of truth for agents is AGENTS.md.
Install & MCP
GitHub install, client JSON, app vs CLI, Node 24 repair.
AGENTS.md
Every MCP tool, the typical loop, and current limitations.
Launch & validate
Control panel first run, Flutter lab, proof, workflows, tracing.
App settings
Theme, reduced motion, restore last project, launch at login.
Architecture
How detect, daemon, adapters, and the panel share one session model.
llms.txt
Short crawler summary for coding agents that fetch URLs.
Flutter lab
Credential-free sample with Local / Test environments.
Workflow lab
Two-project delivery graph: API then console, then recover an outage.
Contributing
How to add an adapter without lying about hot reload.
Changelog
What shipped in 0.2.3 and before.
MCP tools
What an agent can call
inspect_project, list_targets, list_sessions, list_checkouts, list_devices, run_target, run_workflow, hot_reload, hot_restart, stop_session, forget_session, wait_for, read_logs, session_summary, screenshot, set_debug_flag, diagnose, list_network_requests, get_network_request, clear_network_requests, read_launch_config, write_launch_config, run_proof, list_proofs, list_run_history.
Baton does not tap the UI. Pair these with your client’s browser or device tools.
Safety
Loopback, token, no secrets in git
The daemon writes ~/.baton/daemon.json with port and token. Clients read it. Nothing should listen off-loopback. Launch files that will be committed must not contain secrets; Baton will refuse a run when a gitignored config is missing, unless you pass --force.