francis-du/wcode

wcode helps coding assistants read repositories, change code and run checks. It works through MCP with the assistant you already use. You can inspect changes, manage tasks, approve access and see which checks ran against the current code.
The workflow is Understand → Change → Inspect → Verify → Evidence → Accept / Block. The team edition, wteam, adds shared policies, review records and GitHub merge checks. Its complete team workflow still needs a real pilot; individual implemented features do not establish that the whole workflow is ready. See the capability audit and implementation plan.
> Checks are tied to the code they ran against. A past passing result does not approve a later change.
Website · Documentation · Getting started
The Apache-2.0 Core and complete local product remain independently useful. New commercial composition packages consume OSS public contracts in a separate workspace; see the OSS / Commercial architecture audit and migration boundaries.
The website is the canonical product documentation and includes its own language switcher. The four system SVGs below are living product documentation: when wcode changes its engineering loop, repository model, verification contract, or security boundary, the diagrams are expected to evolve with the product.
## Get started
Install on macOS or Linux:
bash
curl -fsSL https://raw.githubusercontent.com/francis-du/wcode/main/install.sh | sh
Windows PowerShell:
powershell
irm https://raw.githubusercontent.com/francis-du/wcode/main/install.ps1 | iex
From the repository you want to expose:
bash
wcode setup
Choose Global (recommended) or Current project, reconnect the coding agent, and let the host launch wcode mcp-stdio. The host working directory becomes the default Workspace.
Run the operator runtime when you also want the TUI, Project Status, Setup Hub, or remote MCP access:
bash
wcode
Press W for the Project Status and O for Setup Hub. Remote clients use the public /mcp endpoint shown by the runtime and complete OAuth.
The current workspace, revision and snapshot state stay visible across all seven pages. This image uses labeled fixture data. See the interface review and page gallery for desktop, phone and terminal states.
## Update and reconnect
For an existing installation, run wcode --version, then wcode update, and check the version again after the updater finishes. The updater fetches the latest stable release; use the fixed GitHub release downloads and their SHA256SUMS when you need a specific version.
Reconnect your MCP Host to start a new stdio process. Replacing the binary does not upgrade an already running session or restart a standalone service. On Windows, replacement begins after the update process exits; the helper's preparation message is not completion.
The documentation source index is also readable directly in this repository. When the documentation website is unavailable, browse the release-note source directory for the bilingual upgrade steps, Jobs operating guide, troubleshooting and verification records.
## The engineering loop
wcode keeps the model replaceable while repository state, policy, proof, and observability remain durable.