April 7, 2026

Build Log 12: Plans That Work.

Mar 8 — vague plans were the number one complaint.

"Build the settings page" is not a plan. It's a wish. The agent kept generating plans like that — directionally correct, but missing everything an engineer needs to actually start coding.

Jira Integration

Jira Cloud OAuth with bulk import and 3 agent tools. Same pattern as Notion and Linear — OAuth, encrypted tokens, agent capabilities. Teams can now pull in their existing Jira issues and let the agent work with them directly.

Large Repo Resilience

Async clone with fallback for repos that take too long. Incremental index updates instead of re-indexing the whole codebase on every change. Persistent indexes that survive restarts. Adaptive timeouts based on repo size. Big codebases no longer mean slow agents.

The Plan Overhaul

Every plan now enforces 7 required sections: context, constraints, data model, behavior, UI/UX, acceptance criteria, and dependencies. Skip one and the agent flags it. The plan quote system lets you send a specific section to chat — "look at the acceptance criteria" instead of re-explaining what done means.

Agent Learning

Semantic memory with embeddings so the agent remembers patterns across conversations. Plan templates generated from successfully shipped tasks. Cross-workspace knowledge — a pattern that worked in one project carries over. Feedback loops from message reactions so the agent learns what's helpful.

Now every plan reads like a spec. The agent doesn't just write plans — it writes plans you can hand to an engineer and say "build this."