Agents and plugins
Agents
An agent is a saved profile: a name, a persona prompt, a graph permission and a default model. You start sessions from it. The full guide is Graphs and agents → Agents.
Default: no agents. While no agent exists, the pane shows four templates: Vision keeper (manage), Project manager (write), Worker (read) and Reviewer (read). Click one to save it as a new agent with its persona prompt, then change it. See Start from a template.
Your edits are a draft until you click Save. Other buttons: Duplicate, Start session… and Delete. When you delete an agent, its sessions stay. They lose the persona and the badge, and keep the permission they started with.
Name and colour
What it does: the name is the session name when you start a session from the agent, and the agent's name in its system prompt ("You act as the Splitkick agent …"). The colour marks the agent in lists.
Persona prompt
Default: empty
What it does: added to the system prompt of every message in every session of this agent, for all backends, together with the graph nodes that the session serves. Splitkick reads it when a message is sent, so an edit reaches existing sessions with their next message.
Why change it: write in words what the agent may decide and how it works. Only the graph permission below is enforced by Splitkick.
Cost: the persona and the graph text are extra input tokens on every message.
Graph permission
Default: read
What it does:
- read: read graphs, set what its own session serves.
- write: also make and change nodes, relations and attachments, propose, send requests.
- manage: also commit, accept done work and drop nodes.
A session gets the permission when it starts. You can start a session with a lower permission, never with a higher one. A later change to the agent does not change running sessions.
Default backend
Default: Session default (the backend that you select when you start, or Default backend)
What it does: the backend of a new session from this agent. When you select a backend in the start dialog, your choice wins. When you change this field, Default model goes back to Session default.
Default model
Default: Session default
What it does: the model of a new session from this agent. For Claude and Codex you select from a list. For other backends you type the model name, and Splitkick does not check it. The model applies only when the session runs on the agent's own backend.
Default serves
Default: Nothing
What it does: the graph, or one node of it, that a new session of this agent serves, unless you select something else in the start dialog. The served nodes go into the system prompt.
Opinionated
Recommended Plugins: three tools that Splitkick can install for you. Nothing is kept in the Splitkick settings: the pane checks each time if a tool is installed. Each card has Install and Refresh, and shows how to use the tool.
RTK
What it does: a command-line proxy that makes the output of common commands (git, npm, docker, cargo) shorter before the agent reads it. It works for all CLIs, through your shell. The install runs the RTK install script and rtk init -g. On Windows, Splitkick downloads the release and adds it to your user PATH. There is no uninstall button.
Why change it: install it to save tokens: RTK says 60 to 90 % on common commands.
Cost: the agent sees filtered output, not the full output. The install runs a script from the internet.
Caveman
What it does: a skill for Claude, Codex, OpenCode, Cursor, PI, Command Code and Grok that makes the agents answer in very short sentences. In Claude and OpenCode it can turn on by itself. In other CLIs, type /caveman in a session.
Why change it: install it to save output tokens (Caveman says 65 to 75 %), when you do not need full sentences.
Cost: answers are terse and harder to read.
Superpowers
What it does: a skill pack for the same CLIs, with workflows for brainstorming, test-driven development, debugging, code review and plans. For Claude it is installed as a plugin in the active Claude account. Splitkick removes the Superpowers skill for git worktrees, because Splitkick manages the worktrees.
Why change it: install it when you want these fixed workflows, for example /superpowers:brainstorm.
Cost: the skills add prompt text when they are used, and workflows such as test-driven development take more turns.
Kimi Code gets neither Caveman nor Superpowers.