Skip to content

feat(claude-plugin): a TongFlow panel in Claude Code; Studio page links that open on a file - #220

Closed
tong-io wants to merge 1 commit into
mainfrom
feat/claude-plugin-pane
Closed

tong-io wants to merge 1 commit into
mainfrom
feat/claude-plugin-pane

Conversation

@tong-io

@tong-io tong-io commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Why

Claude Code cannot embed the Studio — it is a web page (canvas, image and video previews) and no surface draws one. Until now the plugin drew nothing of its own, so in Claude Code TongFlow was tools plus a link. This gives it the part that is plain text, and lets the page open only when someone wants to look at a file or a workflow.

What

claude-plugin/tongflow 0.2.0

  • /tongflow opens a panel: a project picker and the folder tree of the project in work. It also opens by itself the first time Claude uses a TongFlow tool, refreshes after every TongFlow tool call, and follows the project the agent moves to (a project the person picked is not undone by a refresh).
  • Every file and workflow in the panel is a link to the Studio page, opened on it. Folders are headings.
  • The panel reads the studio over the page's own local routes. It finds the page through tongflow_studio_page; a plugin's tool call is put to the permission prompt like any other, so the mod always allows that one tool (it returns a local link and changes nothing).
  • Panel state lives in $.state under a typed contract (types/index.d.ts). The billing dialog and the status line are unchanged.

tongflow-studio 0.1.1

  • The Studio page opens where a link says: ?project=<id>&file=<key> (StudioShell project / file). A pinned project is not followed away from. tongflow_studio_page takes project and file, so the agent can hand out a link to one result.
  • serve.ts accepts the access token as Authorization: Bearer, for a client that is not a browser.

Verified

  • claude plugin validate and claude plugin test (10 tests, Claude Code 2.1.287). The panel's tree validates on the terminal, desktop and vscode surfaces; tsc against the engine's declarations.
  • /tongflow in a real headless session against the real server: TongFlow panel opened: 15 project(s), showing apple. — the debug log shows the routes answering 200 and the pane placed. The first attempt was refused at the permission check, which is what the always-allow hook is for.
  • Deep links in a browser: an output image previewed, a workflow on the canvas (5 nodes), under localhost.
  • pnpm lint:check, pnpm typecheck, pnpm build:packages, pnpm test:packages (tongflow-studio 49, dsh-tongflow 10).

Not verified

  • How the panel looks on any real surface. The test kit checks the tree each surface accepts, not its paint; nobody has seen it drawn in the desktop app, VS Code or a terminal yet.

Order

.mcp.json pins tongflow-studio@0.1.1, so 0.1.1 is published before this merges.

🤖 Generated with Claude Code

…ks that open on a file

Claude Code cannot embed the Studio (a web page: canvas, image and video
previews), and until now the plugin drew nothing of its own. Give it the
part that is plain text, and let the page open only when someone looks.

claude-plugin/tongflow 0.2.0
- `/tongflow` opens a panel: a project picker and the folder tree of the
  project in work; it also opens by itself the first time Claude uses a
  TongFlow tool, refreshes after every TongFlow tool call and follows the
  project the agent moves to. A file or a workflow is a link to the Studio
  page, opened on it.
- The panel reads the studio over the page's own routes. It finds the page
  through tongflow_studio_page; that call is put to the permission prompt
  like any tool call, so the mod always allows that one tool.
- State lives in $.state under a typed contract (types/index.d.ts).

tongflow-studio 0.1.1
- The Studio page opens where a link says: ?project=<id>&file=<key>
  (StudioShell `project` / `file`); a pinned project is not followed away
  from. tongflow_studio_page takes `project` and `file`.
- serve.ts accepts the access token as a bearer credential, for a client
  that is not a browser.

Verified: `claude plugin validate` / `claude plugin test` (10 tests; the
panel's tree validates on terminal, desktop and vscode); `/tongflow` in a
real headless session against the real server ("15 project(s)"); deep
links in a browser (an output previewed, a workflow on the canvas).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@tong-io

tong-io commented Oct 2, 2026

Copy link
Copy Markdown
Owner Author

Closing without merging: the mod is being removed from the plugin altogether (it added little that Claude Code can actually draw). The branch stays, in case the Studio page deep links (?project=&file=) are wanted on their own later.

This branch had an error being deployed

1 failed deployment
npm — 6a894551 Deployed Oct 2, 2026 by tong-io via Build, test, publish #17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant