April 2026

April is the month Nova stopped being a feature and started feeling like a coworker. The agent got a name, a face, and a place to live (Command Bridge), plus explicit approval flows and memory controls so trust doesn't get sacrificed for reach. Planning and delivery moved onto one timeline, and GitHub and Jira sync both ways. Theme of the month: Meet your agent.

In this edition

From Andy

Sometime in mid-April I asked Nova to update a feedback item without watching her do it. She did. Then she did it again on a theme, then on a change. I had to sign off each time, but the loop felt different. Not "click to run an AI feature" but "ask a coworker to handle it." That's the moment Nova stopped feeling like an assistant and started feeling like a teammate.

That shift is what April was about. Command Bridge gave Nova (and the rest of the workspace) a place to live. The new Crew model gave her a face and a presence. Memory compaction controls and explicit approval flows gave her boundaries, which is the part most AI products skip. The Activity Ledger from March got to do its job, because a coworker who can't show their work isn't really a coworker.

The other half of April was about closing the loop from idea to shipped code. The new Changes page puts planning and delivery on one timeline. GitHub and Jira sync in both directions, so issue trackers stop drifting from the workspace. Themes can be exported straight to GitHub Issues or Jira Epics with field mapping. Outcomet stopped being a place where ideas live and started being a place where ideas get traced through to release.

Four release weeks. One new place for the agents to live. One agent that earned a name.

Worth it.

— Andy

Nova steps up as a primary Crew agent

Nova got promoted in April. She has her own avatar and visual presence on the Crew, a dedicated dockable panel (left, right, or bottom, with mobile drawer support), and a streaming Live Timeline that shows what background tasks are doing in real time. By month-end she could inspect and act across nearly every product entity in the workspace: capabilities, feedback, themes, changes, pillars, opportunities, bets, experiments, signals. She can create and update approved feedback and directly manage changes (create, update, link, delete).

Reach without trust would be a disaster. So April also shipped the controls that make reach safe. Background actions that mutate data require explicit approval. Admins get a workspace-level opt-in for AI & Automation, and the agent falls back to read-only suggestions when mutations are disabled. Model selection in Agent Chat lets you pick Haiku, Sonnet, or Opus depending on the depth you want. Memory compaction gets a configurable Sliding Window trigger, in-chat compression markers preserve conversation visibility, and safer defaults retain a larger recent context before summarizing. Background tool activity and AI job results land in the chat timeline so nothing happens behind a curtain.

A place for the work

The main operations hub officially launched as Command Bridge (Bridge in the side nav). It pulls together agents, active learning clusters, and team rosters into one screen so you can see who and what is working on what without hopping between pages. An Active Roster side panel in CrewOverview shows live capability states, and crew cards got a portrait split layout with larger hero visuals. The Dashboard, the Bridge, and the AI assistant panel together make the workspace feel like a control room rather than a bag of tools.

Command Bridge launches as the unified hub for agents, capabilities, and rosters
Active Roster side panel for live capability states
Redesigned crew cards: portrait split layout, larger hero visuals
Persistent, dockable AI assistant panel with streaming Live Timeline
Background AI Jobs Engine with reliable real-time pipeline and persisted job results
System AI presented as Nexus for clearer system identity

Planning meets shipping

The new Changes page is the hinge piece. Planning items and delivery events share one Unified Timeline you can view, filter (by month, capability, status), group, and create from. Four KPIs (Total Changes, Active Integrations, In Progress, Completed) give a project-health snapshot, and inline status editing keeps the board honest.

Underneath, integrations got serious. One-click GitHub connection with historic PR import (selectable date range). Native Jira Cloud with project mapping. Bidirectional sync of issue descriptions across both, so external trackers stop drifting from the workspace. Themes export straight to GitHub Issues or Jira Epics/Stories with configurable field mapping and automatic link tracking. Real-time PR statuses surface in the Changes timeline.

Brand-new Changes & Delivery timeline with month/capability/status filters
KPIs: Total Changes, Active Integrations, In Progress, Completed
One-click GitHub integration with historic PR import (date range)
Native Jira Cloud with project mapping and issue surfacing
Bidirectional GitHub & Jira description sync
Theme export to GitHub Issues and Jira Epics/Stories with field mapping
Real-time PR statuses in the Changes timeline

The strategy map gets honest

Strategy Maps got a structural cleanup. The full three-level hierarchy (Pillar > Opportunity > Bet) was restored and validated, Discovery items now correctly link to their Bets, and Semantic Layers let you group and filter Pillars, Opportunities, and Bets across views. The Strategy Graph itself auto-resizes to panel state, has a deterministic layout, and a new Rearrange Layout control for predictable reflows. Legends and node coloring are synchronized so the visual cues match the semantics. Strategy exports use the right Opportunity/Bet labels and download reliably across browsers.

Restored and validated Pillar > Opportunity > Bet hierarchy
Semantic Layers for grouping and filtering across the strategy view
Deterministic Strategy Graph layout with auto-scaling and Rearrange control
Synchronized legends and node coloring
Reliable strategy exports with correct labels across browsers

By the numbers

4 release weeks
1 net-new interface launched: Command Bridge
1 agent promoted to primary Crew member: Nova
2 issue trackers now syncing both ways: GitHub, Jira

Also shipped

Total Agent Work metric: real-time and historical agent activity trends on dashboards
Account & Billing self-service: subscription, usage limits, and consumption metrics in the user menu
Anonymous feedback submission for candid input
Redesigned FeedbackDetail with Nova Insights collaboration sidebar
Refined S0-S3 severity indicators for clearer prioritization
Default Role for new users (Viewer, Member, Admin) configurable from Members
Unified EmptyState across Discovery, Signals, Capabilities, and Bridge
Capabilities Map fix so dragging or misclicks outside grouped nodes no longer hijack selection
More resilient live chat streaming with reduced disconnects on fragmented message streams
Real-time Changes & Feedback streams with non-intrusive toasts on new items
GitHub sync accuracy fixes: "won't do" and duplicates map to Cancelled, comments don't revert Completed items
Quieter notifications that fire only on real status changes
Tighter typography across operational views (Feedback, Theme, Changelog, Bridge)
Recovered historical content and cleaner error monitoring across the board

Looking ahead

May picks up where Nova's expansion ends. Expect deeper analytical capabilities and tighter handoffs between Nova and the rest of the workspace, especially Discovery and Strategy. The Changes timeline gets richer too as more integrations come online.

If you want a walkthrough of Nova's expanded scope, Command Bridge, or the Changes page, reply here and I'll set up a quick demo.