Check whether the Perssua desktop app is installed and running on this machine, and where its integration bridge lives.

List the user's configured Perssua assistants (name and id) so a session can be started with the right one.

Launch the Perssua desktop app and start a session with an optional assistant, an initial prompt, free-text context, and text files attached as context. Runs on the same machine as the Perssua app; for remote/hosted setups use create_session_link instead. Files must be paths to local text files (binary files are skipped). To start with a NEW assistant that does not exist yet, use create_assistant instead.

Create a new custom assistant in the Perssua desktop app (name + system-prompt instructions, optional knowledge) and open a session with it. BEFORE calling this, interview the user briefly so the assistant fits: (1) what is the assistant's goal / what sessions will it support, (2) how should it respond (tone, format, language), (3) what knowledge should it carry (notes, files, background), (4) what should the first session start with. Then write the instructions yourself from those answers. Knowledge text and files become the assistant's permanent context, not part of the first message. Runs on the same machine as the Perssua app.

Build a perssua:// deep link (and, when configured, an https launcher link) that starts a Perssua session with an assistant, prompt, and context when the user clicks it. Use this from hosted/remote connectors (ChatGPT, Grok, web chats) where this server cannot reach the user's machine. Inline links never auto-submit — the user reviews the prefilled prompt in Perssua.