Skip to content

feat(ext): run / prove / debug digital twin - #16

Open
w1ne wants to merge 4 commits into
mainfrom
feat/context-first-p0
Open

feat(ext): run / prove / debug digital twin#16
w1ne wants to merge 4 commits into
mainfrom
feat/context-first-p0

Conversation

@w1ne

@w1ne w1ne commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Summary

Agent workbench can run, prove, and debug the digital twin (hosted MCP), not only chat.

  • labwired.runOnTwinlabwired_run with .labwired/diagram.json
  • labwired.proveOnTwinlabwired_verifymodel_verified
  • labwired.debugOnTwinlabwired_debug + F5 if LabWired Debugger installed
  • Chat empty state: Run / Prove / Debug buttons
  • Verify/Debug modes hit twin before freeform agent

Requires

  • Signed in (labwired login)
  • Twin mint ready (New board / Import)
  • Hosted MCP with twin tools deployed

Test plan

  • New board esp32-c3 → Run on digital twin
  • Prove on digital twin → model_verified or clear red
  • Debug on digital twin → MCP probe and/or DAP

w1ne added 4 commits August 11, 2026 02:36
Sync zero-dep buildLabwiredContext into extension; workspaceContext is
fs pack only. AGENTS.md session orientation. Parity script for ship gate.
board.json writes mint_ok/supported_part_count; multiImport uses sole
flag engine; workspace e2e script for ship gate.
Hosted MCP labwired_run, labwired_verify, labwired_debug using
.labwired/diagram.json. Chat buttons + commands; F5 DAP when LabWired
Debugger is installed. Verify/Debug modes hit the twin before agent.
Default twinBackend=local: stdio @labwired/mcp labwired_run (demo ELF)
plus CLI smoke. hosted/auto optional. Debug prefers local DAP then MCP.
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