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…

Managing your workspace

Your account

Your account is you, across every workspace you belong to. Workspaces come and go; the account, its sign-in methods and its personal data don't.

Sign-in methods

Settings -> Sign-in methods lists the identities linked to your account. Link more than one and any of them gets you in - useful when you sign in with a work provider and later need a personal route, or when a provider is having a bad day.

On the hosted service, sign-in is with GitHub or Google. Self-host installs can enable GitHub, Google, Microsoft and Apple, plus local email and password - see Self-hosting.

API keys

MCP connections don't use API keys. An assistant registers itself over OAuth and you approve it in a browser, so there's no secret to copy into a config file and no key sitting in your shell history.

API keys exist for the CLI and for scripts. Create one on Connect your AI; it's shown once, at creation. Treat it as a credential: it acts as you.

If a key leaks, delete it - the CLI is the only thing that uses one, so rotating it costs you an export line.

Timezone

Set your timezone on your profile so timestamps read the way you expect. It's per-user, so a distributed team each sees times in their own.

Your data

Two things live on your profile page:

  • Export your data - your personal data, as the subject-access route. This is distinct from a workspace export, which is a workspace backup and is restricted to owners and admins.
  • Delete your account - schedules deletion, and it's cancellable while pending. Work you published into a shared workspace stays part of that workspace's record, correctly attributed, so the team's history doesn't develop holes.

Email

Kythene sends transactional email only - things like notification rules you set up, and onboarding mail that stops as soon as you're set up.

Every message carries a one-click unsubscribe. Unsubscribing doesn't affect the product, only what lands in your inbox.

Instances

Your instances inherit your access. An instance connected to your account sees the workspaces you're a member of, publishes as you, and is attributed to the producer name it reports - which is what lets provenance say "Ana's Claude Code instance" rather than just "Ana".

If you stop using an assistant, remove the Kythene connection in that client. Anything it published stays in the workspace, correctly attributed. API keys used by the CLI are revoked from Connect your AI, which takes effect immediately.