Account → workspace → agent → first Kage

Get your agent building Kages

Kages is driven by your AI agent — Claude Code, Codex, Cursor, and anything else that speaks MCP. Sign in, verify the destination, and give your agent the authoring guidance it needs.

Checking this browser’s workspace…

This checks the browser only. Verify the agent separately with get_setup after connecting MCP.

0/6 reviewed

Sign in to Kages with the account you want your agent to use. Your personal workspace is created automatically; a project is a folder inside it.

Browser sign-in and agent sign-in are separate. You do not need to run kages init to create a cloud workspace.

Install on the machine running your agent. Authoring skills are installed separately in the next steps.

npm install -g https://app.getkages.com/downloads/ifocksh-kages-0.2.0.tgz

Node 18 or newer. Verify with kages --version.

Run this in your own terminal and complete the browser sign-in. The session stays on this machine and lets the agent reach your cloud workspace.

kages auth login --url https://app.getkages.com

For SSH or a remote agent, forward localhost port 52525 to the machine running the command. Never paste tokens or passwords into chat.

This authenticated call provisions the workspace if needed and reports its identity. Check ready:true, mode:cloud and the intended workspace before creating anything.

kages remote get_setup

A missing workspace brief does not block creation. Tell the agent your audience, purpose and constraints; it can save confirmed context with set_brief.

Choose the registration command for your agent, then reconnect its MCP server. The stdio connection uses the terminal session and refreshes access automatically.

claude mcp add kages -- kages mcp
# Or, for Codex:
codex mcp add kages -- kages mcp

For file-based skill discovery, also run kages install. MCP provides get_authoring_guide as a tool even when the client cannot load prompts or resources. An existing hosted HTTP connection needs its own Bearer credential; terminal login does not authenticate that connection.

Paste this into your agent. Its get_setup result must name the same cloud workspace before it creates the draft.

Call get_setup and verify that you are connected to my cloud workspace. If not ready, explain the setup step and stop before creating. Then call get_context with system:core, read its authoring skill and relevant references using get_authoring_guide. Create an interactive new-hire checklist in a project called onboarding. Validate it, check its preview and interactions, then publish it with link visibility and give me the URL.

Local publishing has no hosted share URL. Use kages mcp --local only when you deliberately want offline work.