Skip to content

Import a wisp home

Have a wisp home from another install, or a ~/.wisp folder copied from another computer? Its setup and its task history come in with one command. It shows its plan first and changes nothing until you say yes.

Import

Importing runs in a terminal. Run the CLI command, then open the desktop app: what came in is already there.

What comes over

It reads the home’s config.json and its sessions folder, and brings in:

  • Projects. A project whose folder isn’t on this computer is left out, and the plan says so.
  • Defaults, as settings: your default harness, model and effort among them.
  • Recipes, as declared tasks.
  • Automations and schedules, as triggers.
  • Crew members and teams.
  • Machines and connectors.
  • Task history: every task with its transcript and its changes per turn. Tasks are history, so they are imported, never planned. A task already imported is skipped, so you can run the import again.

The plan shows each change as wisp apply would. Notes under it name anything that didn’t carry over: a spell, for one, isn’t imported; Make wisp your own shows how to build it as a plugin, or ask an agent to.

Secrets

Tokens and keys are never written into a plan. A connector’s environment or a channel’s token that wisp already has becomes a ${secret:NAME} reference. Any other is named in the plan’s notes. Set it with:

Terminal window
wisp secret set NAME # typed hidden, or piped: echo "$TOKEN" | wisp secret set NAME

Keep your setup in the repo

After importing, write it out as a formula you can review and commit:

Terminal window
wisp export > .wisp/setup.wisp.yml

See Formulas.