wisp GitHub

Guide

Share a crew member with your team

A crew member in wisp is a long-lived agent with a name, a brief, a schedule and its own skills: a CI watcher, a PR reviewer. Once one works well, share it. Share… gives a .crew.json file, a secret gist or a spell, and your teammate imports it with a review of what it does. It arrives paused, in a project they pick.

Source on GitHub

Free and open source · Claude Code, Codex, Cursor CLI, opencode, Antigravity CLI, Grok Build, Copilot CLI · macOS, Linux, Windows (beta) · Node 20+

{
  "wispCrew": 1,
  "members": [
    {
      "key": "ci",
      "name": "Scout",
      "role": "CI watcher",
      "avatar": "ghost.sky.visor.flat.antenna",
      "brief": "Watch CI on the default branch (`gh run list`). When a run fails, find the cause in its logs (`gh run view <id> --log-failed`) and fix it on a branch, or say why it is flaky. When everything is green, stay quiet.",
      "cron": "*/30 * * * *",
      "on": [],
      "mode": "plan",
      "kit": [
        {
          "kind": "skill",
          "name": "read-ci-logs",
          "description": "When a CI run failed",
          "body": "1. gh run view <id> --log-failed\n2. …"
        }
      ]
    }
  ]
}
scout.crew.json: who the member is. Never a folder, a computer or what they did.

Share one

  1. Open the member and press Share… (its ⋯ menu, right-click, or ⌘K → Share Scout…).
  2. Choose what goes: their skills and instructions (on), their notebook (off: it holds what they learned about your code), and the crew members they delegate to.
  3. Copy it for a chat, Download the .crew.json, or Create a gist: a secret gist on your GitHub account, after you confirm. As a spell saves a spell that brings them.

Before anything leaves, wisp scans the brief, notebook and skills for API keys, tokens and private keys, and won’t share one it finds; it tells you the line.

wisp crew export scout > scout.crew.json
wisp crew export scout --team --gist      # with their delegates, as a secret gist

Import one

Drop the file on wisp, or paste it or the link into Import… (the last chip under Start from when you add a member). The review shows each member with the name they get (a clash becomes Scout 2), the harness they’ll use here, their brief and skills, and the project they work in. One that starts when CI fails needs a project. They join paused: press Resume when you’re ready.

wisp crew import gist:3f2a9c…
wisp crew import https://trywisp.dev/crew/ci.crew.json

Or ask any agent in wisp: add the member from gist:3f2a9c….

The members wisp offers under Start from, as files you can import:

For a team: a spell that keeps them up to date

A spell can bring crew members (crew in the spell). The spell owns who they are and updates them when you publish a new version; each person picks the project and keeps the notebook. When an update changes what a member does, wisp pauses them and shows the change on Resume.

Questions

What does a shared member include?
Their name, face, role, brief, schedule, what else starts them, mode, harness and delegates, and if you tick them, their skills and instructions and notebook. Never their project folder, computer, log or jobs.
Is the gist public?
No. wisp creates a secret gist with your gh login and asks first. It isn’t listed on your profile, but anyone with its link can read it.
What if my teammate doesn’t have the same harness?
The review says so, and the member runs on Auto, which picks a harness they have.
Can a shared member run on its own straight away?
No. Imported members start paused, and a member from a spell shows you what it does before its first Resume.