Skip to content

Pi

Start Pi on your computer and follow or steer it from the web client, your Sesame agent, or its own terminal. Pi is available to all verified Sesame accounts.

Install Pi CLI on the computer running Sesame Link, with pi on your PATH, a Node version supported by Pi, and tmux 3.4 or newer. On macOS, install tmux with brew install tmux.

Check the installation, then open Pi:

Terminal window
pi --version
tmux -V
pi

Run /login inside Pi to connect a provider, then send it a message to check that authentication works. See Pi’s setup guide.

If Sesame Link was already running when you installed or updated Pi, run sesame-link restart. Run sesame-link status to check that Pi is available.

In the web client, select Pi when creating a session, or ask your Sesame agent to start a Pi session. Choose a model and thinking level, or keep Pi’s defaults. From the terminal, run:

Terminal window
sesame-link pi

This starts Pi in the current folder and attaches to its terminal. To choose a model or thinking level when starting it:

Terminal window
sesame-link pi --provider anthropic --model MODEL --thinking high

Use a model available to your authenticated provider. You can change the model and thinking level with a later message; a change during a turn applies from Pi’s next model request.

Terminal window
sesame-link sessions attach <id-or-name>

The terminal and your remote clients share the same Pi session. Disconnecting the terminal or restarting Sesame Link leaves Pi running. Pi keeps its own extensions, drafts, and conversation history. If a native dialog needs an answer, attach to the terminal to answer it.

You can send another message during a turn to steer Pi. If Sesame Link cannot confirm delivery, check the conversation before sending it again. It does not automatically resend uncertain input.

When Pi is idle, send /compact, optionally followed by instructions, to compact its conversation. If there is not enough older history to compact, Pi reports that instead.

/reload reloads Pi’s extensions when the computer allows it. The owner can enable it in the remote slash-command settings.

End the session from a client or run sesame-link sessions delete <id-or-name>. This stops Pi’s process; the saved conversation remains in Pi’s history on your computer.