Company · External room agents

Your own Claude Code, working in the room

Pair your computer and the agentic room sends its work to the coding agent you already use. Claude Code runs in a folder you choose, every step shows live in the room, and it asks before it edits or runs anything.

My Claude Code · Web app · Sprint 42

Online
Fix the checkout limit bug from QA-214 and add a test.
Personalweb-appNew sessionMode · Auto
Read src/checkout/limits.ts
Ran npm test -- limits
Edit src/checkout/limits.ts
src/checkout/limits.ts+3−1
41 const total = items.reduce(sum, 0);
42− if (total > limit) throw new Error();
42+ if (total > limit) {
43+ return { ok: false, reason: 'over_limit' };
44+ }
45 return { ok: true, total };
Claude Code wants to edit this fileDeny
Runs with your own Claude Code on Maya’s MacBook, in web-app. Only you see these runs.

The task

QA-214 · Checkout throws over the limit

Assigned to My Claude Code

In progress

Claude Code leaves a note and a review status — never Completed.

Type “/”

/reviewYour Claude Code command
/open-tasksQik · your open tasks here
/attachQik · attach room items
/folderQik · change the folder
Your personal agent

The room gives the work, your computer does it

Type a command in the room or hand Claude Code one of your tasks. It runs on your computer, with your code, under your own Claude plan.

  1. 01

    A folder per room

    Choose the project folder each room works in, from suggestions worked out on your computer. Only the folder name is stored in Qik.

  2. 02

    Allow / Deny, in the room

    Claude Code’s own “may I edit or run this?” questions arrive as cards showing the proposed change as a diff. Your answer lands on the run.

  3. 03

    Only you see your runs

    External room agents are personal: only you send them work and only you see the run. The rest of the room sees what changed.

Capabilities

Everything the terminal gives you, in the room

The run card reads like a Claude Code session, with the room’s tasks, people and AI project manager around it.

Code changes as diffs

Every edit and new file shows with line numbers, green added and red removed. The diffs are read from your computer; Qik stores no code.

Sessions you can pick up

Replies continue the same session. Pick an earlier one, continue a terminal session as a copy, or copy the claude --resume command.

A “/” menu

Your own Claude Code commands, skills and plugins, plus Qik actions such as /new, /attach, /open-tasks and /folder, and Qik’s agent skills.

Hand it a task

Assign one of your tasks to My Claude Code. It updates the task with a note and a review status — never Completed.

Helpers in view

When Claude Code starts helper agents, the run shows “N agents working”, each with its status, steps so far and latest step.

Runs side by side

Several commands can run in one folder at once, like two terminals, with up to eight runs per computer.

Set up in a minute

Pair, choose a folder, give a command

One bridge on your computer connects it to Qik Office. Connected apps lists your rooms under each agent, each with its own switch.

  • ① Connect your computer

    Run npx qik-claude connect and enter the code in Settings › Connected apps › External room agents — or click Connect this computer in the desktop app.

  • ② Turn it on in a room

    In the room’s Agent menu, choose your personal agent, My Claude Code, and pick the folder it works in.

  • ③ Work from anywhere

    Command it from the room, or let Claude Code in your terminal claim a task with the Qik plugin and report progress back to the room.

  • Company control

    Company admins switch External room agents on or off for the whole office. Off takes it out of every room at once; folders are kept.

Connected apps › External room agents

Web app · Sprint 42web-app
Payments APIpayments-api
Mobile releasemobile

Computers

Maya’s MacBookonline
npx qik-claude connect
Codex CLI · soonGemini CLI · soonOpenCode · soonCursor CLI · soonCopilot CLI · soon

One bridge serves every agent on the computer.

Flow through the room

From a task to reviewed code

The room keeps the context; your computer keeps the code.

In practice

Who runs on External room agents

Engineering teams

The sprint room drives the code

Tasks agreed in the sprint meeting go straight to Claude Code in the repository, and each comes back as a change ready for review.

Solo builders

One place for the plan and the code

Keep the roadmap, meetings and AI minutes in the room, and have Claude Code work through the list in your project folder.

Tech leads

See what changed, not every keystroke

Runs stay private to the person who started them, while the room sees the tasks move and the notes Claude Code leaves.

Across the product

One company, one office, one shared state

Questions

External room agents, answered

Claude Code today. Codex CLI, Gemini CLI, OpenCode, Cursor CLI and Copilot CLI are listed in Connected apps and are on their way; one bridge on your computer serves them all.

No. Claude Code runs on your computer, in your folder. Code changes travel from your computer to your own app; finished runs read their diffs back from the session on your computer. Qik stores only the folder name and step counts.

External room agents come with AI Office Pro, Custom and Enterprise. Each run uses 2 agent credits for Qik’s coordination — relaying the command, following it live, approval cards and the room tools. Claude’s own usage is billed by your Claude plan, never by Qik.

Only you. It is your personal agent: only you can send it work and see its runs. Others in the room see what changed — the tasks it updated and the notes it left.

Yes. Every run ends with its session id and a copyable claude --resume command. In the room you can also pick up sessions started in the terminal, or continue one that is still open as a copy.

External room agents

Deploy AI project managers across your office

Unlimited agentic rooms and AI project managers on every plan. Start free, or walk through your office with us.