Sasha MCP reference

What's new

2026-11-16: Scheduled sending of CRM drafts, from chat

On a CRM Agent whose schedule is ready, four new tools work with its Schedule tab, for admin and staff. app__<app>__list_schedule reads which messages go when, each with its state in words (Scheduled, Needs approval, Held with the reason, Changed after approval, Missed, Did it go?, Draft) and its time in the agent's time zone; the draftId of each is in the structured part only. app__<app>__schedule_drafts asks the person to approve 1 to 50 messages for their times: it works only in chat in the Sasha web interface, where the person reads each message on a card and ticks "I have read each message I am approving" before the button works. You send draft ids and, if the person asked, a day and time; you never send a hash. Sasha then sends each message at its time, exactly as approved. app__<app>__stop_schedule and app__<app>__set_draft_day stop a message or reschedule it, and ask the person as bin_draft does. The work log has a new kind, scheduled, for these changes. No new scope, so no reconnect is needed. See Report tools.

2026-11-14: One question to bin many drafts, and a new bin reason

On a report app with drafts (the CRM Agent), the new tool app__<app>__bin_drafts bins 1 to 50 drafts with one reason, and the person answers one box for all of them, not one box per draft. The drafts are binned all together or not at all; when one stops the bin, the answer names it in drafts. When a person asks to bin more than one draft, call it once with every id, never bin_draft in a loop. Admin and staff have it, with the same apps:invoke scope, so no reconnect is needed. Both bin tools take a new reason, already-hears (They already hear from us), beside stale, wrong-person, not-now and other. A bin of a draft that was edited or given a new To after the person was asked now asks again. In the Sasha web interface the person's answer to a box arrives as a message that ends in a <sasha-confirmation> block: call again with the token only when its verdict is approve. See Report tools.

2026-11-04: Claude Desktop jobs

Some work needs clicks on a web app's own screens that no tool can make. A chat in the Sasha web interface now prepares such a job with createClaudeDesktopJob, and the person approves the whole text in a Confirm box. Claude Desktop then lists, reads, asks about and reports the job with listMyClaudeDesktopJobs, getClaudeDesktopJob, askAboutClaudeDesktopJob and reportClaudeDesktopJob, and the chat reads the result with checkClaudeDesktopJob. Only the person who approved a job can see it. The four Claude tools need the new scope jobs:run, which is in the admin and staff default grant: a connection approved before the release that added it must reconnect to get it. The prompt menu has the recipe Do a Sasha job in Claude Desktop and report it back. Members do not have these tools.

2026-11-03: A report's tables refuse a person before the Confirm box

A person cannot write the tables of a report app (for example the CRM Agent's drafts) with the per-table tools. Until now a person's app__<app>__<table>__create, __update or __delete call showed a Confirm box and was then refused with app_access_denied. Now the call is refused at once with APP_AGENT_TABLE_READ_ONLY, no Confirm box is shown, and the tool description says so. To change a draft, use edit_draft, bin_draft or send_draft. See Report tools.

2026-10-25: A pricing skill on every Sasha

Every Sasha now has the skill pricing-coach, so an admin or staff connection sees the tool skill_pricing-coach. It takes offer (required, a sentence on what is being priced and who buys it) and project (optional). It reads the organisation's pricing documents, works out a recommendation with a fairness check, saves a pricing note at pricing/<offer-slug>.md in the project, and names it as outputPath in checkExecution. It asks no questions in a run: what it could not answer is listed in the note. See Skill tools. The prompt menu also has the recipe Work out what to charge for an offer, which does the same in the conversation and only reads.

2026-10-21: Folders synced from GitHub

An admin can connect a folder of a GitHub repository to a project. listProjects now shows a syncedFolders list on a project that has synced folders, and the new tool syncFolder syncs one now. The tool needs synced-folders:sync, which only an admin holds and which is not part of a default grant: an admin's chat in the Sasha web interface has it, and another client must ask for it by name.

2026-10-19: Each role has its own brief

Each role now has its own brief, the file skills/<agent id>/brief.md. The Our business and Settings tabs are one tab: Finance Brief, Marketing Brief. The tool app__<app>__set_setting is gone. Change a brief on its tab, or edit the file in Studio chat. See Report tools.

2026-10-18: A Confirm box in Studio chat, and the Our business page

In the Sasha web interface, a change through an app tool (the app-table, app-action and report-agent families) now waits for the person. Sasha shows a Confirm box in the chat. The confirmationToken works only after the person presses Confirm, never after Decline, so call the tool again only when the person says they confirmed. Other clients keep MCP form elicitation. See App table tools and Report tools.

A report's products, accounts, suppliers and shared-cost rules now live on one document, company/our-business.md in the Company project, not in its settings. (History: on 2026-10-19 each role got its own brief, and this page was replaced.)

2026-10-17: Tools by job, and this page

The reference has two new pages: Tools by job, which groups every tool and family by the job it does, and this page.

2026-10-11: Members can survey the public context

The member-survey family adds surveyPublicContext and checkSurvey. A member starts a contained run that reads public sources about the business, then polls for its result. The connection must ask for skills:run-contained by name. See the family page.

2026-10-03: A guide to brains

The guide Work with brains shows how to read a brain's contents page and search inside it.

2026-10-02: The public reference, and the brain tools

The first public edition of this reference: one page for each tool and tool family, guides, the getDocs sections, scopes, prompts and resources. The same release added the brain tools listBrains, getBrain, getBlueprint and searchBrain.

Built with BernardCookie settings