[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7826ZH7PPC4WEF3ZTP8EZFH":3,"skill-same:01M7826ZH7PPC4WEF3ZTP8EZFH":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M7826ZH7PPC4WEF3ZTP8EZFH","agent-flow-visualization",null,"VS Code extension for real-time visualization of Claude Code agent orchestration as interactive node graphs","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fskills_sh\u002Fs\u002Fskills-sh_aradotso_trending-skills_agent-flow-visualization\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: agent-flow-visualization\ndescription: VS Code extension for real-time visualization of Claude Code agent orchestration as interactive node graphs\ntriggers:\n  - visualize claude code agents\n  - debug agent tool calls\n  - see agent execution graph\n  - monitor claude code sessions\n  - agent flow vscode extension\n  - watch agents think and branch\n  - trace agent tool call chains\n  - configure claude code hooks for visualization\n---\n\n# Agent Flow\n\n> Skill by [ara.so](https:\u002F\u002Fara.so) — Daily 2026 Skills collection.\n\nAgent Flow is a VS Code extension that provides real-time visualization of Claude Code agent orchestration. It renders agent execution as an interactive node graph, showing tool calls, branching, subagent coordination, and timing — turning Claude Code's black-box execution into a transparent, debuggable flow.\n\n## Installation\n\n### Via VS Code Marketplace\n\n1. Open VS Code Extensions (`Cmd+Shift+X`)\n2. Search for **Agent Flow** by simon-p\n3. Click Install\n\nOr install directly: [marketplace.visualstudio.com\u002Fitems?itemName=simon-p.agent-flow](https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=simon-p.agent-flow)\n\n### Requirements\n\n- VS Code 1.85 or later\n- Claude Code CLI installed and accessible\n- Node.js (for Claude Code)\n\n## Quick Start\n\n```\n# 1. Open Command Palette\nCmd+Shift+P (Mac) \u002F Ctrl+Shift+P (Win\u002FLinux)\n\n# 2. Run the command\n> Agent Flow: Open Agent Flow\n\n# 3. Start a Claude Code session in your workspace\n# Agent Flow auto-detects it and begins streaming\n```\n\nOr use the keyboard shortcut:\n- **Mac**: `Cmd+Alt+A`\n- **Win\u002FLinux**: `Ctrl+Alt+A`\n\n## Commands\n\n| Command | Description |\n|---------|-------------|\n| `Agent Flow: Open Agent Flow` | Open visualizer in current editor column |\n| `Agent Flow: Open Agent Flow to Side` | Open in a side editor column |\n| `Agent Flow: Connect to Running Agent` | Manually connect to a specific agent session |\n| `Agent Flow: Configure Claude Code Hooks` | Set up Claude Code hooks for live event streaming |\n\n## Configuration\n\nSettings available in VS Code settings (`settings.json`):\n\n```jsonc\n{\n  \u002F\u002F Path to a JSONL event log file to watch\u002Freplay\n  \"agentVisualizer.eventLogPath\": \"\u002Fpath\u002Fto\u002Fagent-events.jsonl\",\n\n  \u002F\u002F Auto-open the visualizer when an agent session starts\n  \"agentVisualizer.autoOpen\": true,\n\n  \u002F\u002F Development server port (0 = production mode, use built assets)\n  \"agentVisualizer.devServerPort\": 0\n}\n```\n\n### Auto-Open on Agent Start\n\n```jsonc\n\u002F\u002F settings.json\n{\n  \"agentVisualizer.autoOpen\": true\n}\n```\n\n## Claude Code Hooks Setup\n\nAgent Flow uses Claude Code's hook system for zero-latency event streaming. Hooks are configured automatically on first open, but you can reconfigure manually.\n\n### Automatic Configuration\n\nRun from Command Palette:\n```\n> Agent Flow: Configure Claude Code Hooks\n```\n\n### Manual Hook Configuration\n\nIf you need to configure hooks manually, Agent Flow starts a local HTTP server that receives events. The hooks forward Claude Code lifecycle events (tool calls, responses, session start\u002Fend) to the extension.\n\nClaude Code hooks are configured in `~\u002F.claude\u002Fsettings.json` or project-level `.claude\u002Fsettings.json`:\n\n```jsonc\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \".*\",\n        \"hooks\": [\n          {\n            \"type\": \"command\",\n            \"command\": \"curl -s -X POST http:\u002F\u002Flocalhost:PORT\u002Fhook -H 'Content-Type: application\u002Fjson' -d @-\"\n          }\n        ]\n      }\n    ],\n    \"PostToolUse\": [\n      {\n        \"matcher\": \".*\",\n        \"hooks\": [\n          {\n            \"type\": \"command\",\n            \"command\": \"curl -s -X POST http:\u002F\u002Flocalhost:PORT\u002Fhook -H 'Content-Type: application\u002Fjson' -d @-\"\n          }\n        ]\n      }\n    ]\n  }\n}\n```\n\n> Agent Flow manages this configuration automatically — prefer using the command palette command.\n\n## JSONL Event Log Mode\n\nFor replaying past sessions or watching log files generated outside VS Code:\n\n```jsonc\n\u002F\u002F settings.json\n{\n  \"agentVisualizer.eventLogPath\": \"${workspaceFolder}\u002Flogs\u002Fagent-session.jsonl\"\n}\n```\n\nAgent Flow tails the file and visualizes events as they arrive. Use this for:\n- Post-hoc debugging of agent runs\n- Sharing agent execution recordings with teammates\n- CI\u002FCD pipeline agent monitoring\n\n### JSONL Event Format\n\nEach line in the log file is a JSON event object:\n\n```jsonl\n{\"type\":\"session_start\",\"sessionId\":\"abc123\",\"timestamp\":\"2026-03-21T10:00:00Z\",\"model\":\"claude-opus-4-5\"}\n{\"type\":\"tool_use\",\"sessionId\":\"abc123\",\"toolName\":\"bash\",\"input\":{\"command\":\"ls -la\"},\"timestamp\":\"2026-03-21T10:00:01Z\"}\n{\"type\":\"tool_result\",\"sessionId\":\"abc123\",\"toolName\":\"bash\",\"output\":\"total 48\\n...\",\"timestamp\":\"2026-03-21T10:00:02Z\"}\n{\"type\":\"message\",\"sessionId\":\"abc123\",\"role\":\"assistant\",\"content\":\"I can see the files...\",\"timestamp\":\"2026-03-21T10:00:03Z\"}\n```\n\n## Multi-Session Support\n\nAgent Flow tracks multiple concurrent Claude Code sessions with tabs. Each session gets its own visualization canvas.\n\n```\n# Start multiple Claude Code sessions in different terminals\n# Each appears as a separate tab in Agent Flow\n# Click tabs to switch between session graphs\n```\n\n## Interactive Canvas Features\n\n### Navigation\n- **Pan**: Click and drag on empty canvas\n- **Zoom**: Scroll wheel \u002F pinch gesture\n- **Select node**: Click any agent or tool call node to inspect details\n- **Reset view**: Double-click empty canvas\n\n### Node Types in the Graph\n\n| Node Type | Visual | Description |\n|-----------|--------|-------------|\n| Agent\u002FSubagent | Circle | Claude instance making decisions |\n| Tool Call | Rectangle | Individual tool invocation (bash, read_file, etc.) |\n| Tool Result | Rectangle (dashed) | Output returned from tool |\n| Branch | Diamond | Decision point spawning subagents |\n| Return | Arrow | Subagent returning result to parent |\n\n### Panels\n\n- **Timeline**: Chronological view of all events with durations\n- **Transcript**: Full message history between agent and tools\n- **File Heatmap**: Which files received the most attention\n\n## Contributing \u002F Development Setup\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fpatoles\u002Fagent-flow\ncd agent-flow\nnpm install\n\n# Build the extension\nnpm run build\n\n# Watch mode for development\nnpm run watch\n\n# Run with dev server (hot reload)\n# Set in settings: \"agentVisualizer.devServerPort\": 3000\nnpm run dev\n```\n\n### Extension Structure\n\n```\nagent-flow\u002F\n├── src\u002F\n│   ├── extension.ts          # VS Code extension entry point\n│   ├── hookServer.ts         # HTTP server receiving Claude Code hook events\n│   ├── sessionManager.ts     # Manages multiple agent sessions\n│   ├── webviewProvider.ts    # Webview panel management\n│   └── logWatcher.ts         # JSONL file tail watcher\n├── webview\u002F\n│   ├── src\u002F\n│   │   ├── App.tsx           # Main React app\n│   │   ├── Graph.tsx         # Node graph canvas (likely D3 or React Flow)\n│   │   ├── Timeline.tsx      # Timeline panel\n│   │   └── Transcript.tsx    # Message transcript panel\n│   └── package.json\n└── package.json              # Extension manifest\n```\n\n## Common Patterns\n\n### Pattern: Debug a Failing Agent Run\n\n1. Open Agent Flow (`Cmd+Alt+A`)\n2. Run your Claude Code command that's failing\n3. Watch the graph — look for:\n   - Red\u002Ferror nodes indicating failed tool calls\n   - Unexpected branching\n   - Loops (agent retrying the same tool)\n4. Click the failed tool node to inspect input\u002Foutput\n5. Check the Timeline panel for which tool call took unexpectedly long\n\n### Pattern: Replay a Saved Session\n\n```bash\n# Save Claude Code output to JSONL during a run\n# (depends on your Claude Code version\u002Fconfig)\nclaude --output-format jsonl > session-$(date +%s).jsonl\n\n# Point Agent Flow at it\n```\n\n```jsonc\n\u002F\u002F .vscode\u002Fsettings.json (project-level)\n{\n  \"agentVisualizer.eventLogPath\": \".\u002Flogs\u002Fsession-1234567890.jsonl\"\n}\n```\n\n### Pattern: Auto-Visualize All Agent Sessions\n\n```jsonc\n\u002F\u002F settings.json\n{\n  \"agentVisualizer.autoOpen\": true\n}\n```\n\nNow every time a Claude Code session starts in your workspace, Agent Flow opens automatically.\n\n### Pattern: Side-by-Side Coding and Visualization\n\n```\n# Open Agent Flow to side so you can code and watch simultaneously\nCmd+Shift+P > Agent Flow: Open Agent Flow to Side\n```\n\nThis opens the visualizer in a split editor, keeping your code files accessible in the main editor group.\n\n## Troubleshooting\n\n### Agent Flow doesn't detect my Claude Code session\n\n1. Verify Claude Code is running in the same workspace folder\n2. Check that hooks are configured: run `Agent Flow: Configure Claude Code Hooks`\n3. Verify the hook server is running — look for \"Agent Flow hook server listening\" in the Output panel (`View > Output > Agent Flow`)\n4. Try `Agent Flow: Connect to Running Agent` to manually specify the session\n\n### Hooks aren't forwarding events\n\n```bash\n# Test the hook server manually\ncurl -X POST http:\u002F\u002Flocalhost:PORT\u002Fhook \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d '{\"type\":\"test\",\"sessionId\":\"test123\"}'\n```\n\nCheck VS Code Output panel for the correct PORT value.\n\n### Graph is empty \u002F not updating\n\n1. Check `agentVisualizer.eventLogPath` — if set, Agent Flow reads from file instead of hooks\n2. Clear the setting if you want live hook-based streaming:\n   ```jsonc\n   { \"agentVisualizer.eventLogPath\": \"\" }\n   ```\n3. Reload VS Code window (`Cmd+Shift+P > Developer: Reload Window`)\n\n### Extension not loading\n\n```bash\n# Check VS Code version meets requirement\ncode --version\n# Must be 1.85 or later\n\n# Check extension is enabled\n# Extensions panel > search \"Agent Flow\" > verify enabled\n```\n\n### Multiple sessions showing in wrong tabs\n\nEach session is identified by a unique session ID from Claude Code. If sessions are merging incorrectly, check that each `claude` process is started fresh (not reusing an existing session ID).\n\n## Resources\n\n- [VS Code Marketplace](https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=simon-p.agent-flow)\n- [Demo Video](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=Ud6eDrFN-TA)\n- [GitHub Repository](https:\u002F\u002Fgithub.com\u002Fpatoles\u002Fagent-flow)\n- [CraftMyGame](https:\u002F\u002Fcraftmygame.com) — the project that inspired Agent Flow\n- [License: Apache 2.0](https:\u002F\u002Fgithub.com\u002Fpatoles\u002Fagent-flow\u002Fblob\u002Fmain\u002FLICENSE)\n","# Agent Flow\n\n> Skill by [ara.so](https:\u002F\u002Fara.so) — Daily 2026 Skills collection.\n\nAgent Flow is a VS Code extension that provides real-time visualization of Claude Code agent orchestration. It renders agent execution as an interactive node graph, showing tool calls, branching, subagent coordination, and timing — turning Claude Code's black-box execution into a transparent, debuggable flow.\n\n## Installation\n\n### Via VS Code Marketplace\n\n1. Open VS Code Extensions (`Cmd+Shift+X`)\n2. Search for **Agent Flow** by simon-p\n3. Click Install\n\nOr install directly: [marketplace.visualstudio.com\u002Fitems?itemName=simon-p.agent-flow](https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=simon-p.agent-flow)\n\n### Requirements\n\n- VS Code 1.85 or later\n- Claude Code CLI installed and accessible\n- Node.js (for Claude Code)\n\n## Quick Start\n\n```\n# 1. Open Command Palette\nCmd+Shift+P (Mac) \u002F Ctrl+Shift+P (Win\u002FLinux)\n\n# 2. Run the command\n> Agent Flow: Open Agent Flow\n\n# 3. Start a Claude Code session in your workspace\n# Agent Flow auto-detects it and begins streaming\n```\n\nOr use the keyboard shortcut:\n- **Mac**: `Cmd+Alt+A`\n- **Win\u002FLinux**: `Ctrl+Alt+A`\n\n## Commands\n\n| Command | Description |\n|---------|-------------|\n| `Agent Flow: Open Agent Flow` | Open visualizer in current editor column |\n| `Agent Flow: Open Agent Flow to Side` | Open in a side editor column |\n| `Agent Flow: Connect to Running Agent` | Manually connect to a specific agent session |\n| `Agent Flow: Configure Claude Code Hooks` | Set up Claude Code hooks for live event streaming |\n\n## Configuration\n\nSettings available in VS Code settings (`settings.json`):\n\n```jsonc\n{\n  \u002F\u002F Path to a JSONL event log file to watch\u002Freplay\n  \"agentVisualizer.eventLogPath\": \"\u002Fpath\u002Fto\u002Fagent-events.jsonl\",\n\n  \u002F\u002F Auto-open the visualizer when an agent session starts\n  \"agentVisualizer.autoOpen\": true,\n\n  \u002F\u002F Development server port (0 = production mode, use built assets)\n  \"agentVisualizer.devServerPort\": 0\n}\n```\n\n### Auto-Open on Agent Start\n\n```jsonc\n\u002F\u002F settings.json\n{\n  \"agentVisualizer.autoOpen\": true\n}\n```\n\n## Claude Code Hooks Setup\n\nAgent Flow uses Claude Code's hook system for zero-latency event streaming. Hooks are configured automatically on first open, but you can reconfigure manually.\n\n### Automatic Configuration\n\nRun from Command Palette:\n```\n> Agent Flow: Configure Claude Code Hooks\n```\n\n### Manual Hook Configuration\n\nIf you need to configure hooks manually, Agent Flow starts a local HTTP server that receives events. The hooks forward Claude Code lifecycle events (tool calls, responses, session start\u002Fend) to the extension.\n\nClaude Code hooks are configured in `~\u002F.claude\u002Fsettings.json` or project-level `.claude\u002Fsettings.json`:\n\n```jsonc\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \".*\",\n        \"hooks\": [\n          {\n            \"type\": \"command\",\n            \"command\": \"curl -s -X POST http:\u002F\u002Flocalhost:PORT\u002Fhook -H 'Content-Type: application\u002Fjson' -d @-\"\n          }\n        ]\n      }\n    ],\n    \"PostToolUse\": [\n      {\n        \"matcher\": \".*\",\n        \"hooks\": [\n          {\n            \"type\": \"command\",\n            \"command\": \"curl -s -X POST http:\u002F\u002Flocalhost:PORT\u002Fhook -H 'Content-Type: application\u002Fjson' -d @-\"\n          }\n        ]\n      }\n    ]\n  }\n}\n```\n\n> Agent Flow manages this configuration automatically — prefer using the command palette command.\n\n## JSONL Event Log Mode\n\nFor replaying past sessions or watching log files generated outside VS Code:\n\n```jsonc\n\u002F\u002F settings.json\n{\n  \"agentVisualizer.eventLogPath\": \"${workspaceFolder}\u002Flogs\u002Fagent-session.jsonl\"\n}\n```\n\nAgent Flow tails the file and visualizes events as they arrive. Use this for:\n- Post-hoc debugging of agent runs\n- Sharing agent execution recordings with teammates\n- CI\u002FCD pipeline agent monitoring\n\n### JSONL Event Format\n\nEach line in the log file is a JSON event object:\n\n```jsonl\n{\"type\":\"session_start\",\"sessionId\":\"abc123\",\"timestamp\":\"2026-03-21T10:00:00Z\",\"model\":\"claude-opus-4-5\"}\n{\"type\":\"tool_use\",\"sessionId\":\"abc123\",\"toolName\":\"bash\",\"input\":{\"command\":\"ls -la\"},\"timestamp\":\"2026-03-21T10:00:01Z\"}\n{\"type\":\"tool_result\",\"sessionId\":\"abc123\",\"toolName\":\"bash\",\"output\":\"total 48\\n...\",\"timestamp\":\"2026-03-21T10:00:02Z\"}\n{\"type\":\"message\",\"sessionId\":\"abc123\",\"role\":\"assistant\",\"content\":\"I can see the files...\",\"timestamp\":\"2026-03-21T10:00:03Z\"}\n```\n\n## Multi-Session Support\n\nAgent Flow tracks multiple concurrent Claude Code sessions with tabs. Each session gets its own visualization canvas.\n\n```\n# Start multiple Claude Code sessions in different terminals\n# Each appears as a separate tab in Agent Flow\n# Click tabs to switch between session graphs\n```\n\n## Interactive Canvas Features\n\n### Navigation\n- **Pan**: Click and drag on empty canvas\n- **Zoom**: Scroll wheel \u002F pinch gesture\n- **Select node**: Click any agent or tool call node to inspect details\n- **Reset view**: Double-click empty canvas\n\n### Node Types in the Graph\n\n| Node Type | Visual | Description |\n|-----------|--------|-------------|\n| Agent\u002FSubagent | Circle | Claude instance making decisions |\n| Tool Call | Rectangle | Individual tool invocation (bash, read_file, etc.) |\n| Tool Result | Rectangle (dashed) | Output returned from tool |\n| Branch | Diamond | Decision point spawning subagents |\n| Return | Arrow | Subagent returning result to parent |\n\n### Panels\n\n- **Timeline**: Chronological view of all events with durations\n- **Transcript**: Full message history between agent and tools\n- **File Heatmap**: Which files received the most attention\n\n## Contributing \u002F Development Setup\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fpatoles\u002Fagent-flow\ncd agent-flow\nnpm install\n\n# Build the extension\nnpm run build\n\n# Watch mode for development\nnpm run watch\n\n# Run with dev server (hot reload)\n# Set in settings: \"agentVisualizer.devServerPort\": 3000\nnpm run dev\n```\n\n### Extension Structure\n\n```\nagent-flow\u002F\n├── src\u002F\n│   ├── extension.ts          # VS Code extension entry point\n│   ├── hookServer.ts         # HTTP server receiving Claude Code hook events\n│   ├── sessionManager.ts     # Manages multiple agent sessions\n│   ├── webviewProvider.ts    # Webview panel management\n│   └── logWatcher.ts         # JSONL file tail watcher\n├── webview\u002F\n│   ├── src\u002F\n│   │   ├── App.tsx           # Main React app\n│   │   ├── Graph.tsx         # Node graph canvas (likely D3 or React Flow)\n│   │   ├── Timeline.tsx      # Timeline panel\n│   │   └── Transcript.tsx    # Message transcript panel\n│   └── package.json\n└── package.json              # Extension manifest\n```\n\n## Common Patterns\n\n### Pattern: Debug a Failing Agent Run\n\n1. Open Agent Flow (`Cmd+Alt+A`)\n2. Run your Claude Code command that's failing\n3. Watch the graph — look for:\n   - Red\u002Ferror nodes indicating failed tool calls\n   - Unexpected branching\n   - Loops (agent retrying the same tool)\n4. Click the failed tool node to inspect input\u002Foutput\n5. Check the Timeline panel for which tool call took unexpectedly long\n\n### Pattern: Replay a Saved Session\n\n```bash\n# Save Claude Code output to JSONL during a run\n# (depends on your Claude Code version\u002Fconfig)\nclaude --output-format jsonl > session-$(date +%s).jsonl\n\n# Point Agent Flow at it\n```\n\n```jsonc\n\u002F\u002F .vscode\u002Fsettings.json (project-level)\n{\n  \"agentVisualizer.eventLogPath\": \".\u002Flogs\u002Fsession-1234567890.jsonl\"\n}\n```\n\n### Pattern: Auto-Visualize All Agent Sessions\n\n```jsonc\n\u002F\u002F settings.json\n{\n  \"agentVisualizer.autoOpen\": true\n}\n```\n\nNow every time a Claude Code session starts in your workspace, Agent Flow opens automatically.\n\n### Pattern: Side-by-Side Coding and Visualization\n\n```\n# Open Agent Flow to side so you can code and watch simultaneously\nCmd+Shift+P > Agent Flow: Open Agent Flow to Side\n```\n\nThis opens the visualizer in a split editor, keeping your code files accessible in the main editor group.\n\n## Troubleshooting\n\n### Agent Flow doesn't detect my Claude Code session\n\n1. Verify Claude Code is running in the same workspace folder\n2. Check that hooks are configured: run `Agent Flow: Configure Claude Code Hooks`\n3. Verify the hook server is running — look for \"Agent Flow hook server listening\" in the Output panel (`View > Output > Agent Flow`)\n4. Try `Agent Flow: Connect to Running Agent` to manually specify the session\n\n### Hooks aren't forwarding events\n\n```bash\n# Test the hook server manually\ncurl -X POST http:\u002F\u002Flocalhost:PORT\u002Fhook \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d '{\"type\":\"test\",\"sessionId\":\"test123\"}'\n```\n\nCheck VS Code Output panel for the correct PORT value.\n\n### Graph is empty \u002F not updating\n\n1. Check `agentVisualizer.eventLogPath` — if set, Agent Flow reads from file instead of hooks\n2. Clear the setting if you want live hook-based streaming:\n   ```jsonc\n   { \"agentVisualizer.eventLogPath\": \"\" }\n   ```\n3. Reload VS Code window (`Cmd+Shift+P > Developer: Reload Window`)\n\n### Extension not loading\n\n```bash\n# Check VS Code version meets requirement\ncode --version\n# Must be 1.85 or later\n\n# Check extension is enabled\n# Extensions panel > search \"Agent Flow\" > verify enabled\n```\n\n### Multiple sessions showing in wrong tabs\n\nEach session is identified by a unique session ID from Claude Code. If sessions are merging incorrectly, check that each `claude` process is started fresh (not reusing an existing session ID).\n\n## Resources\n\n- [VS Code Marketplace](https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=simon-p.agent-flow)\n- [Demo Video](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=Ud6eDrFN-TA)\n- [GitHub Repository](https:\u002F\u002Fgithub.com\u002Fpatoles\u002Fagent-flow)\n- [CraftMyGame](https:\u002F\u002Fcraftmygame.com) — the project that inspired Agent Flow\n- [License: Apache 2.0](https:\u002F\u002Fgithub.com\u002Fpatoles\u002Fagent-flow\u002Fblob\u002Fmain\u002FLICENSE)\n",{"name":5,"triggers":24,"description":7},[25,26,27,28,29,30,31,32],"visualize claude code agents","debug agent tool calls","see agent execution graph","monitor claude code sessions","agent flow vscode extension","watch agents think and branch","trace agent tool call chains","configure claude code hooks for visualization","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fskills_sh\u002Fs\u002Fskills-sh_aradotso_trending-skills_agent-flow-visualization",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill agent-flow-visualization",{"tool":48,"command":49},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill agent-flow-visualization",{"tool":51,"command":52},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill agent-flow-visualization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fskills_sh\u002Fs\u002Fskills-sh_aradotso_trending-skills_agent-flow-visualization\u002FSKILL.md",true,[],[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]