March 26, 2026

Build Log 07: The Platform Layer.

Mar 2 — building the invisible parts that make the visible ones hold up.

The features were done. The UI worked. But a product is not its features — it's the platform underneath that decides whether those features stay reliable at scale.

Slash Commands

Eight of them: /compact, /plan, /diff, /cost, /context, /clear, /resume, /skills. Power-user shortcuts for people who live in the keyboard. /compact compresses conversation history. /cost shows token usage. /context shows what the agent currently knows. Small tools, big difference in daily use.

Platform Features

Six pieces of infrastructure landed the same day. Context window management so conversations don't silently degrade when they get long. Parallel execution so the agent can handle multiple actions without blocking. Skills and reusable prompts for teams to codify their workflows. Webhooks for external integrations. Token and cost transparency so teams know exactly what they're spending. Workspace-level instructions that shape agent behavior across all channels.

Realtime fallback polling for when websockets degrade — because websockets always degrade eventually. 49 unit tests. Agent branch switching fix. Knowledge base search with full-text indexing.

The Invisible Work

None of this shows up in a demo. Nobody screenshots their context window management. But this is the layer that determines whether the product works on a Tuesday afternoon three months from now, when the team has 200 threads and the agent has processed 10,000 messages.

The visible features were done. Now it was about making the invisible parts robust.