Taming the LLM

Changelog v0.1.2: Taming the LLM (Deterministic AST Generation)

Let's address the elephant in the room: Most AI coding assistants are just glorified autocomplete. They are fantastic at writing a 10-line Python function, but if you ask them to architect a multi-file, full-stack application, they lose context, hallucinate package names, and output code that immediately crashes on compilation.

You can't build production software on a slot machine. Code needs to be deterministic.

With v0.1.2, we’ve completely overhauled how Gor://a’s brain interacts with the syntax it writes. We didn't just tweak the system prompt; we rebuilt the generation pipeline.

What we shipped in v0.1.2

• The ReAct "Planner & Coder" Split: We separated the AI's "thinking" from its "typing." Gor://a now runs a dual-agent ReAct loop. First, the Planner Agent drafts a strict JSON architectural blueprint based on your prompt. It maps out the exact file tree, dependencies, and state management flow. Only when the blueprint passes internal validation does the Coder Agent actually start generating syntax.

• AST (Abstract Syntax Tree) Validation: LLMs write text, but compilers read trees. We introduced an intermediate AST validation step. Before Gor://a writes a file to your WebContainer, it parses the generated code into an AST to check for syntax validity, missing imports, and scope errors. If the AST parser throws an error, the Coder Agent is forced to fix it before you ever see it on your screen.

• Context-Aware Token Routing: We implemented a custom chunking algorithm that keeps our context window incredibly lean. The Coder Agent only "sees" the specific files and interfaces relevant to the component it is currently building, completely eliminating the "context bleed" that causes other AI tools to hallucinate variable names across different files.

Why this matters

The result is a massive drop in hallucination rates. When you tell Gor://a to build a Stripe checkout flow, it doesn't just invent a random API wrapper. It reads the blueprint, imports the exact correct SDK, writes the frontend form, wires up the backend webhook, and validates the syntax.

It means when you hit "Generate," the code actually compiles.

What's Next?

We are actively stress-testing this new ReAct loop on complex database migrations (Postgres/Supabase). Early results are wild, but we are optimizing the latency before we push it to the main branch.

Keep an eye on your inbox. Private beta invites are rolling out soon.

— The Gor://a Team