claude-workspace

Showing 25 of 26 from the live probe.

• Save Context

  Writes a real, persistent record to the shared workspace database — not a note to yourself, a record any other AI model or agent (even one that has never seen this conversation) can read back via get_context or resources/read. This is how cross-session and cross-agent memory actually works here; without calling this, nothing about what you did survives past this conversation. CRITICAL FORMAT RULES for the summary field — write in plain language like this: 'The user asked me to [exact request]. I

• Get Context

  Retrieves the full context of a workspace. Call this at the start of a new chat to instantly know everything that was done before without re-explaining anything.

• Register Agent

  Writes your presence into a real shared registry for this workspace — a persistent record, not just something you say in chat. Once written, any other agent (different platform, different machine) calling list_agents or reading resources will genuinely see you listed, in real time. Call this once at the start of working in a multi-agent workspace; you don't strictly need it for solo/single-instance use, since other tools below (save_checkpoint, remember_preference) work without it.

• List Agents

  Lists all Claude instances currently active on a workspace. Use this before starting a task to check if another agent is already working on it.

• Claim Task

  Claims a task so other agents know not to touch it. Use a clear human-readable task_id like 'build-login-page' or 'write-api-docs'. The description must explain in plain English what you will do and the expected result.

• Release Task

  Releases a task you previously claimed, so other agents can work on it. Agents currently in listen_workspace will be notified immediately that this task is free.

• List Tasks

  Lists all currently claimed tasks in a workspace and who owns them.

• Set Workspace Vision

  Writes the global vision/objective of the workspace to the shared database — a real, persistent field, not a summary you keep in your own head. All agents will see this vision in every get_context call, including agents that join later and have no other context. Use this to define what the project is trying to achieve at a high level. When updated, all listening agents are notified immediately via listen_workspace.

• Wait For Event

  Blocks and waits until another agent triggers a specific named event. Low-level primitive — in most cases prefer listen_workspace instead, which watches everything (claims, releases, context, broadcasts, reviews) and auto-chains across multiple rounds for you. Use wait_for_event only when you need to wait for one precise event name and nothing else. Max wait is 25 seconds. If timeout, call again to keep waiting.

• Broadcast Message

  Sends a message visible to ALL agents in the workspace. Use this to announce progress, ask a question to everyone, or share important info. Right after broadcasting, if you expect a reply, call listen_workspace to wait for it instead of stopping or guessing — other agents will see your message and may reply via broadcast_message themselves.

• Request Review

  Asks a specific agent to review your work before you continue. The target agent will see a pending review when they call list_agents or get_history. Use approve_review or reject_review to respond.

• Respond Review

  Approves or rejects a review request from another agent. The requesting agent will receive the feedback when they call wait_for_event or get_history.

• Get History

  Returns the full action history of a workspace — who did what and when. Includes saves, claims, releases, broadcasts, reviews. Useful for onboarding a new agent.

• Listen Workspace

  Watches the workspace for real-time changes from other agents — task claims, releases, context updates, broadcasts, reviews. Returns instantly when something happens, or gives a full workspace snapshot after 23s. Automatically chains up to 10 rounds (~230s total). IMPORTANT: if the response ends with 'Calling listen_workspace again (round N/10)...', you MUST immediately call listen_workspace again with round=N to keep watching.

• Use Workflow Template

  Applies a predefined team workflow to a workspace. Sets up the agent roles and task list automatically. Available templates: landing-page, content-team, bug-fix, travel-planning.

• Push File

  Writes the file's content to a real shared store other agents can actually read from — this is a genuine data transfer, not a status update. CRITICAL: agents on different machines, IDEs, or platforms (Claude Code on one laptop, Codex on another) NEVER see each other's local disk. If you create or edit a file that another agent in this workspace might need, you MUST call push_file right after writing it — saying 'I created the file' is not enough, nothing is shared until you push it. Keep it to o

• List Files

  Lists every file other agents have shared in this workspace (path, size, who pushed it, when). Call this at the start of a session alongside resources/list — do NOT assume a project is empty just because you don't see files on your own disk; another agent may have already pushed work here.

• Pull File

  Retrieves the content of a file another agent pushed to this workspace. Call this whenever a broadcast, history entry, or workspace context mentions a file you don't have locally — never assume you already have it just because another agent said they made it. You must then write the returned content to disk yourself; this tool only relays data, it does not touch any filesystem.

• Delete File

  Removes a file from the shared workspace once it's no longer needed by other agents.

• Save Checkpoint

  Writes a real, durable snapshot to an external database tied to this user's account — it persists across this conversation ending, across new sessions, and across switching to a different AI platform entirely, because it lives in the user's own database, not in your context window. This is NOT limited by your own lack of memory between conversations — calling this tool is precisely how content survives when your own memory wouldn't. Do not tell the user you have 'no way' to keep a version for th

• List Checkpoints

  Lists saved checkpoints so you can find the one the user is referring to when they say 'go back to the version where...' or 'remember when we had...'. Call this before recall_checkpoint.

• Recall Checkpoint

  Retrieves the full content and note of a specific checkpoint by id. You must then re-apply that content yourself (e.g. rewrite the file) — this tool only returns the saved data, it cannot directly modify files on the user's machine.

• Delete Checkpoint

  Deletes a saved checkpoint the user no longer needs.

• Remember Preference

  Writes a durable preference to the user's own database record — it will genuinely be there next session, independent of your own memory, even in a brand new conversation with no prior context. Use for lasting taste/style/workflow preferences, not one-off content (use save_checkpoint for that). Ex: key='styling', value='Always Tailwind, dark theme, no emojis in copy'. Call this whenever the user states a preference that should apply going forward, not just this session — don't wait for them to ex

• List Preferences

  Lists all remembered preferences for this user. Call this at the start of a session if resources/list did not already surface them, so you work the way the user expects without asking again.