A toolkit is a bundle of the workspace's servers and skills that you give to a group of people. It's how you decide whose AI gets what: the sales team gets the CRM and the refund skill, support gets the helpdesk, and nobody's AI is wading through tools they'll never use.
Nothing reaches a member's AI until a toolkit gives it. That goes for a server's tools, prompts and skills, and for the workspace's own published skills. A workspace with servers and skills but no toolkits serves none of them to anyone. Kythene's own tools aren't affected.
It's on the Team and Enterprise plans, and on self-host with a licence that includes it. Owners and admins build toolkits; everyone else just gets what theirs hold.
Making a toolkit
Settings > Toolkits > New toolkit. Give it a name (up to 60 characters) and, if you like, a description of who it's for. Then choose what goes in and who gets it, and Create toolkit.
Servers. Tick Give next to a server and it brings everything it offers: all its tools, prompts and skills. The line above the tick says how many of each, and how many tools are destructive. Once it's ticked, each tool, prompt and skill has its own box. Untick one to leave it out.
- Everything is on unless you switch it off, and anything the server adds later is on too. A toolkit that leaves out the three tools you don't want doesn't need touching when the server gains a fourth.
- Tools that can delete or overwrite things are marked Destructive. That's what the server says about them, the same kinds its own page shows.
- A server that's switched off can still be ticked, but nothing of it reaches anyone until it's enabled.
Workspace skills. Skills the workspace wrote aren't tied to a server, so you pick them one by one. A draft, archived or deleted skill can be ticked too, but it reaches nobody until it's published or restored.
Members. Tick who gets the toolkit. Each name shows their role and, where they hold any, the other toolkits they're already in, so you can see what they'd get anyway.
Save toolkit says how many members' AI changed. Connected AI picks the change up without reconnecting.
What a member gets
A member can be in several toolkits. Their AI gets everything in all of them, each thing once. Two toolkits that both hold the CRM give them one CRM, with a tool on if either toolkit has it on. Someone in no toolkit gets none of the workspace's servers or skills.
Viewers get only the read-only tools, whatever a toolkit says. Prompts and skills reach them as they would anyone.
Your own drafts stay on your own connector, whatever the toolkits say. A skill you're still writing isn't given to anyone by being in a toolkit.
A call to something no toolkit gives you is refused.
Signing in follows the kit
A member connects to a server once, on My tools, and My tools lists only the servers their toolkits hold. If a toolkit change takes a server out of their kit, Kythene deletes their sign-in to it and asks the server to end it, so no credential sits around for something they can no longer use. Giving it back later means connecting again.
- Removing a member from one toolkit doesn't sign them out of a server another of their toolkits still holds.
- Owners and admins keep their sign-ins whatever toolkits they're in. It's how they refresh a server's list of tools and manage it, so a toolkit change never takes it.
- A sign-in a member still has to a server they no longer get stays on My tools with Disconnect only, so they can remove it themselves.
- Taking a server out of the workspace, or a member out of it, signs them out too.
When a server couldn't be told to end a sign-in, the confirmation says so, because that server may still list Kythene as signed in.
Changing and deleting
Saving a toolkit changes what its members' AI gets straight away, and the confirmation counts them. Delete takes it away: its members lose anything only it gave them, and their sign-ins to servers they no longer get are ended. Someone who's also in another toolkit that holds the same thing loses nothing.
A member who leaves the workspace is taken out of its toolkits at once.
Each server's page lists the toolkits that hold it. On Settings > Servers and Settings > Skills, a server or skill in no toolkit says Not in any toolkit, so no one gets this yet.
In the audit log
Each audit log entry names the toolkit that gave the member the tool or prompt. If two did, it names both. A call a toolkit didn't grant never reaches the server, so it isn't in the log.
Starting out
A toolkit for everyone is the way to keep today's behaviour: put in the servers and skills the whole workspace had, tick every member, and nothing changes for them. Nothing makes one for you, because which members get which tools is a decision about your workspace, not ours.