DEV Community

Fenju Fu
Fenju Fu

Posted on

I built an open-source AI workbench in Astron—and kept the evidence

AI workbench demos often stop at a polished mockup. This one started in a real local Astron deployment and kept the evidence for every important boundary.

Astron creation entry

What was built

The project created a local Astron database named ai_workbench_0820 and a workbench_items table. Four fictional rows were entered manually with a task title, owner, status, channel, maintenance note, and maintainer. The workflow then synchronized a fifth reviewed draft and read all five records back.

Five records in the shared table

The workflow is deliberately small:

Start → AI-assisted draft sync → Prepare page data → End
Enter fullscreen mode Exit fullscreen mode

Four-node Astron workflow

The phrase AI-assisted describes how the draft content was prepared and reviewed. Runtime synchronization is deterministic and consumed zero model tokens.

The adapter boundary

Authenticated database access differs between Astron deployments, so the tested workflow calls a local UI adapter at host.docker.internal:8801. The adapter performs an idempotent sync and returns a stable JSON page contract. It is clearly documented as a deployment-specific integration—not an official built-in Astron connector.

The first write succeeded in the table but exceeded the code node's ten-second limit. Because the adapter checks for the draft title before inserting, the rerun did not create a duplicate. It completed successfully in 6.94 seconds, used 0 model tokens, and returned five auditable records.

Debugger returning five page records

Human approval stays visible

The result contract explicitly lists three operations that remain human-controlled:

  • payment;
  • outbound messages;
  • public publishing.

A collaboration space was created, but no external account was invited. The user preview and publishing request were opened, but the final publish action was not clicked. Astron offered marketplace and API publishing as real UI options.

Astron publishing request

Reuse

The public package contains the tested Astron DSL, integration notes, adapter response contract, bilingual site registration, and horizontal runtime screenshots. The YAML does not contain account credentials, browser state, API keys, or production data.

Top comments (0)