The Wisp stack
The Wisp stack splits into local and cloud components.
Local
Desktop app. What you see and click when you open Wisp: chat, your file tree, the diff viewer, the audit log. The app reads folders straight off your disk, never through the cloud or the agent. The binary holds zero API keys or credentials, so there are no baked-in secrets to leak. See The desktop app.
Storage (encrypted). At rest, your chats, audit log, memory and connector tokens live in a ChaCha20-Poly1305 encrypted database on your machine. The encryption key lives in your OS keyring, or, on a server without one, under a key file you keep. Wisp doesn't keep a copy. See Data encryption.
Wisp agent. The Wisp agent runs entirely on your machine. It plans and executes each step: which file to read, which command to run, which tool to call. See The Wisp agent.
Kernel. As an additional privacy and security measure, every agent action goes through
the Kernel first. The Kernel refuses any path into sensitive directories such as ~/.ssh
or into Wisp's own ~/.wisp, keeps the agent's file tools inside your project folder
unless you approve a call outside it (or refuses it outright with the
sandbox on), checks every tool
call against your Permissions (allow, ask or deny), waits for
your approval on ask, and logs every tool call locally. It
also encapsulates encryption and key management, so the Wisp agent has no access to
secrets such as MCP auth tokens: the agent can only ask the Kernel to call the MCP tool.
The agent can decide to do something, but it can't reach around the Kernel to do it on its
own. See The Kernel.
Cloud
Wisp Proxy (Anonymizer). The stateless gateway that forwards your prompts to the LLM and executes identifiable requests (web search, for example) on your behalf, so third parties can't track you or build a profile of you. The Wisp Proxy keeps no database, and runs inside a Trusted Execution Environment (TEE), so nobody at Wisp can see inside. See Wisp Proxy.
LLM. The model itself runs inside a Trusted Execution Environment (Intel TDX), a secure hardware enclave that the chip encrypts with a key it never reveals. The OS, the cloud host, the root user and Wisp's own staff see only ciphertext: no person can read what's inside. See The LLM and Trusted Execution Environments.