Skip to main content

Glossary

Look up a Kosuke word here. Each entry gives a short definition and links to the page that explains it in full.

Workspace and people​

TermMeaning
WorkspaceHolds your projects, members, AI provider Credentials and billing. Every project belongs to one workspace. Members and roles
MemberA person who belongs to a workspace. Every member can open and send into every chat session in it. Members and roles
RoleWhat a member may do in a workspace. It is Owner, Admin or Member, and owners and admins manage members, Credentials and settings. Members and roles
CredentialsThe workspace's stored access to an AI provider, such as an API key or a Claude Code or Codex login. Admins manage them. AI providers
SubscriptionYour own Claude, Codex, GLM Coding Plan or Kimi Code access. It follows you into every workspace, and sessions you are the Assignee of run on it. AI providers
ProviderA company whose models Kosuke runs. Kosuke works with Anthropic, OpenAI, Z.ai and Moonshot AI. AI providers
GitHub ConnectionYour link to your own GitHub account. It lists the repositories you can import and puts your name on the commits and pull requests from your messages. Import a repository
Kosuke AppThe GitHub App you install on a repository so Kosuke can read and push its code. It opens pull requests for members without a GitHub Connection. Import a repository
API KeyYour own key for the Kosuke CLI, the MCP server and the API. It acts as you. Authentication
Connector TokenWhat an AI app such as Claude or ChatGPT holds once you allow it on Kosuke's consent screen. It acts as you, like an API Key, and stops working when you disconnect the app. Connect your coding agent
Connected AppAn AI app you have allowed to act as you through the Kosuke MCP server. Settings lists it next to your API Keys, and you disconnect it there. Connect your coding agent
Free CreditsThe usage a workspace gets without an invoice. On a Trial it is a one-time grant, given once per person. Plans and billing

Projects and deploys​

TermMeaning
ProjectA GitHub repository imported into a workspace, plus everything Kosuke needs to run it. Import a repository
DeployOne attempt to get the project's app running in its main sandbox. A redeploy tries the saved settings first, and the deploy agent works out or fixes how to run the app when needed. A project needs one successful deploy before sessions can start. Deploy your project
Deploy ChatThe project's conversation with the deploy agent, in the project's Settings view. Deploy your project
SandboxThe cloud machine a project or a session runs in. It costs money while awake and pauses when nobody uses it. Preview and sandboxes
PreviewYour app running in a sandbox, shown inside Kosuke and at its own web address. Preview and sandboxes
Target BranchThe branch a session's pull request targets and a Sync brings in. Unless a project sets one, it is the repository's default branch. Project settings

Chat sessions​

TermMeaning
Chat sessionOne unit of work on a project. Once started, it has its own branch, sandbox and conversation, and later a pull request. Chat sessions and the board
BoardA project's Sessions view, with one column per session status. Chat sessions and the board
BacklogA session holding only its prompt, ready to start. It has no branch or sandbox yet. Chat sessions and the board
ActiveA session whose conversation is open. Its pull request, if it has one, is a draft. Chat sessions and the board
Under ReviewA session whose pull request is ready for review. A member's message resumes it, and so does Resume. Chat sessions and the board
CompletedA session whose pull request merged, or a Backlog session completed without code work. Chat sessions and the board
ArchivedA session set aside without a merge. Its pull request is closed and its sandbox removed. Chat sessions and the board
AssigneeThe member a session is booked to. The session runs on the Assignee's Subscription when they have one. Chat sessions and the board
TurnOne exchange with the agent. It covers your message, the agent's work and its reply. Messages, Up next and steering
Up nextThe messages waiting behind the running turn. Each one starts its own turn, in order. Messages, Up next and steering
SteerSending your waiting message into your own running turn, so the agent changes course without starting a new turn. Messages, Up next and steering
ClarificationA question the agent asks before it goes on. The turn ends, and your answer starts the next one. Messages, Up next and steering
ArtifactA document, mockup, image or video the agent writes for people to read. It stays out of the repository and the pull request. Artifacts
Open PRThe button that asks the agent to open the session's pull request. Open a pull request
Ready for reviewMarks a draft pull request ready and moves the session to Under Review. Open a pull request
ResumeTurns the pull request back into a draft and moves the session back to Active. Open a pull request
SyncBrings the session's branch up to date with the Target Branch. The agent does it and resolves conflicts. Sync with the Target Branch
Needs youSessions blocked on a person, for example by failing checks or a question from the agent. Home, Needs you and Activity
ActivityThe workspace's log of what changed and who changed it, kept for 30 days. Home, Needs you and Activity

Skills and automation​

TermMeaning
SkillInstructions the agent follows when you run them, with /name in a Claude, GLM or Kimi session or $name in a Codex session. Skills
Workspace SkillA skill kept in the workspace's settings. While it is on, every chat session in the workspace has it. Skills
Factory SkillA skill Kosuke ships in its kosuke plugin, such as /kosuke:open-pr. Every session carries it. Skills
Personal SkillA skill you keep for yourself. It is loaded into every session you are the Assignee of, in every workspace. Skills
Project SkillA skill stored in the repository itself. Skills
PluginA bundle the agent installs from a marketplace. It can add skills, commands, subagents or hooks. Kosuke offers only plugins that carry no MCP server. Plugins
CronA saved prompt handed on a schedule to the Cron Agent in each of the projects it covers. Each fire makes one Cron Run per project. It runs on the workspace's Credentials. Crons
The LeadYour own agent for one workspace, marked Beta. It reads every project and session there and has no modes. It acts on sessions only when you ask. On its own it orders your cards, writes their reasons and notifications, and proposes a ticket to start. The Lead
PrototypeA page the Lead draws to show a change before it is built, with one or more variants. Yours alone until you put it on a ticket. The Lead
Lead CardA card the Lead writes in Needs you and in the Lead chat when something about a session needs you. The Lead picks its words and its buttons. Cards post one at a time, and each has Skip and Cancel. The Lead
TriagerYour Lead, when it answers what happened to your sessions. It writes, orders and closes your Lead Cards, decides whether one is worth a notification, and sends a review that asks for changes into its session. The Lead
ProposalA card for something an agent suggests and may not do itself. A cron sends one to the member it chooses: delete a shipped ticket, merge tickets, create a cron or start a ticket. The Lead proposes only a ticket to start. Accept runs it as you. The Lead
/kosuke:shipA Factory Skill that carries a ticket inside its session from grounding to a pull request marked ready. It stops only when it needs a person. The Lead
ReadyA session where /kosuke:ship stopped with ready. Its checks are green, QA passed, and the review passed or was skipped. The Lead
Merge QueueThe line approved pull requests merge through, one at a time per project. A conflict keeps the pull request's place in the line, and the Assignee's Lead sends /kosuke:sync-branch into the session. The Lead

Models​

TermMeaning
ModelThe AI a session runs. It combines a provider, a model family, a reasoning effort and, on some OpenAI models, a speed. You pick it for each session. Models
Reasoning effortHow hard the model thinks, such as Low, Medium or High. You pick it as part of the model. Models
SpeedHow fast an OpenAI model answers. Standard is the default. Fast and Ultrafast cost more. Models
FastA paid speed tier, about 1.5x to 2x faster depending on the model. Models
UltrafastThe fastest paid speed tier, for GPT 6 Astra only. It is not the Ultra reasoning effort. Models
Default ModelThe model a new session starts on when nobody picks one. Models

Next steps​