jonasbu11/dsh-plugin-stet

Connects dsh to Stet, where your standing rules, processes and past work live: the agent reads your manual before drafting and learns from your corrections.

Before the assistant drafts anything it reads your manual, and when you correct it, your words are passed back; Stet promotes a correction to a rule when you say it explicitly or say it twice. The same manual serves Claude through sign-in and dsh through the key, so the two harnesses do not develop separate opinions about how you work. It is memory as a managed service rather than a local file, which is the right shape if several machines and several agents need the same context.

Memory ★ 0
View on GitHub ↗

Install

dsh plugin --profile web add dsh-plugin-stet

The npm line from the README (dsh-plugin-stet 0.1.0). It is only half the setup: you first make an access key in the Stet app, then start dsh with that key in the environment, as the README's own command line shows. Without the key the Stet connection stays off and nothing else changes.

Compatibility

The connection is an MCP client to Stet over streamable HTTP with a bearer token, so the tools appear to the agent under the Stet namespace. The plugin's patch row also disables dsh's own session log for the official DeepSeek API, and a separate environment variable overrides the Stet address. Revoking the key in the Stet app stops the connection on the next call, which is the revocation story you want for a hosted service.

Details

Alternatives

fonlan/dsh-gitmemo · 863683348/dsh-plugin-focus · ruby1304/dsh-vision-subagent

More plugins in Memory

Browse more in Memory

Guides for Memory plugins