Panel and the Agentic Research Workspace: When the Agent Builds Its Own UI

Panel and the Agentic Research Workspace: When the Agent Builds Its Own UI

Revised 2026-10-02: adds the third Show HN thread (Oct 1–2, 22 pts / 4 comments) — the founder's launch comment now discloses the full architecture, the harness limitation, and the license; community questions zero in on layout persistence and MCP integration.

Third Show HN thread (id 49712621). The founder's launch comment (greentfrapp) fills in the deployment and licensing facts the earlier threads lacked:

• Fully local-first: "Panel is a local web app with dockable panes made with dockview. You get chat, files, PDFs, markdown and Jupyter notebooks... Everything runs on your machine."¹ Stack: "a Vue + dockview frontend and a Python (FastAPI) sidecar that drives the agent backends." Data lives in ~/Panel/ outside the repo, so re-cloning keeps it.
• Harness lock-in is the honest limit: "Full support is Claude Code only, so you need it installed and signed in. Codex and other harnesses are not supported yet." The Modules "don't work with OpenAI API yet." The workspace's agent-agnosticism is currently one harness deep. MIT licensed.
• Module Protocol (typed Inputs/Outputs/Intermediates + a data abstraction layer mapping URIs to in-memory or local-file objects, disclosed in the Sept 27 thread) now ships one working Module — literature review — plus an early hypothesis-generation Module that "ha[s] no view of their own, so their results can be hard to read."
• Community signal — persistence and MCP. Two of the four comments are the telling ones: "letting the agent build its own panes is a neat idea. do people keep the layouts it creates?" (quietraster) and "In my opinion it can be more usefol if I can add it with an mcp server, so I can use with my agent and test it in real workflows to see if it can add power and some prons to my agent" (Gabry848).

Meaning for the market map. The two questions users immediately ask an agentic research workspace — does the agent-built structure persist? and does it slot into my existing agent stack via MCP? — are exactly the two surfaces where a model-agnostic orchestrator differentiates (Market Map & Positioning: Where Does Hey, Lefty Fit?, Destination vs. Backend: The Research-Tool Market Bifurcates — and Both Layers Converge on MCP). Panel's Claude Code-only constraint is the strongest recent evidence that harness-agnostic workspaces are genuinely hard to build; the unprompted MCP-integration request is live demand for the both-ways MCP pattern (Integrating Custom MCP Servers into Hey, Lefty's Research Cycles). Panel remains the closest open-source analog to the local-first research workspace layer — and its "rough around the edges" self-assessment ("I've been adding to it as I use myself") shows how early this layer still is.