Agent Studio

Create, manage, and orchestrate AI agents inside Visual Studio Code with a visual, developer-friendly control plane.

Hero / Tagline

🚀 Build multi-agent workflows without getting lost in config files.
Agent Studio gives you a visual dashboard to design agents, inspect relationships, and understand tools, skills, and MCP servers at a glance.

CTA: Install Agent Studio and run your agent ecosystem directly where you code.

Features

🧠 Visual Agent Dashboard

• Manage agents from a dedicated VS Code sidebar and dashboard.
• Edit agent definitions with a clearer, structured workflow.
• Keep agent context close to your codebase.

🔗 Agent Relationships

• Visualize how agents connect and hand off work.
• Understand flow and dependencies faster in multi-agent setups.
• Reduce onboarding time for new teammates.

⚡ Tools, Skills, and MCP Visibility

• Inspect which tools, skills, and MCP servers each agent uses.
• Spot capability gaps and overlap quickly.
• Navigate from high-level architecture to implementation details.

🛠 Better DX Than Raw Config Files

• Move from scattered files to a guided in-editor experience.
• Discover, edit, and organize agents with less friction.
• Keep workflows readable as your system grows.

📍 Native VS Code Experience

• Works directly in your editor, alongside your project.
• Open agents in chat and move from design to execution quickly.
• No context switching to external dashboards.

🤖 Multi-AI Agent Generation

• Generate the same agent for Claude Code, OpenAI Codex (via AGENTS.md), or Google Antigravity from a single definition.
• Pick ✨ All AIs to produce every provider's file in one step.
• Export (or re-export) any existing agent later from its context menu — see Creating Agents.

📦 Bulk Export, Repo Scaffolding, and Import

• Export All Agents: write every loaded agent as a .agent.md file into any folder you choose.
• Create Repo Structure: scaffold a fresh .github/agents/ folder (plus a short README.md) with all your agents, ready to become its own repo.
• Import Agents: pick a folder of previously exported .agent.md files and bring in the ones you don't already have.
• All three live in the Choose view's Export / Import section, with bilingual (English/Spanish) labels and hints.

Screenshots

Choose what to work on — agents, workflows, and the Export / Import section, all in one screen.

Agent Builder, Identity tab — Agent ID, Scope, Name, and Role in a single grid.

Capabilities tab — toggle Tools/Skills/MCP servers, or add a new one on the fly.

Agent graph — handoff relationships between agents, with the selected agent's connections highlighted.

Workflow graph — steps, entry point, run status, and inline controls to add steps or run the workflow.

Inspect view — an agent's capability layer, handoffs in/out, and the workflows it's used in.

Capability filters — narrow the agent list by tool, skill, MCP server, or scope.

Why Agent Studio?

If you are building with multiple AI agents, complexity grows fast. Agent Studio helps you stay in control.

• Clear visual model of your agent ecosystem.
• Faster debugging of orchestration issues.
• Better collaboration across teams.
• Reduced cognitive load versus manual configuration.

Installation

From VS Code Marketplace (recommended)

1. Open Extensions in VS Code.
2. Search for Agent Studio.
3. Select the extension and click Install.

Manual install (VSIX)

1. Download the latest .vsix package from your release channel.
2. In VS Code, open the Command Palette.
3. Run Extensions: Install from VSIX... and select the file.

Basic Usage

Quick Getting Started

1. Open the Agent Studio icon in the Activity Bar.
2. Run Agent Studio: Open Dashboard.
3. Create your first agent with Agent Studio: Create Agent and choose whether it should be Repository or Global.
4. Add or inspect capabilities (tools, skills, MCP servers).
5. Create a workflow and connect agent steps visually.
6. Open an agent in chat and execute your flow.

Typical first workflow

1. Create an agent for planning.
2. Create an agent for implementation.
3. Connect them in a workflow.
4. Validate capabilities from the dashboard inspector.
5. Launch from chat and iterate.

Available Commands

• Agent Studio: Open Dashboard
• Agent Studio: Quick Find Agent
• Agent Studio: Quick Find Workflow
• Agent Studio: Quick Find Capability
• Agent Studio: Create Agent
• Agent Studio: Edit Agent
• Agent Studio: Delete Agent
• Agent Studio: Duplicate Agent
• Agent Studio: Export Agent for Claude, Codex or Antigravity
• Agent Studio: Open Agent In Chat
• Agent Studio: Create Workflow
• Agent Studio: Start MCP Server
• Agent Studio: Focus Capability In Dashboard
• Agent Studio: Focus Workflow In Dashboard
• Agent Studio: Refresh Studio
• Agent Studio: Show Tools Guide

Configuration

Agent Studio supports workspace configuration for agent discovery paths.

• agentStudio.agentPaths: Additional workspace-relative directories to discover .agent.md files.
• agentStudio.includeClaudeAgents: When true (default), also discovers globally installed Claude Code subagents from ~/.claude/agents/*.md and lists them as global agents.

Agent scopes

Agent Studio supports two storage scopes for agents:

• repository: stored in the current repo, under .github/agents
• global: stored in the current user's home directory, either under ~/.agents/agents (Agent Studio's own format) or ~/.claude/agents (Claude Code subagents, read-only frontmatter shape — tools may be a comma-separated string instead of an array)

When Agent Studio loads agents, it merges:

• repository agents from the open workspace
• global agents from ~/.agents/agents
• global Claude Code subagents from ~/.claude/agents (unless agentStudio.includeClaudeAgents is set to false)

The dashboard's agent picker and search results show a Repo/Global badge next to each agent so you can tell scopes apart at a glance, and you can filter the agent list by scope from the Capability Filters panel.

If two agent files resolve to the same agent id, the later one in the merge order above wins (repository beats global, and ~/.claude/agents beats ~/.agents/agents). The shadowed agent is dropped from the list, and Agent Studio surfaces a warning in the Inspector panel, the sidebar tree tooltip, and the developer console so the conflict isn't silent.

You can choose the scope:

• when creating a new agent from the command palette
• from the Scope field in the Agent Builder Identity tab

Editing and saving works the same way for both scopes — saving writes back to the folder matching the agent's Scope field (and migrates the file there if it was loaded from elsewhere, e.g. from ~/.claude/agents).

Default:

{
  "agentStudio.agentPaths": [".github/agents"],
  "agentStudio.includeClaudeAgents": true
}

Sample data seeding

By default, Agent Studio does not create any files automatically.

If you want starter sample agents and a sample workflow in an empty workspace, enable the agentStudio.seedSampleData setting:

{
  "agentStudio.seedSampleData": true
}

Donations

Hey there, fellow adventurer! 🐾

If you'd like to support Agent Studio, you can make a small contribution at https://buymeacoffee.com/eric92rodrm.

Your donations help keep the project alive — covering hosting, infrastructure and maintenance so the dashboard and related services stay online and responsive. Any remaining funds will be used to provide food, supplies, and shelter for animals in need.

Thank you for your generosity—you're making a difference both for this project and for real-life companions. Together we protect our pets, digital and furry alike! 💖

Roadmap

Planned improvements include:

• More advanced workflow orchestration controls.
• Richer validation and diagnostics for agent setups.
• Expanded templates for common agent architectures.
• Enhanced observability for multi-agent execution.

Contributing

Contributions are welcome. For contribution guidelines, issue reporting, and collaboration flow, check the project documentation and open a pull request.

License

MIT License. See LICENSE for details.

Frontmatter & Agent File Format (developer notes)

Agent Studio uses a structured frontmatter in .agent.md files to declare capabilities and handoffs. Recent updates changed a few rules — update your .agent.md files accordingly.

• tools: now serialized as an array of tool IDs (strings). Example:

tools:
  - run_in_terminal
  - apply_patch

• mcp: an array of MCP server objects or ids. MCP objects may include an optional autoRunMCP boolean. Example:

mcp:
  - id: chrome-devtools-mcp
    command: npx
    args:
      ["chrome-devtools-mcp@0.21.0", "--browserUrl", "http://127.0.0.1:9222"]
    autoRunMCP: true

• handoffs: migrated from an array of agent-id strings to objects with agent, optional label, optional prompt, and optional send boolean. Strings are still accepted and will be migrated on save. Example:

handoffs:
  - agent: reviewer
    label: Reviewer
    prompt: "Please review the changes and focus on tests"
    send: true

Validation: Agent Studio will log/notify when it discovers older formats and offer migration guidance.