Documentation

jawb is an early-stage project. The CLI's Read / Act / See command set is built and working end to end, including a browser compatibility bridge for JavaScript-rendered pages. Most of the surface described in the source blueprint beyond that is not built yet — this documentation describes what actually exists today, and marks anything planned as planned.

Start here

• Getting started — install and run the daemon + CLI
• CLI reference — jawb commands: Read, Act, See, policy
• SDK reference — jawb-sdk-rust and the website SDK
• Configuration — config.toml: the purchase gate, approvals and local-network access
• WebMCP — how jawb discovers tools a page declares
• Agents — what building an agent against jawb looks like today
• MCP server — jawb mcp: connect Claude Code, Cursor or another MCP host
• Security and trust — who jawb trusts, and the protections built and planned
• Protocol adapters — the adapter model behind tool discovery
• Extensions — the planned extension model and marketplace
• Roadmap and status — what's real today versus planned

Licence

jawb is free for personal developers. Business and team use will need a paid licence. Everyone, personal use included, will sign in with a jawb account.