Cookies on Kythene

We use cookies and similar technologies for the things below. You can accept all, reject everything except what's essential, or pick what you're OK with.

Preferences
Remembers things like your last workspace and how you had a list sorted. Improves the experience but the site works without.
Improvement
Anonymous usage measurement so we can fix bugs and prioritise work.
Marketing
Lets us measure whether ads we run send people who actually use the site. We don't share personal data with advertisers.

Read our cookies policy and the privacy policy. California residents: Do Not Sell or Share My Personal Information.

Loading…
kythene
Start free
Self-host licence Start free

Reference

Reference: the Claude skill & plugin

Kythene ships a plugin + skill bundle for Claude Code. One install does two things: it connects Claude to your workspace over MCP, and it teaches your instance the Kythene workflow - so it recalls context at the start of a session, remembers what it learns, publishes work for the team, and picks up feedback, without you having to prompt each step.

You do not need the skill to use Kythene - the MCP tools work on their own (see MCP and assistants). The skill just makes an instance use them well, unprompted.

What the skill teaches

  • Catch up first. At the very start of a session it calls catch-up, so the instance opens knowing what changed while it was away - your other instances' and teammates' publishes, versions, feedback and memory changes since it last looked. That's how "what did the other session do?" gets answered automatically rather than by chance.
  • Recall first. At the start of a session on a connected project, recall the project's memory - decisions, gotchas, conventions, prior findings - and read it before doing anything, so nothing is re-derived. Recall also returns the workspace guide, so the instance follows the team's house style (taxonomy, memory vs collection, what not to store) without being told each time.
  • Remember as you go. Store durable facts and decisions with a title and a project, so what one session learns the next can use. Re-using a title in the same project supersedes the old memory, keeping it current.
  • Keep memory true. When a recalled memory contradicts the live system, correcting it is part of the task. Verify against the real system first, then supersede it (same title and project) or deprecate it with a replacement, and say what changed. Never leave a memory you know to be false in place.
  • Publish your work. Push outputs - a result, a doc, a dataset, a binary - as collections the team and their instances can read, comment on and build on.
  • Pick up feedback. Check the inbox for comments and approvals on your previous publishes and fold them into what you do next.
  • Stay collision-aware. Report what you are working on and check who else (or which instance) is active in the same area.

Install

For the hosted service, in Claude Code:

/plugin marketplace add kythene/plugin
/plugin install kythene@kythene

If you self-host, add the marketplace served by your own instance instead, so the plugin points at your box:

/plugin marketplace add https://<your-instance>/.claude-plugin/marketplace.json
/plugin install kythene@kythene

On older clients that can't add a marketplace by reference, download kythene-plugin.zip from Connect your AI in the app and add it locally as a fallback:

unzip kythene-plugin.zip
/plugin marketplace add ./kythene
/plugin install kythene@kythene

The bundle sets up the MCP connection and installs the kythene-workflow skill. The first time your instance calls a Kythene tool, Claude opens a browser to log you in and authorise it (OAuth) - no API key needed for MCP.

Other clients

The skill is Claude-Code-specific, but the workflow it encodes is not: on any MCP-capable client you can ask your instance to recall, remember, publish and review in plain language, and it will use the same tools. See Getting started to connect a client, and the CLI reference for terminal and scripted use.