Three pastes, and your assistant knows when to ask. Whatever the work.
| A task | One thing you do once. Reviewing Harbor Foods’ plan on Tuesday. Stet never tracks these; they happen in your chat. |
| A type of task | The category a task belongs to. Plan reviews. Quotes. Meeting briefs. You name each one in a line, and Stet holds how you do it. |
| A rule | One standing instruction, the way you would tell a new hire. It applies to everything you do, or to one type of task, or to one client. |
| Past work | Something you delivered and kept, tagged with its type. The model for the next one. |
| A template | The shape of a document you deliver, with blanks your assistant fills. |
| The manual | All of the above, written down, with where each rule came from. Yours to read, print and take with you. |
Your server address comes with your pilot. Any assistant that can attach a remote connector (MCP) can use Stet; Claude is where pilots run first.
DeepSeek Harness, or any assistant that cannot sign in:
dsh plugin --profile web add dsh-plugin-stet, then start it with the key: STET_ACCESS_KEY=<your key> dsh web. Stet's tools appear on their own. The plugin also turns off DeepSeek Harness's upload of your session log to DeepSeek.Authorization: Bearer <your key>.A key works for the same things your assistant does with Stet, as you, and nothing else. Revoke it in the app and it stops on the next call. In DeepSeek Harness, paste step 2 below into AGENTS.md.
Connecting Stet gives your assistant the tool. These instructions tell it when to reach for it. Paste them once and they apply to every chat.
In Claude: a Project’s instructions, or your personal preferences in Settings. In ChatGPT: Settings › Personalization › Custom instructions.
I use Stet to keep track of how I work. It is connected to you as a tool.
When to use it
- Before you produce anything for me (anything a client will see, or anything I will act on: a quote, a plan review, a report, a meeting brief, a reply), call Stet's recall with the type of task and who it is for, and follow what comes back. My rules in Stet outrank your defaults and anything from earlier chats.
- If it is a type of task Stet does not list, ask me what it is in one question and call define_kind.
- When I describe how a piece of work goes from start to finish, call define_process. When I start one, call start_run and keep the run id; pass it to recall so you see which step we are at and what is owed. When a step is done or handed to someone, call run_step with a pointer to the result (a link or document id), never the text.
- When I correct a draft or tell you how I do something, call Stet's learn with what I said, the type of task, the client, the job, and the process and step it came up at. Don't ask me whether to save it.
How to pass it along
- "Always", "from now on" or "every time": mark it explicit.
- About one client only ("Harbor Foods pays net 45"): mark it for that client.
- About one type of task only ("for plan reviews, lead with the cash runway"): pass the kind.
- "Just this once", "one-off" or "only for this job": mark it once.
- If it changes one of my existing rules, say which rule it replaces.
- "Except when...": add it as an exception to the rule it belongs to.
- "Forget that rule" or "undo": retire it. "Bring it back": restore it.
- "That's not a rule": drop it.
Afterwards, tell me what Stet said in one line. Nothing more.
You draft. I send. Never send anything for me.For a single chat outside that project, start with this instead:
The first message of a chat.
Use Stet for this: recall before you draft, pass along anything I correct, and tell me what Stet says in one line.
One line each: what comes in, what goes out, who it is for. Tell your assistant (“I do business plan reviews: the client’s plan and financials in, a written assessment out”) or add it on your manual page. Rules, past work and templates can then be for that type alone. Nothing to set up before the first one; your assistant asks when it meets a type it does not know.
You never have to confirm anything. Stet decides, tells your assistant in one line, and you can take it back.
| “Always lead with the cash runway.” | A rule, at once. |
| “Invoices are due in 15 days.”, said on two different jobs | Noted the first time. A rule the second. |
| “For plan reviews, never more than six pages.” | A rule for plan reviews only. |
| “Harbor Foods pays net 45.” | A rule for Harbor Foods only, at once. |
| “Just this once, skip the executive summary.” | Followed for this job. Never a rule. |
| “Deposits are 30%, except for repeat clients.” | The rule keeps its exception. |
| “Forget that rule.” or “Undo.” | Retired. It stays retired until you say otherwise. |
| “Bring it back.” | Back in the manual. |
| “That’s not a rule.” | Dropped. |
These rules live in Stet’s database, not in your assistant’s instructions, so they hold whichever assistant you use. Every rule Stet adds on its own shows on your manual page for a week with an Undo button.
Ask this in a new chat. A connected assistant calls Stet and answers that you send everything yourself.
What does my Stet manual say about sending things?