Skip to main content

Bootstrap CLI that hoists the shared workstate-system surface into consumer repos.

Project description

workstate-bootstrap

Pip-installable CLI that hoists the shared workstate-system surface (typed protocol, two MCP servers, hooks, skills, generated agent workflows) into consumer repositories. Lives inside darce/workstate.

Consumers run workstate-bootstrap install --target <path> once; it clones the monorepo, materializes the overlay, and registers both managed MCP servers (mcp-workstate-handoff, mcp-workstate-orchestrator) across .mcp.json, .vscode/mcp.json, and .codex/config.toml. No hand-edits required.

Install

From PyPI (recommended)

uvx --from workstate-bootstrap workstate-bootstrap install --target /path/to/your/repo
# or, persistent:
uv tool install workstate-bootstrap

From the monorepo source tree (development)

cd packages/workstate-bootstrap
python -m pip install -e ".[dev]"

Direct from git (private-repo phase, before PyPI release)

One-shot (no install — fetches each invocation):

uvx --from "git+https://github.com/darce/workstate@workstate-bootstrap-v0.2.1#subdirectory=packages/workstate-bootstrap" \
    workstate-bootstrap install \
    --target /path/to/your/repo

Persistent (recommended once you start running status / doctor regularly — installs workstate-bootstrap onto $PATH):

uv tool install "git+https://github.com/darce/workstate@workstate-bootstrap-v0.2.1#subdirectory=packages/workstate-bootstrap"
# then:
workstate-bootstrap status --target /path/to/your/repo
workstate-bootstrap doctor --target /path/to/your/repo
# upgrade later:
uv tool upgrade workstate-bootstrap

Hardlink warning on first install? If you see Failed to hardlink files; falling back to full copy, your uv cache and tool dir live on different filesystems. The install still succeeds; silence the warning with export UV_LINK_MODE=copy in your shell profile.

Subcommands

workstate-bootstrap install --target <path> [--remote-ref <tag>] [--mcp-servers <default|path>] [--no-mcp-servers]
workstate-bootstrap update  --target <path> --remote-ref <tag>
workstate-bootstrap status  --target <path>
workstate-bootstrap doctor  --target <path> [--mcp-servers <default|path>]
workstate-bootstrap repair  --target <path> [--force-dirty] [--mcp-servers <default|path>]
  • install: Clone the monorepo, materialize SHARED + GENERATED surfaces, write the three MCP-config files, run init-state to provision <target>/.task-state/handoff.db (skipped under --no-mcp-servers), set core.hooksPath, and write the overlay manifest.
  • update: Re-run install at a new --remote-ref; refresh GENERATED surfaces and, optionally, configs.
  • status: Print a summary of the installed overlay manifest. When the install registered MCP servers, also reports the resolved state_dir / db_path / exports_dir / schema_version via init-state --check.
  • doctor: Detect drift in SHARED, GENERATED, config, and initialized-state surfaces. Flags missing .task-state/handoff.db as state_drift only when the manifest recorded .mcp.json. Exit 1 when drift exists.
  • repair: Restore drifted surfaces flagged by doctor.

See docs/CONSUMER.md for the consumer-facing walkthrough (upgrade, drift handling, skill overrides, the current_task_auto_regen migration note).

Surfaces written by install

The canonical source of truth for bootstrap-managed surfaces is the installer implementation in src/workstate_bootstrap/install.py (SHARED_SURFACES and GENERATED_SURFACES). Keep this table aligned with those constants.

Surface Source Layer
scripts/hooks/ shared symlink
.github/hooks/ shared symlink
docs/agentic/contracts/ shared symlink
docs/agentic/rules/ shared symlink
Makefile.d/ non-excluded children shared carved dir
scripts/workstate/ non-excluded children shared carved dir
.github/prompts/ generated real dir
.agentic/generated/plugins/workstate-system/base/ generated real dir
.agentic/generated/plugins/workstate-system/effective/ generated real dir
.mcp.json generated real file
.vscode/mcp.json generated real file
.codex/config.toml generated real file
core.hooksPath git config generated git config
.task-state/handoff.db runtime sqlite
.task-state/exports/ runtime dir
.agentic/remote/ bootstrap git clone
.workstate-bootstrap.json bootstrap manifest

.task-state/ is provisioned by the handoff server's init-state subcommand at install time and is gitignored — each fresh checkout regenerates it through workstate-bootstrap install.

Defaults

  • --profile defaults to all, which materializes the full surface set: generated Copilot prompts, Claude/Codex plugin trees, shared overlay surfaces, and the lifecycle hoist (Makefile.d/lifecycle.mk plus the sentinel-bracketed -include block in the consumer Makefile). Pass --profile minimal for a clone-only install with no surfaces, or --profile lifecycle for just the lifecycle runner and Makefile fragment. The active profile is recorded in .workstate-bootstrap.json under "profile".
  • --remote-url defaults to git@github.com:darce/workstate.git.
  • --remote-ref defaults to main (override with a release tag like v0.1.0).
  • --mcp-servers defaults to the built-in managed map registering mcp-workstate-handoff and mcp-workstate-orchestrator via uvx with --workspace-root . serve-stdio, so Codex, VS Code, and Claude clients start real MCP stdio servers from the generated config. Pass a JSON file path to override; pass --no-mcp-servers to skip the three config writers entirely.
  • Plugin overrides are auto-discovered at workstate-overrides/workstate-system/ when that root contains an overrides.yaml manifest. Use --plugin-overrides <path> on install, update, doctor, or repair for a non-default root; bootstrap records that path so later update/doctor/repair runs reuse it. Override-aware installs generate effective plugin trees under .agentic/generated/plugins/workstate-system/effective/{claude,codex} and point marketplace pins at those generated trees.
  • install and update preserve plugin override files by default. --reset-overrides is the explicit destructive path; it removes only the resolved override root, refuses dirty git worktrees unless --backup is supplied, and archives backups under .agentic/override-backups/<timestamp>/ before removal.

Development

Tests live under tests/. From the monorepo root:

cd packages/workstate-bootstrap
PYTHONPATH=.:src:../workstate-protocol/src pytest tests -q

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

workstate_bootstrap-0.5.2.tar.gz (96.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

workstate_bootstrap-0.5.2-py3-none-any.whl (46.0 kB view details)

Uploaded Python 3

File details

Details for the file workstate_bootstrap-0.5.2.tar.gz.

File metadata

  • Download URL: workstate_bootstrap-0.5.2.tar.gz
  • Upload date:
  • Size: 96.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.13

File hashes

Hashes for workstate_bootstrap-0.5.2.tar.gz
Algorithm Hash digest
SHA256 92b6b24b3657e6ebf5047f2cb6913cc8fd31c10212ae44d1e148d42782b266a9
MD5 c66df4a75b38803b3de69e282506086f
BLAKE2b-256 e48f576caa8ef70667e31b0483619c7b393abd86a303506d2a5684f16d039684

See more details on using hashes here.

File details

Details for the file workstate_bootstrap-0.5.2-py3-none-any.whl.

File metadata

File hashes

Hashes for workstate_bootstrap-0.5.2-py3-none-any.whl
Algorithm Hash digest
SHA256 be3f374f61e2904ac1a63c8a4cd06437b2aacb2985aa84682226dead13c747c8
MD5 f159ec36a7de6d665730364f1975f1b2
BLAKE2b-256 fa0daa7aa0063cd3bff4fbaa52443c203447059d7e6bee4ecd6fa39121bac432

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page