DeepWind CLI installer

Install DeepWind in one command

Install the same disciplined harness lifecycle for Claude Code, Codex, or both. Choose before you run it; Both is the default. Re-running the versioned installer updates managed files safely.

Choose your coding agent

One installer. Your target.

Both is the default.

Both install
curl -fsSL https://deepwind.ai/install | bash -s -- --target both

Connect DeepWind after the files are installed

MCP setup is opt-in. Add --configure-mcp to open an OAuth flow in your browser after you type yes in an interactive terminal. The installer never copies or transfers credentials to another agent.

install + connect Codex
curl -fsSL https://deepwind.ai/install | bash -s -- --target both --configure-mcp

If deepwind doctor reports No workspace found, authentication succeeded but your account is not assigned to a workspace. Ask your DeepWind admin to add you, then run the doctor again.

Latest release v1.1.14 published . Re-published every Monday from DeepWindAI/harness.

Tested on macOS and Linux. Requires curl and tar. Depending on your target, managed files go to ~/.claude/, ~/.deepwind/, and ~/.codex/agents/ — never root, never sudo.

Prefer to clone + inspect first? Browse the public repo on GitHub — git-clone + ./install.sh is an equivalent path.

How the skills compound

Each bundled skill is a load-bearing checkpoint — skipping any one is how harnesses fail. The workflow runs end-to-end:prep→ plan→ review→ coordinate→ execute.

The lower band of the diagram lists, per skill, the failure mode when it's skipped. Click to enlarge; switch site theme to see the dark/light variant.

What gets installed

Target-specific archives are published as immutable GitHub Release assets with checksums and signed release metadata. Review the latest release before piping the installer to bash or preparing an offline install.

~/.deepwind/install/ + ~/.codex/agents/ · Codex
  • codex-marketplace/
    A verified local marketplace containing the versioned DeepWind harness plugin and shared skills.
  • agents/*.toml
    Connector-free Codex roles. Strategic MCP reads and writes stay with the coordinator.
~/.claude/agents/ · DeepWind harness roles
  • harness-coordinator.md
    Orchestrates multi-session harness work. Delegates to specialists; never writes code.
  • harness-planner-agent.md
    Breaks 16+ hour projects into phased tasks with TDD plans.
~/.claude/agents/ · Specialist agents (from wshobson/agents, MIT)
  • ai-engineer.md
    Production LLM apps, advanced RAG, multimodal AI, agent orchestration.
  • api-documenter.md
    OpenAPI 3.1, AI-powered docs, SDK generation, developer portals.
  • backend-architect.md
    Scalable APIs, microservices, REST/GraphQL/gRPC, distributed systems.
  • code-reviewer.md
    AI-assisted code review, security vulnerabilities, performance, production reliability.
  • database-admin.md
    PostgreSQL ops, schema design, RLS policies, performance tuning.
  • frontend-developer.md
    React 19, Next.js 15, accessibility, responsive layouts, state management.
  • performance-engineer.md
    OpenTelemetry, load testing, Core Web Vitals, multi-tier caching.
  • security-auditor.md
    OWASP, OAuth2/OIDC, threat modeling, GDPR/HIPAA/SOC2 compliance.
  • test-automator.md
    AI-powered test automation, self-healing tests, CI/CD integration.
  • ui-ux-designer.md
    Design systems, wireframes, design tokens, inclusive design.
~/.claude/skills/ · Claude Code
  • deepwind-mcp/
    DeepWind MCP tool conventions — load before any pm33_* call. Tool routing, the 9 known gaps (5000-char description cap, score_alignment is keyword-only, MCP intermittent disconnect), batch-creation patterns, queue-and-execute fallback.
  • harness-prep/ ★ Phase 0
    Orchestrator entry point. Sequences discovery + brainstorming (always) + bounded research (conditional) into one enriched doc that harness-planner consumes. Skipping this is the root cause of 5-10x over-estimates. Requires the superpowers plugin for the brainstorming pass.
  • harness-discovery/
    Internal-audit pass — what already exists in the codebase that the plan can reuse?
  • harness-research/
    Bounded external research (1+3 search budget, hard cap 2+6). Use only when scoping requires outside-codebase context. Decay-tags findings so stale citations don't cargo-cult into future plans.
  • harness-planner/
    Plans the harness from the prepared discovery doc.
  • harness-coordinator/
    Coordinator workflow rules + progress.json patterns.
  • harness-discipline/
    TDD discipline for specialist agents. RED → GREEN → REFACTOR → DELIVERY.
  • gauntlet-review/
    Multi-specialist adversarial spec review (backend, security, performance, AI engineer, etc.) before implementation.
  • feature-enhancements/
    Pending-feature triage + readiness assessment workflow.
~/deepwind-frameworks/
  • HARNESS_PROJECT_TEMPLATE.md
    Section-by-section template for a new harness project.
  • LONG_RUNNING_AGENT_FRAMEWORK.md
    The full framework reference (long read).
  • HARNESS_TASK_DEFINITION_TEMPLATE.json
    Per-task JSON skeleton.
  • CLAUDE.md.starter
    Starter DeepWind-aware CLAUDE.md fragment for your project root.

After install — 5 steps

~5 minutes from install to running your first harness-planned project.

  1. 1
    Restart your selected coding agent

    Claude Code and Codex discover newly installed agents, roles, plugins, and skills when a new session starts.

  2. 2
    Run the local doctor

    Run deepwind doctor. It checks the selected target files and reports sanitized MCP status without reading OAuth token files.

  3. 3
    Connect DeepWind from the coordinator

    MCP authentication is a separate, explicit browser OAuth step. Keep it in the interactive coordinator session; specialists use filesystem skills and return proposed reads or writes.

  4. 4
    Add project-level guidance

    Review your project guidance before adding harness instructions: CLAUDE.md for Claude Code or AGENTS.md for Codex. Preserve any instructions already there.

  5. 5
    Try the harness flow

    On a non-trivial project, ask your agent to prep a harness, plan it, run the gauntlet, and resume as coordinator. The same lifecycle applies to both targets.

The deepwind CLI

Installed alongside the harness bundle. Works outside an agent session for status checks, manual updates, and opt-in daily auto-update.

deepwind status

Installed version, latest available, auto-update state.

deepwind update

Re-run the installer to upgrade in place. Idempotent.

deepwind doctor

Validate selected-target files and report sanitized MCP status.

deepwind enable-cron

Opt in to daily auto-update via launchd (macOS) or systemd (Linux). OFF by default.

deepwind disable-cron

Remove the cron entry.

deepwind version

Print the local installed version.

Auto-update is opt-in. The installer never enables cron-driven updates — you run deepwind enable-cron when you want them. The daily cron job uses deepwind update --quiet --if-newer --skip-if-claude-running so it never swaps managed files while an agent session is mid-feature.

Before you pipe to bash

Inspect the script first (recommended)

Open it in your browser, read the source, then run it once you're happy.

Browse the immutable tagged release assets

Inspect the bundle contents

To inspect v1.1.7, download the archive for your target and list it before extracting. For both targets, inspect both archives.

# Claude Code
curl -fsSLO \
  https://github.com/DeepWindAI/harness/releases/download/v1.1.7/deepwind-harness-claude-v1.1.7.tar.gz
tar -tzf deepwind-harness-claude-v1.1.7.tar.gz

# Codex
curl -fsSLO \
  https://github.com/DeepWindAI/harness/releases/download/v1.1.7/deepwind-harness-codex-v1.1.7.tar.gz
tar -tzf deepwind-harness-codex-v1.1.7.tar.gz

The installer verifies the signed release manifest, then checks each archive against its published checksum before extracting it. Browse every published version on GitHub.

Remove a target safely

Follow the removal steps in the installed release README. Codex removes the plugin and marketplace registration before managed files; Claude Code removal uses the release state file. Locally changed files are reported and retained.

New to the DeepWind harness framework? Read the 25-minute walkthrough in the curriculum.