W11 — Agentic chat, local LLM panel, blog scaffolding
The chat panel learns to call tools. Local LLMs become first-class citizens. The Astro blog scaffolding goes up — eventually, the very page you're reading.
A small-commit-count week (4 commits) but each one heavy. Three threads converged.
What shipped
- Local LLM chat panel. Master prompts, self-healing improvements, the bones of a chat surface that doesn’t depend on cloud inference. 3k LOC. The single biggest reason this matters: cost no longer scales with curiosity.
- Agentic chat with tool calling and Brave Search. The chat panel grew tool invocation. Brave Search wired in as the first tool. Local LLM analytics added — token usage, latency, model-comparison views. This is where chat stops being a transcript and starts being an agent surface.
- Astro blog initial scaffold. First commit on the aj-blog repo: content collections, a hello-world post, RSS feed. Almost no styling — that comes later. The pipeline from cockpit blog panel to public site begins to take shape.
Architecture moves
The decision to make tools a first-class concept in the chat panel — rather than a bolt-on for one particular model — set up everything that came later. By W15, flows themselves became tools. By W18, the Telegram bridge inherited the same shape. The earlier you get the abstraction right, the more cheaply everything downstream ports onto it.
By the numbers
- 4 commits (3 playground, 1 aj-blog)
- +9,517 / −699
- 3 milestone-class drops
What’s next
Public-facing site with the proper design treatment. Begin the long arc of consolidating jobs onto the flow runtime — the architectural decision that defines the next month.