---
title: "Helix, rebuilt around your project data"
description: "Helix now works from one set of tools across every part of the product, shows its working as a timeline you can open, links straight to what it touched, and sizes sprints from real estimates."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.heizen.work/llms.txt
> Use this file to discover all available pages before exploring further.

# Helix, rebuilt around your project data

Helix used to route your request to a specialist behind the scenes — one assistant for sprints, another for the wiki, another for tests. That routing was invisible when it worked and confusing when it didn't, and a request that spanned two areas often stalled between them.

It now works directly from your project data using one small set of tools that cover every entity in the product: sprints, tasks, stories, bugs, requirements, wiki pages, test suites, diagrams, meetings, and email threads. Nothing gets handed off, so nothing falls between the gaps.

## See exactly what it did

Every reply now opens with a working area — a running list of what Helix read, created, and changed, in order. It stays open while Helix works and folds away once the answer is ready, so the summary is what you're left with.

Open it and each step expands. A step that touched a single record links straight to it; one that touched many links to the page where they live. Records created or updated in the reply are clickable too, so a new story takes you to its sprint board and a new wiki page opens the page itself.

## Sprints sized from real numbers

Sprint planning now derives the sprint count from estimated hours rather than the number of features. One sprint is one week — 40 to 45 hours of story estimation — and parallel sprints are named as a pair and filled to 90 to 100.

In practice this means a piece of work worth 60 hours becomes two sprints instead of eight thin ones, and the plan you get back reflects how long the work actually takes.

## Clearer while it thinks

Helix narrates as it goes, so you can follow its reasoning while it works rather than waiting for a verdict. The working indicator stays visible for the whole turn instead of disappearing at the first step, and tips about what Helix can do appear while you wait.

Source: https://docs.heizen.work/releases/1-11-1/index.mdx