wednesday docs
Docs/Guides

Security & data

Wednesday is local-first: keys, crews, skills and run state stay on your machine. There is no Wednesday server to send them to.

Local by design#

The MCP server runs on your machine. It talks to the model provider you configure and to your own machine. It calls no registry and no update service.

WhatWhere
Credentials~/.wednesday/.env
Crews~/.wednesday/state/crews.json
Task history~/.wednesday/state/tasks.json
Event log~/.wednesday/state/events.jsonl
Skills~/.wednesday/skills/
Attached MCP servers~/.wednesday/state/mcp.json

Deleting ~/.wednesday/ removes the local profile. The code itself is public under Apache 2.0.

Keys and redaction#

API keys, tunnel URLs, and server headers are read from your local profile. They are never written to the repository, the event log, the task record, or a receipt. A central redaction pass runs over receipts and status output as a second line of defence.

There is no Wednesday account and no hosted inference. A private key is yours; Wednesday is BYO-key by design.

The secret scan#

scan
wednesday scan                  # the repo you are standing in
wednesday scan --repo ./other   # another repository
wednesday scan --install-hook   # a pre-commit gate

It matches shapes: a leaked secret, a dangerous call. A pass means no secret shape and no dangerous call shape — never no vulnerability. --install-hook writes .githooks/pre-commit and sets core.hooksPath, so every clone and contributor gets the gate. It scans what is staged: the bytes actually being committed.

Escape hatches are loud rather than silent. --allow-findings reports the finding and says it is now part of the history. git commit --no-verify bypasses everything.

Workspace confinement#

Engineering work runs in a controlled sandbox with explicit tools. File tools are workspace-confined; the model does not get a free-form shell. Only verification scripts the project already declares are executed.

Over MCP the team runs unattended inside its workspace. A client-side approval gate wired to MCP elicitation is not built yet; if you need a human in the loop today, use the CLI and inspect the diff before committing.

This website#

  • Static, served from Cloudflare Pages.
  • No analytics, no advertising, no tracking pixels, no cookies.
  • Fonts come from Google Fonts; that request is subject to Google’s privacy policy.
  • No server-side processing of visitor data.

The policy pages are Privacy, Terms, Security disclosure and Cookies.

Reporting a vulnerability#

Do not open a public issue for a vulnerability. The disclosure process is in SECURITY.md; the repository’s security page is here.

A report that names the version, the command, and the smallest reproduction is the most useful one.