The Wisp Runtime
Wisp is an AI agent you run on your own machine. You install one program, wisp. It keeps
your credentials and your conversations on that machine and does the work there. The model
it talks to runs inside a trusted execution environment, so the files it reads are never
visible in the clear on the way to the model.
There are two ways to use it, and both talk to the same Runtime:
- From a terminal or a script.
wisp run "…"sends a prompt and prints the answer, the wayclaude -pdoes. - Over HTTP. The
/v1API on127.0.0.1lets your own code (a chat bot, a webhook handler, a scheduler) turn its events into Runs.
If you also use Wisp Desktop on the same machine, the CLI talks to the Runtime inside the app while it is open, and your Sessions and connectors are shared between the two. The app can also work with a Runtime you run on a server, over SSH: see Connect to a server.
Where to go next
| You want to… | Read |
|---|---|
| Install it and get a first answer | Quickstart |
| Run it as a service, update it, remove it | Install, update, uninstall |
| Use it day to day from the terminal | Using the CLI |
| Know where a conversation's files live, and tie it to a folder | Sessions and Projects |
| Change a setting, open it to the network, pick the default model | Configuration |
| Know what pays for a Run, top up the balance | Plan and balance |
| Give the agent access to GitHub, Drive, your Telegram account, your own MCP servers | Connectors |
| See which tools the agent has | Tools |
| Decide which tools may run unattended | Permissions |
| Teach the agent a procedure, or give it standing instructions | Skills, Instructions |
| Run a prompt on a timetable | Schedules |
| Send it voice, images and documents, get files back | Voice and files |
| Talk to the agent from Telegram or Slack | Telegram bot, Slack app |
| Run it on a server and use it from Wisp Desktop | Connect to a server |
| Reach it from another machine, a token per device | Remote access |
| Ship an agent as a folder you can check out on a server | Deploying an agent |
| Call Wisp from your own code | The adapter contract and a worked example |
| Keep it running | Runs and restarts, Troubleshooting, Security |
| Look up a command, route or setting | Reference |
Words used on this site
- Runtime: the running
wisp serveprocess (or the one inside Wisp Desktop). - Session: one conversation. It keeps its history between Runs and across restarts.
- Run: one prompt sent to a Session, and the agent's work until it answers.
- Project: the folder a Session works in. The agent's file tools work there; a call outside it asks first (with the sandbox on, it is refused).
- Connector: an MCP server that gives the agent more tools. The built-in Telegram connector signs in as your own account, so the agent can read it.
- Channel: a messenger you write to the agent through:
wisp telegramorwisp slack. - Rule: a decision (
allow,askordeny) for one tool, globally or for one Project.