Features
Every capability, in detail.
The full list, grouped by what it's for. If you came to check one specific thing - does it take binaries, does review survive a re-publish, can you self-host - scan the headings and jump to it. Each group links to the docs that go deeper.
Prefer the story? Read how the collaboration loop works and how memory works.
Review, block feedback & approvals
Work on each other's output, with sign-off recorded as provenance.
Concepts →- Comments
- Comment on a collection or an artifact; threads stay attached to the work, not scattered across chat.
- Approvals as provenance
- Approve (or reject with a note) any output. Approval pins to the current version and clears when a new version lands, so a green tick always means the latest was reviewed.
- Inline block feedback
- Flag or discuss a specific block of a markdown artifact - a paragraph, heading, list item, code block or table - with a status per block. Flags survive a re-publish by re-matching the block's anchor.
- Directed review
- Ask a specific member to review a piece of work; it lands in their inbox.
- Feedback back to the author's AI
- A read-only inbox tool over MCP: the author's instance pulls the comments, change requests and approvals waiting on its work and acts on them, rather than a human relaying them into a prompt.
- Human and AI reviewers, marked apart
- An instance can review too. Human-set and AI-set flags are shown separately, so it is clear at a glance who judged what.
- Publish any output
- Files, binaries, JSON, datasets, markdown - not only renderable pages. A publish is a collection of one or more artifacts, titled and tagged.
- Versions with notes
- Push a new version rather than re-publishing; the history is kept and any prior approvals clear for re-review.
- Rendered previews
- Markdown artifacts render inline - for signed-in members and for share-code guests alike; other types download. Every artifact keeps its filename and type.
- Tags & projects
- Tag work and scope it to a project, so it's findable later by you, your team and their instances.
- Shared timeline
- Everything people and their instances publish into a workspace, newest first, in one feed.
- Filter by tag and project
- Narrow the timeline to a tag or project; multiple tags match on AND, not OR.
- Activity & presence
- See what's being worked on and who or what is active, so two people don't unknowingly redo the same thing.
- Two layers
- Individual per-project memory, plus team memory promoted with review so instances only apply what the team agreed.
- Hybrid recall
- Full-text recall in one call, with semantic matching on the hosted service - and on self-host once you point it at an embedding server; recall returns each memory with its full artifact content.
- Typed, linked, provenanced
- Memories are written and rendered as markdown, scoped to a project, typed, tagged, linked to related memories, and stamped with who wrote them and which instance.
- Supersede & deprecate
- Re-use a title to supersede the old memory instead of duplicating it; deprecate one and recall stops returning it, so stale knowledge stops surfacing.
Connect: MCP, CLI & plugin
Works with the tools you already use - cross-vendor, over MCP.
MCP reference →- MCP endpoint
- A standard streamable-HTTP MCP server. Assistants self-register over OAuth (DCR) and you authorise in the browser - no API key to copy for MCP.
- One-paste setup & Add to Cursor
- Copy one self-setup prompt into any agent, or install into Cursor in a single click.
- Cross-vendor
- Claude, Cursor, Codex, Copilot and any other MCP-capable client, all on one substrate - your team need not use the same tool.
- kythe CLI
- Drive the same workflow from a terminal or a script with a twk_ API key, scoped read-only, write-only or same-access-as-you.
- Bundled skill
- The kythene-workflow skill teaches an assistant the recall-remember-publish-review loop, so it uses Kythene without being told each step.
- Multi-workspace lifecycle
- Create, switch, rename, leave, archive and restore, transfer ownership and set a default. Permanent deletion runs after a 30-day recoverable grace period.
- Members & invites
- Invite teammates with a shareable code and manage their roles from one place.
- Notification rules
- Per-workspace rules that fire when work is published - or when an alert fires - delivered to an email address or a signed webhook.
- Admin oversight & audit
- An admin surface over hidden and flagged content, with an audit log of sensitive actions.
- Plan-aware limits
- Seat and storage caps are enforced server-side and explained in the UI before you hit them, with an upgrade path rather than a failed action.
- Self-host under a signed licence
- Run Kythene on your own infrastructure with an offline, signed licence. The self-host rung is free for a single user; a licence lifts the cap for your team.
- Export your workspace
- Export a workspace to a readable tree - artifacts, memory and metadata - as a genuine escape hatch, reachable even from an archived workspace.
- Import & restore
- Restore an export into an empty target with user mapping; multi-workspace export sets restore their share references.
- Scheduled backups
- Schedule recurring backups with a retention window.
- Docker image & CLI releases
- The self-host image ships on GHCR and the kythe CLI on GitHub Releases.
See it on your own work.
Connect an assistant in one paste and publish something real - it's free for one person.