paseo-crew

{
  "name": "paseo-crew",
  "version": "0.1.5",
  "description": "The orchestrator/worker session model over Paseo. An orchestrator session keeps its context for decisions and dispatches everything else to worker sessions launched by seat name as Paseo subagents: Paseo profiles are the seats (read with list_profiles) and .paseo-crew/roles.md names which fills each role, implementers route by complexity class, one reviewer session runs /code-review once per PR, the retained implementer works GitHub threads to zero, merge only on the operator's word. A session budget caps each work item at one implementer and one verifier. A worker's report file is its finish: one background wait per dispatch returns on the report, once the seat that wrote it is `idle`, or on an attention state (a pending permission, idle with no report past a settle window, an error, the time budget), a heartbeat catches a lost wait, and Paseo's one-shot finish notice is only a hint. A handoff launches its successor detached and verifies it has no parent; a predecessor is never archived while its seats run. A run's state lives in a dagr run.json. One fail-open hook, on Claude Code only, tells a seat its own context figure past a configurable ceiling (default 500000 tokens). A spine's spine and close seats can be a DeepSeek Harness session (kind dsh-spine-driver, with dsh-crew). No lib, no state.",
  "author": {
    "name": "Pras"
  },
  "repository": "https://github.com/pulseai-labs/claude-agent-scaffolding",
  "license": "MIT",
  "keywords": [
    "orchestration",
    "paseo",
    "multi-agent",
    "code-review",
    "skills"
  ],
  "skills": "./skills/",
  "interface": {
    "displayName": "Paseo Crew",
    "shortDescription": "Orchestrator/worker session model over Paseo.",
    "longDescription": "Paseo Crew states who does what when one orchestrator session drives worker sessions through Paseo: which named seat fills each role, what a brief must carry, where the orchestrator stops and dispatches instead, one code review per PR with findings returned through the seat's report file, GitHub threads worked to zero, and a merge only on the operator's explicit word. It defers every other Paseo command to Paseo's bundled paseo skill and its own MCP tool descriptions.",
    "developerName": "Pras",
    "category": "Coding",
    "capabilities": [
      "Interactive",
      "Read",
      "Write"
    ],
    "defaultPrompt": [
      "Start a Paseo orchestrator session for this objective.",
      "Dispatch a Paseo worker seat for this task.",
      "Review PR 123 in a fresh Paseo seat."
    ],
    "websiteURL": "https://github.com/pulseai-labs/claude-agent-scaffolding/tree/main/paseo-crew",
    "brandColor": "#1D4ED8"
  }
}

{
  "name": "paseo-crew",
  "version": "0.1.5",
  "description": "The orchestrator/worker session model over Paseo. An orchestrator session keeps its context for decisions and dispatches everything else to worker sessions launched by seat name as Paseo subagents: Paseo profiles are the seats (read with list_profiles) and .paseo-crew/roles.md names which fills each role, implementers route by complexity class, one reviewer session runs /code-review once per PR, the retained implementer works GitHub threads to zero, merge only on the operator's word. A session budget caps each work item at one implementer and one verifier. A worker's report file is its finish: one background wait per dispatch returns on the report, once the seat that wrote it is `idle`, or on an attention state (a pending permission, idle with no report past a settle window, an error, the time budget), a heartbeat catches a lost wait, and Paseo's one-shot finish notice is only a hint. A handoff launches its successor detached and verifies it has no parent; a predecessor is never archived while its seats run. A run's state lives in a dagr run.json. One fail-open hook tells a seat its own context figure past a configurable ceiling (default 500000 tokens). A spine's spine and close seats can be a DeepSeek Harness session (kind dsh-spine-driver, with dsh-crew). No lib, no state.",
  "author": {
    "name": "Pras"
  },
  "userConfig": {
    "context_ceiling": {
      "type": "number",
      "title": "Context ceiling (tokens)",
      "description": "Past this many tokens of context, a paseo-crew coordinator seat (the top, a spine session, a work-PR session) is told to finish the unit in hand, start no new one and rotate at its next boundary. Any JSON number of 1 or more is taken as the ceiling: a context figure is a whole number of tokens, so a fractional setting takes effect at the next whole token (100000.5 fires at 100001). A value below 1, or a spelling that is not a JSON number, is ignored and 500000 applies. 500000 is half a 1M window.",
      "default": 500000,
      "min": 1
    }
  }
}