The code tool is not quite ready for beta release, however, we have working demos for chat to architecture (determining the structure of a project and automatically generating all of the pre-requisite files) and Fully or Semi automated generation of each file for the project working, we were even able to one-shot a working pong game:

Zero to Pong in Two Minutes
Here’s a web-based pong game (desktop-only, sorry mobile users!) that was created using the code tool in just about two minutes: Pong Web Game Using typical chatbot interfaces this same project would have taken ~an hour generating files and discovering links one at a time. Using a tool like Codex
Pulse AIMatt Krueger
Video - Chat to Architecture in Pulse Code
0:00 /0:20 1× Quick update on the code editor - something that all the available tools miss is talking to the user about implementation and determining the general structure before diving in and starting to develop things. This is a demo of “chat to architecture” where an AI
Pulse AIMatt Krueger
Fully Automated In-App Progressive Code Generation
Working nicely - I still need to fix some bugs with the export/import feature but as you can see you can go from a conversation, to an architecture, to an app in ~8 minutes. 0:00 /1:57 1× I’m not 100% sure how to roll this feature out
Pulse AIMatt Krueger

Most of the testing/troubleshooting time this week went to making sure that changes to the description, pseudocode, links, and raw code cause the correct cascade of updates to the PML files representing the architecture. This is working reliably now in the lab, so we'll move on to finishing the tool.

The features that still need to be completed are:

  • Automated generation of PML from an existing codebase without making changes to the code to trigger the workflow
  • "Troubleshoot" tool that allows you to pop open an analysis pane next to your code and discuss error messages, design changes, etc with an AI assistant
  • "Recon" tool that determines which files are most likely involved in an error message or glitch you're seeing and prompts you to add them to the troubleshooting tool

I expect to have the full code tool in the hands of at least a few beta testers by the end of next week.

Bug Fixes

I got a surprising amount of cleanup done this week including:

  • removing unused fields from the ACL Rule editor
  • fixing the cancel button on the ACL Rule editor
  • fixing the delete all button/backend functionality for digests
  • general mobile-friendly CSS adjustments in several pages

Known Issues

  • Long running requests through the ingest tool return 500 errors instead of a "check digests for long running requests" warning (will fix this week if time allows, otherwise first sprint after code tool is done)
  • Comma-separating multiple tags in the ingest tool does not work (will fix next sprint - sorry!) you can still manually add tags in the digests page as a workaround
  • Video ingestion does not work in Qwen mode because of a relatively simple tokenizer mistake I didn't catch on the backend - this should also be fixed this or next sprint depending upon workload for the code tool

Infrastructure Issues

  • Only one infrastructure issue this week, a GPU node experienced a driver crash and needed to be restarted, health checks dropped this node's endpoints out of the cluster, there was no impact to users.

That's all for this week - Happy testing!