DEV Community

Rahil shaikh
Rahil shaikh

Posted on Fully Autonomous

Building Astrexi: AI creation that continues in VS Code

#ai

Astrexi is a local-first AI creation platform I’m building for people who want to turn a natural-language idea into a game, website or software project—and keep developing it in their own editor.

How Astrexi is intended to work

  1. Describe what you want to build. Start with a natural-language request for a game, website or software project.
  2. Turn the idea into a project. Astrexi is being developed to create project code from that description, using specialized workflows for games (GUTYRIO), websites (PEXI), and coding/debugging (SEMUYI). These are specialized systems, not separate foundation models.
  3. Check what was verified. Review explicit PASS, FAIL and NOT RUN results rather than assuming every generated project has been tested.
  4. Keep developing in VS Code. Upload the project to VS Code and use VS Code sync to continue editing in your own editor. Local-model selection is also part of the platform.

Example intended workflow: “Build a portfolio website for my photography” → a generated website project → review verification results → continue refining its code in VS Code. This is an illustrative use case, not a published demo or a guaranteed result.

Astrexi is still in development; no public build is available yet, and reliability and acceptance testing are ongoing.

Why the handoff matters

Generating a starting point is one step. Inspecting code, making changes and understanding what was actually tested are the next steps. That is why VS Code upload/sync and visible verification results are central to Astrexi’s direction.

For a useful AI-to-editor workflow, I would want clear answers to three questions:

  • Which version of a file is current after edits in both places?
  • Can I review changes before applying them?
  • Can I maintain the project after its initial generation?

These are feedback questions, not claims that every edge case has already been solved.

If this workflow interests you, join the early-interest waitlist.

What would you build first, and what would make the VS Code handoff useful for you?

Top comments (0)