Taiga Chat Agent
Ask an agent what a product's specification decided, what the code actually does, why last night's build failed or what to build next, and every answer says what it read.
Changelog
Dated the day they shipped, newest first. Follow the feed.
Ask an agent what a product's specification decided, what the code actually does, why last night's build failed or what to build next, and every answer says what it read.
Discovery writes the whole document set from your specification in one run, marks every document a later edit leaves behind, and ends with a set the rest of the product can trust.
Connect the registries that serve your private packages, whether they hold npm packages, Terraform modules, Python, NuGet, Go or Cargo, and every run installs them the way your own engineers do.
Import a codebase and the first backlog holds only the work a one-click fix on the Maintaining tab cannot cover: the missing capabilities behind its findings and policy gaps, checked against the code before they are proposed.
Teams are now factories and projects are now products, and an organization runs as many factories as it needs, each with its own instructions and knowledge that every product in it builds on.
Taiga fits into the delivery process you already run: it works on the branch your team chooses and leaves infrastructure and pipelines to the teams that own them.
Each run reads as a record of one attempt: what every step set out to do, what it achieved, and the evidence behind it.
Ask for a modernization, a platform migration or a large refactor and Taiga plans it as a sequence of initiatives, each one shippable on its own.
An email address that belongs to a project, a team or the organization, rather than to a person, receives each action-required item raised in that scope, which is also how the inbox reaches a Slack channel.
Import the requirement spreadsheet a regulator or customer sent and Taiga answers what the project's documents support, each answer naming the document and version it rests on, written back into your own file.
One page per initiative: the description, the plan, and its history in order, from who defined it through each run and the pull request it opened.
The application sits on a new shell, with the content lifted onto a panel that scrolls on its own, and two more themes, Boreal light and Boreal dark, beside Midnight.
Line initiatives up and Taiga works them one at a time: it plans the first, builds it, opens a pull request, and now merges that itself once your rules allow.
Editing the User Flows document is a conversation. Say what is wrong and the agent writes the change into the document as you watch.
Taiga drafts nine design concepts, picks the combination that works together, and shows it as one screen you can change a piece at a time.
Alongside vulnerable dependencies, a maintenance sweep now looks for committed secrets, insecure code and infrastructure misconfiguration, each found by its own scan.
Where a project stands against the policies you publish, with every gap carrying the control it contradicts and the passage from the document that shows it.
The phase where a project gets defined has been reworked around the work you actually do in it: moving through the steps, reading and editing the documents it produces, and signing them off.
Line up initiatives in the order you want them built. Taiga plans and runs the first, opens a pull request, and starts the next when you merge it.
Taiga has been in production since May 13, 2026. The record runs forward from today.
Security posture, subprocessors and the trust documents change on their own register: trust center updates.