// Manage Agent Filesystem through the control-plane MCP server. Use when the `agent-filesystem` MCP server is available, or when the user asks Codex to list, create, fork, checkpoint, delete, or connect AFS workspaces using a control-plane token.
| name | agent-filesystem |
| description | Manage Agent Filesystem through the control-plane MCP server. Use when the `agent-filesystem` MCP server is available, or when the user asks Codex to list, create, fork, checkpoint, delete, or connect AFS workspaces using a control-plane token. |
This plugin connects Codex to AFS as the agent-filesystem MCP server. It uses
a control-plane token, so the server exposes workspace management and
token-management tools rather than file tools for one specific workspace.
agent-filesystem MCP tools for workspace management instead of
shelling out to afs or editing local config by hand.Self-managed in user-facing copy for a user-run control plane.Use these tools when the agent-filesystem MCP server is connected with a
control-plane token:
workspace_list: list visible workspaces.workspace_get: inspect a specific workspace.workspace_create: create a workspace, optionally from a template.workspace_fork: fork a workspace into a new workspace.workspace_delete: delete a workspace and its data. Confirm first.checkpoint_list: list checkpoints for a workspace.checkpoint_create: create a checkpoint from live workspace state.checkpoint_restore: restore live workspace state from a checkpoint. Confirm first.mcp_token_issue: mint a workspace-scoped MCP token for a specific workspace.mcp_token_revoke: revoke a control-plane or workspace MCP token by id.Call workspace_list, then summarize the workspace names, databases, template
slugs, and anything that looks like a likely current target.
Ask for a name only if the user has not given one. Prefer lowercase,
hyphen-delimited workspace names. If a template is relevant, pass
template_slug; otherwise create an empty workspace.
mcp_token_issue with the workspace name and a clear token label.workspace-rw for normal file editing, workspace-ro for inspection,
and workspace-rw-checkpoint when the agent should manage checkpoints.url returned by mcp_token_issue; it will match the cloud or
local/Self-managed control plane the agent is connected to.For Codex, prefer an environment-backed token:
[mcp_servers.afs-workspace-name]
url = "<url-returned-by-mcp_token_issue>"
bearer_token_env_var = "AFS_WORKSPACE_TOKEN"
Call checkpoint_create before risky changes or when the user explicitly asks
for a restore point. Use a short, meaningful checkpoint name when one is given;
otherwise let the server generate one.
The plugin's MCP endpoint is configured in the plugin root .mcp.json.
Use the cloud endpoint for AFS Cloud:
"url": "https://agent-filesystem.vercel.app/mcp"
Use localhost for a local or Self-managed control plane:
"url": "http://127.0.0.1:8091/mcp"
Use when agents need persistent shared storage, when saving or restoring workspace state, or when coordinating file access across multiple agents and machines. Creates Redis-backed workspaces, checkpoints and restores agent state, mounts shared filesystems locally, searches workspace contents, and forks workspaces for parallel work.
Persistent Redis-backed workspaces for agents. Use via `afs mcp`, the `afs` CLI, sync mode, live mounts, and explicit checkpoints.
Use when the user wants to migrate Codex state in ~/.codex into Agent Filesystem and mount the same shared Codex memory/settings across multiple computers. Recommends a .afsignore before migration and defaults to excluding worktrees, caches, logs, and temporary files.
"Use before writing, modifying, or reviewing code when the {{serverName}} MCP server is connected. Read the relevant standards files live from standards/, cite the specific path you used, and treat the workspace as read-only."
"Use when Codex has access to the {{serverName}} AFS shared-memory MCP server, or when the user asks to check shared memory, prior cross-agent context, durable learnings, memory entries, workspace memory, saved commands, acronyms, aliases, shorthand such as CPP/CCP, /memory-search, or /memory-record. Before any non-trivial answer in a connected project, fresh-search /shared-memory for the task's key nouns, read relevant entries, and build on them instead of re-deriving. After discovering a durable reusable fact, write a new dated memory entry and append a pointer to /shared-memory/index.md. Skip trivial, purely conversational, or session-only tasks."
"Use when answering non-trivial questions in a project connected to the {{serverName}} MCP server (tools prefixed {{toolPrefix}}*). Read wiki/index.md first, search wiki/ for key nouns, cite relevant wiki paths, and offer to file durable answers back into the Shared LLM Wiki (Karpathy style). When ingesting sources from raw/, update source/topic/entity pages plus wiki/index.md and append to wiki/log.md."