Segue

List or search your saved contexts, and ones shared with you. Use this when the user wants something they've saved but has no handle — "what do I have saved about pricing?", "load my launch notes", "do I have anything on X?" — or wants an overview of recent saves. Search before telling the user something isn't saved. Args: query: Optional search terms. Plain words match in titles and content; "quoted phrases", or-words, and -excluded-words are supported. Omit to list the most recently updated contexts. project: Optional project name to filter by (case-insensitive). Only applies to the user's own contexts. limit: Max results, 1-25 (default 10). scope: "all" (default), "owned" for only the user's own contexts, or "shared" for only ones other people have shared with them. Use "shared" when the user asks what someone sent them. Returns `results` — each with `handle`, `title`, `project`, `updated_at`, and a short `snippet` with **matched terms** marked — plus `count` and `has_more`. Results never include full content: call `load_context(name=<handle>)` to read one. A result with `shared_by` set belongs to that person, not to the user: it is read-only, and it can be revoked or expire at any time. Say whose it is when you show it, and don't offer to edit it — offer to save the user their own copy instead. Matching is keyword-based, not semantic. If a reasonable query returns nothing, retry once or twice with synonyms or broader terms ("auth" -> "login") before concluding nothing is saved. When several results look plausible, show the user the titles and handles and let them choose rather than guessing.

Load a previously saved context by its handle. Pass the handle the user got from ``save_context`` (in this or another AI) to read the saved context back. Only handles saved to the same Segue account resolve. Args: name: The context handle (e.g. "brelavo"). Returns a dict with the ``title`` and ``content`` (Markdown), or an ``error`` if no context with that handle exists for this account.

Save a block of context and get back a short handle to hand to another AI. Use this to capture the state of a conversation, a working brief, research notes, a plan — anything you'd want to pass to a *different* AI so it can pick up where you left off. The content is stored as Markdown. By default this *creates* a new context and returns a short, pronounceable ``handle`` (e.g. "brelavo"). Give that handle to the user; in another AI connected to the same Segue account, they can call ``load_context(name= <handle>)`` to read it back. To *revise* a context you already saved, pass its ``handle`` — this overwrites that context in place (keeping the same handle) instead of creating a new one. Use this when the user asks to update, refine, or correct something already saved, rather than saving a near-duplicate under a new handle. Updating replaces the whole ``content``; it never gets you a new handle. Args: content: The context to save, as Markdown text (max 100,000 characters). title: Optional short label to help the user recognize this context later. When updating (``handle`` given), leave unset to keep the existing title, or pass a new one to change it. project: Optional project name to file this context under. Leave this unset unless the user explicitly asks to add the context to a project. If a project with that name doesn't exist yet, it's created automatically. When updating, leave unset to keep the context's current project. handle: Optional handle of an existing context to overwrite in place. Leave unset to save a new context. Pass a handle you got from a previous ``save_context`` / ``load_context`` / ``list_contexts`` to update that one. Returns a dict with the ``handle``, ``title``, ``project`` (or null), and a ``url`` to view or edit the context in the Segue web app.

Share one saved context with another person by email. Use when the user wants to hand a context to someone else — a colleague, a friend, a client. The recipient gets an email with the context's title and a link. If they have a Segue account, they can load the handle in their own AI; if not, they can read or download it as Markdown and are invited to sign up. Sharing is read-only and revocable. Only the owner of a context can share it. The context body is never included in the email itself. Sending a share requires Segue Pro. On a Free account this returns a plan restriction: explain that sharing is unavailable and do not retry. Receiving, loading and downloading shares is free on every plan. The first time a user shares with a given address, this returns state="pending_confirmation" and a confirm_url — nothing is emailed until the user opens that link. Give them the link and say so plainly. Later shares to the same address send immediately. Args: handle: The context to share (e.g. "brelavo"). Must be one the user owns. email: The recipient's email address. expires_in_days: How long the link stays valid, 1-90 (default 14). require_signin: Set true for sensitive contexts — the recipient must sign in to Segue with that address to open it, and no downloadable copy is emailed. Ask the user before setting this; don't assume. Returns `state` ("sent" or "pending_confirmation"), the recipient, `recipient_has_account`, `expires_at`, and a `manage_url` for revoking. Always report the expiry and that the share can be revoked.