Tapeo for VS Code (preview)

Work on your Tapeo hardware projects from VS Code. Edit RTL locally, run the server's workflow (simulation through layout checks), and see the results without switching to the browser. The extension uses your Tapeo account and the same server, files, workflow queue, and plan as the web app.

Get started

1. Run Tapeo: Connect to Server and choose Sign in with your browser. Check that the code matches, approve the device, and VS Code finishes signing in. The token is kept in VS Code's secret storage.
2. Open an empty folder and run Tapeo: New Design with the Architect (describe the hardware, answer its questions, choose an option, build), Tapeo: Create Project (an empty project), or Tapeo: Pull Project Files (an existing project).
3. Edit files, Tapeo: Push All Changes, then Tapeo: Run Workflow. The status bar follows the run. When it ends, tool errors appear in the Problems panel on the lines they name.

Features

• New Design with the Architect. The Architect asks clarifying questions in quick picks, proposes design options, and shows the build plan. Building uses one build from your plan, then the generated files are pulled into the folder.
• AI Engineer. Tapeo: Open AI Engineer opens a chat beside your editor. It shares the project's conversation with the browser, and answers stream in as they are written. Proposed file changes can be reviewed as a diff and applied to your local files. Applying is refused while the file has unsaved edits. Push afterwards to save the changes in Tapeo.
• Tool problems. Errors from Verilator, Icarus Verilog, Yosys, and OpenROAD/OpenSTA scripts are shown on the matching project files. Warnings are shown too when a tool step failed. Tapeo: Show Tool Problems reads the latest run again.
• Runs and results. Run the full workflow, one stage, or a stage and every later one. You can also cancel a run, read stage results, open tool logs, and check the goal report.
• Safe sync. Each push sends the version your edit was based on. If the server file changed meanwhile, your edit is kept and the server copy is saved under .tapeo/conflicts/ for comparison. Tool outputs are read-only.

Commands

Connect to Server · Sign Out · New Design with the Architect · Create Project · Pull Project Files · Pull Tool Outputs · Show Local Changes · Push Current File · Push All Changes · Delete Current File on the Server · Run Workflow · Show Workflow Runs · Show Run Details · Open a Tool Log · Show Goal Results · Show Tool Problems · Cancel Workflow · Open AI Engineer · Ask the AI Engineer · Review Proposed Changes · Apply All Proposed Changes · Discard Proposed Changes · Open Project in Browser

Limits

• The AI Engineer sees the server copy of your files. Push local edits before asking about them.
• Image and PDF attachments for the Architect, the 2D/3D layout views, and the Evaluation editor are in the web app.
• Problems are found by reading tool logs. Messages without a file and line, or about files outside the project, appear only in the tool log.

Settings

• tapeo.serverUrl: the Tapeo server. Remote servers must use HTTPS.

A terminal client with the same features is available as tapeo-cli on npm.