Skip to content

Conversation

@sxlijin
Copy link
Collaborator

@sxlijin sxlijin commented Nov 19, 2025

control flow viz logic is all vibe coded right now, has not yet been through manual review

  • snapshot tests are in engine/baml-runtime/tests/viz-runtime.rs
  • rerun snapshot tests using build --watch engine/baml-runtime or INSTA_UPDATE=always cargo test -p baml-runtime --test viz-runtime
  • pnpm dev in engine/baml-runtime/tests/viz-runtime/web/ will start the vite app that shows all these results
  • a bunch of the coding agent docs i wrote are in engine/baml-runtime/tests/viz-runtime/docs/
    • docs/viz-runtime/project-goal is handwritten, plan1 is ai generated and 90% reviewed, and the others have progressively less human review on them
    • note that you should use node_id and not lexical_id on the StateUpdate events coming out of VizStateReducer to decide which nodes to highlight/not - lexical_id is not sufficiently unique and should only be used for log filtering

@sxlijin sxlijin temporarily deployed to boundary-tools-dev November 19, 2025 02:54 — with GitHub Actions Inactive
@sxlijin sxlijin temporarily deployed to boundary-tools-dev November 19, 2025 02:54 — with GitHub Actions Inactive
@sxlijin sxlijin temporarily deployed to boundary-tools-dev November 19, 2025 02:54 — with GitHub Actions Inactive
@vercel
Copy link

vercel bot commented Nov 19, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
promptfiddle Error Error Dec 4, 2025 9:29pm

@github-actions
Copy link

@github-actions
Copy link

@github-actions
Copy link

@github-actions
Copy link

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.

3 participants