@stackwright-pro/raft

Launch the Pro Otter Raft — verifies otter integrity, writes init context, and spawns raft-puppy (or code-puppy) in foreman mode.

Prerequisites

Install the Stackwright-patched build of code-puppy:

pip install stackwright-puppy

This provides the raft-puppy binary (and code-puppy alias) with two fixes required for clean-install compatibility:

• MCP servers auto-enable on startup (no manual /mcp start needed)
• Local .code-puppy.json project config loading

Source: https://github.com/Per-Aspera-LLC/stackwright-puppy
Upstream: https://github.com/mpfaffenberger/code_puppy (MIT)

No specific credentials or API keys are required by the raft itself — see Authentication below.

Usage

npx @stackwright-pro/raft [options]

Options

| Flag | Description | | ----------------------- | ------------------------------------- | | --project-root <path> | Project root directory (default: cwd) | | --verbose | Enable verbose logging | | --help, -h | Show help |

Authentication

The raft does not check for API keys or credentials — that is raft-puppy/code-puppy's responsibility. Any auth mechanism supported by your binary works:

• claude auth login — OAuth browser login (interactive sessions)
• ANTHROPIC_API_KEY — Direct Anthropic API key
• AWS Bedrock, Google Vertex, Ollama, custom inference — configured via your raft-puppy/code-puppy setup

If your binary can talk to a model, the raft will launch successfully.

Air-gapped & custom deployments

To skip the binary version pre-flight check entirely (useful when running a custom or pinned binary that reports a non-standard version string):

STACKWRIGHT_SKIP_PREFLIGHT=true npx @stackwright-pro/raft

This bypasses all raft-level validation and spawns your binary directly. The binary itself is still responsible for validating its own environment.

Binary resolution

raft searches for the Python binary in this order:

1. STACKWRIGHT_CODE_PUPPY_PATH env var (explicit override)
2. raft-puppy on PATH (stackwright-puppy fork — preferred)
3. code-puppy on PATH (vanilla upstream — fallback)

If neither is found, the error message will guide you to install stackwright-puppy.

What it does

1. Acquires a pipeline lock (.stackwright/.lock) to prevent concurrent sessions
2. Writes/enriches .stackwright/init-context.json (project name, spec path, theme)
3. Registers the @stackwright-pro/mcp server in .code_puppy/mcp_servers.json
4. Verifies otter file integrity
5. Spawns raft-puppy / code-puppy in foreman mode with STACKWRIGHT_PROJECT_ROOT set

Version

See CHANGELOG.md for release history.