The feature list is now in its collapsed state by default. This helps simplify the interface and direct more focus to the functional area (INVENT, IMPLEMENT, INSPECT, ITERATE). In the vertical center of the list, you can click the expanding arrow to toggle the state. The state is remembered locally in your browser and will restore to your desired state across page refreshes. The selected state will apply across all of your projects.
Opening a project lands you on an Overview page instead of dropping you straight into the backlog and the four phase tabs.
The Overview provides you with: Waiting on you, naming exactly what's waiting on your role, and Suggested next, ranking what to do across every assessment and your open ideas so a critical finding never sits below a nice-to-have. They are followed with Delivery, Shipping, and Cost to report how the build is progressing and what it's cost so far. About — provides a short description of the project itself, pulled straight from the executive summary of its functional spec, for anyone who lands here without already knowing the project — finally Outcomes, which pairs your goals' progress with the live usage they're measured against (and still shows that usage even before a goal has been set), and Risks, covering every critical or high finding across your assessments whether or not it's reached the backlog yet.
A health pill at the top shows the project's overall score at a glance and opens the full seven-signal breakdown when clicked. Every card takes you to exactly where its information lives — the backlog, a specific assessment, or the exact finding inside it. The whole page takes its color from the project's own icon, blurred into the light behind the panels. Which surface you were last on is remembered, so if you live in the backlog you'll keep landing there; bring the Overview back anytime with the header button or ⌘⇧O (Ctrl+Shift+O).
Settings → General's Project Logo field now has a second option next to uploading your own image: pick from a gallery of 24 pre-made icons — 16 solid colors and 8 gradients, each with a generic app-icon mark — instead of needing an image ready. Picking one applies it the same way an upload does.
Preferences → Background, in the account menu, controls the blurred wash of color behind the Overview (and, if you turn it on, the rest of the workspace too) — drawn straight from whichever icon the project has set. Turn it on or off, dial its Intensity from 20% to 150% so a vivid icon can be pulled back or a muted one pushed further, and set the Icon Scale to change how large the icon reads before it's blurred into the light. Paired with the new stock icons above, a project's background can now be as colorful as the icon you pick for it.
The "Add project" menu now has a third option, "Blank Project", alongside Describe Your Project and Analyze Existing Repo. Give it a name and, optionally, a group (pick an existing one or create a new one), and it opens straight into the Invent tab with no specs. The Project Functional Spec and Project Technical Spec cards flag themselves with a dashed border and dot badge when empty so it's obvious content is still needed. The functional spec can be typed or pasted in by hand; once it exists, the technical spec can either be written the same way or generated from it via the architect interview button in the Technical spec viewer.
The INVENT tab's project view has been redesigned around a "Project Specifications" header showing your total feature count and remaining estimated duration and cost at a glance. Below it, Project Functional Spec and Project Technical Spec cards open a slide-in panel with the rendered spec and an explicit Edit button for switching to markdown editing. A "Selected Feature" card shows the currently selected feature across four tabs — Deliverables, Functional Spec, Technical Spec, and Work Breakdown, each with its own download button — replacing the previous sub-tab-and-scope-dropdown layout.
Aggregate estimated duration, cost, and story point totals — shown in the feature-list header, each bundle/version header, and the INVENT tab's Project Specifications stats — now exclude features that are already Done, so they reflect the work still remaining rather than the whole project's history.
Every project now has an "Ask Agiloop" panel — open it from the sparkle icon in the project header (Contributor role and up) to ask questions about the project in plain language. Answers are grounded in the project's own specs, backlog, and assessments rather than generic knowledge, and it's aware of what you're currently looking at, so a question like "what depends on this?" resolves against the feature or finding you have open without you needing to name it. Each answer cites its sources as clickable chips underneath — click one to jump straight to the feature it references, the relevant Iterate assessment (Readiness, Usability, Compliance, Competitive Analysis, Ideas, Bugs, or Technical Debt), or the exact file and line range in your connected repository. It's read-only: it can explain how something works and point you to what's relevant, but it never makes changes on your behalf, and it's upfront when it's giving general knowledge or an assumption rather than something drawn from your project. Conversations pick up where you left off if you close and reopen the panel, and "New conversation" starts fresh. There's a daily per-project question limit to keep it sustainable to offer for free. Projects with a connected repository and an Iterate+ subscription also get semantic code search, so answers can be grounded in your actual source code as well.
The Iterate tab now has a "Usability" view that tests a running app by its live URL. Give it a target URL — and, optionally, login credentials, which are never stored and are discarded once the run completes — and an AI agent drives a set of realistic user journeys against it, capturing a screenshot at every step. Each run evaluates accessibility (WCAG rules), UI/UX heuristics, and journey completion, and turns what it finds into backlog-ready recommendations. Depth (Quick, Standard, or Deep) controls how many journeys are tested, and Device Coverage can extend testing to mobile viewports as well as desktop. Each journey gets an outcome badge — Success, Dead End, Error, or Incomplete — and hovering one explains what it means, and an "Onboarding Funnel" section derived from the journey transcripts reports completion rate, steps to success, and required inputs/decisions. Requires an Iterate+ entitlement.
Usability is now a seventh signal in the Overall Project Health score, reweighted alongside Readiness, Goals, Code Health, Compliance, Competitive Analysis, and Ideas. The Summary dashboard has a Usability card with a category radar chart. There is also an in-panel "How this works" dialog that explains the assessment pipeline and its settings.