Release notes

This page lists every release in the 0.1 track, newest first. Patch releases are added here as they ship, and the rest of these docs are kept current with them, so the 0.1 docs always describe the newest 0.1 release. For another track, pick it from the version menu at the top of the page. Documentation versions explains how tracks and docs fit together.

Release	Date	Install	Upgrade from
0.1.0	October 29, 2026	Install 0.1.0	0.1 pre-releases

0.1.0

October 29, 2026. The first release of Infrared.

Infrared is a software factory built around the person who manages change. Agents plan, build, test, review and verify; you decide what gets built, what merges and what reaches production, from evidence you can read in a minute. Everything in this release came out of that idea: the work arrives at your desk ready to judge, nothing reaches production without a person, and you never have to go hunting for what needs you.

0.1.0 brings together everything built since September 11, 2026, whether a person or an agent wrote it.

0.1 is an open beta

0.1 needs no license through November 30, 2026 (UTC). See Licensing.

Highlights

• One change flow for people and agents. Ask for a change in a sentence. The architect plans it, you triage it, AgentRoles build, test and review it, and you approve the merge from each step's verdict and evidence. Follow a Change.
• What waits for you, in one place. The rail counts what needs you: triage, approvals, an agent asking a question, a promotion to production. Show only these filters Changes down to it. Built for the person in charge.
• A stuck run you can rescue. An agent that stops asks you up to five questions with suggested answers, and you retry with your guidance. A step Infrared itself can't finish says what happened and what is already done.
• Products first. Products opens on the week in review and the weekly video, and every Product shows its environments, Changes, deployments, releases, SLOs and incidents. Products.
• Safe delivery. Every push to the default branch deploys, zone by zone, under a release guard that holds and rolls back a failing zone. Production waits for your approval. Deployments.
• Releases people can read. Cut a release from what reached production, with notes for engineers and a post for everyone else. Releases.
• A workforce of people and agents. Teams, People, Agents and Access groups in one area, with default Teams in every org. Workforce.
• Summary videos. Each Change gets a short narrated video of what happened, and each org gets a weekly video of its week. Summary videos.
• Runs on your cloud. Use the hosted control plane, or install on your own GKE or EKS cluster with one command. Build workload clusters in Google Cloud and AWS without stored keys. Install.

What's in 0.1.0

Getting started

• Install on your own GKE or EKS cluster with one ir install; --setup --wait takes it all the way to a ready install.
• One install file, infrared.yaml, with secrets read from a file or a command, never from an argument. chartLogin signs in to a private chart registry.
• A setup wizard that resumes where you left off, with an optional backups step, a layer-by-layer view of the platform syncing, and a warning when the gitops repo takes longer than a minute to hydrate. ir setup run scripts it.
• GitHub or Gitea as the forge. With Gitea you need no GitHub organization.
• The hosted control plane at infrared.darkshift.io, by invitation.

Products

• Products opens on the week in review: the week's story, what stands out, activity per Product, this week against last, and the weekly video.
• DORA figures across every Product and production uptime in one strip, and open incidents across all Products under the cards.
• A card per Product shows what is moving now, where it runs, what waits for you, what shipped lately with its summary video, and production's SLOs.
• A Product's page has four tabs, Environments, Changes, Deployments and Releases, and a shield that shows where a person approves its Changes and promotions.
• Product settings on a page of their own, with every field editable.
• Start a Product from a zip or a template and get a private, running preview with nothing to write. Set up delivery for repos you already have, with the build detected for you.
• Umbrella delivery ships several repos as one versioned chart, with whole-version rollback.
• Environments in promotion order, each with its own page (Overview, Live, History, Settings), Guarded or Fast deploys, editable smoke and guard checks, and a move to a workload cluster.
• Custom domains with DNS checks that name the exact record to add, and redirects.
• Environment variables and secrets per environment, with .env paste.
• Default uptime, edge error and edge latency SLOs for every Product; alerts open incidents; a public or signed-in status page with 30 days of uptime.
• Logo suggestions designed by Claude.

Changes

• Ask for a change in one sentence on a Product's Changes tab. The architect turns it into a planned issue.
• Triage each planned request: Build it or Hand to a person.
• Changes groups every request by Waiting for you, In progress, Done and Stopped, with its cost and video. Every entry is the full log: agent runs, merges, approvals, builds, deployments, rollbacks, settings changes and syncs.
• A Change's page shows its journey from issue to deployment, each step's verdict card in plain words, a live timeline and each step's record and evidence.
• Approve from evidence: each step's verdict, what it recorded, its evidence and its log, with the run's cost and success criteria.
• An agent that stops asks up to five questions with suggested answers; retry with guidance in the app or with ir run retry --guidance. Cancel a run in the app or with ir run cancel.
• Reviewers send a Change back to the builder a set number of times. The QA engineer decides whether the code or the test is wrong and works the fix out with the builder on the same branch.
• Comments on the issue steer every agent. Closing an issue or pull request cancels its runs.
• One switch per Product turns human approvals off, with a confirmation. A blocking verdict or a stopped step still waits for a person.

Deployments

• Every push to the default branch deploys; pushes within two minutes of each other ship as one deployment.
• The Deployments page shows what is on its way first, each environment's state, and who asked.
• A deployment's page has its environments, release guard, screenshots, build steps and log, what ships, and where the lead time went.
• Promotion zone by zone under a release guard that holds and rolls back a failing zone. Go now ends a hold early and records who pressed it.
• Approve production from the page or with ir deployment. An open infrared:blocks-release issue holds production.
• Retry or dismiss a failed deployment.

Releases

• Announce the release track production runs, or cut the next minor or major.
• A nudge on the Product's Releases tab once there is enough in production to tell.
• Release notes for engineers and a post for everyone else, drafted from conventional commits and editable before you cut.
• Cutting tags the commit and the production image and publishes the GitHub release. A cut that fails partway resumes without repeating a tag.
• The org's Releases list, a page per release, and a reading page for its post. ir release cut, ir release list and ir release get.

Workforce

• One area for Teams, People, Agents and Access groups.
• Eight default Teams in every org, with a one-step way to put them back.
• Team states (People and agents, Agents only, Lights out), a guided New Team flow, and a Team's page with its members, processes, access, context, status and activity.
• An opt-in daily status per Team.
• Import people from sign-ins, Google Workspace, Slack, GitHub or Gitea, or add a person by hand. A person's page credits their work and never ranks it.
• AgentRoles grouped by Team. Edit an AgentRole's opinions, guardrails, success criteria and instructions, and reset to the catalog's.
• Weekly spend budgets and a circuit breaker per AgentWorkflow.
• Model tiers (Frontier, Balanced, Fast) with recommended models, per-step overrides, and cost by AgentRole and by step.
• A default catalog of AgentRoles and AgentWorkflows seeded into every org, each one yours to edit or switch off. Default catalog.

Clusters

• Register a workload cluster by kubeconfig, or build a GKE or EKS cluster from a template.
• Builds take short-lived credentials from a cloud account, and a built cluster connects itself. Cloud accounts reach Google Cloud and AWS with no stored keys.
• Platform admins can let an org's admins register and build clusters of the org's own, on the org's own cloud bill.
• Deleting a cluster shows what it removes and an hourly cost estimate first, then backs up disks, moves or removes environments, and sweeps for leftovers.
• Template conformance proves cluster templates on a schedule under a monthly cap.
• Agent steps can have a node pool of their own, sized memory and a fenced network.

Usage

• An AI usage chip on every page, green, amber or red.
• The Usage page: today's spend, budgets and what is left, Gemini daily limits, spend by day, Claude by model and AgentRole, and Anthropic rate limits.

Access

• Sign in with Google for your Workspace domains through your own OAuth client, or with GitHub through the platform org's GitHub App.
• Sign-up: an install can let anyone with a Google account get an org of their own, with limits on Products, people and Teams.
• Access groups give each org a role by Workspace group, email address or GitHub login. Roles follow Workspace groups within about two minutes, and Infrared fails closed when it can't read them.
• GitHub teams kept in step with access groups.
• Linked GitHub, GitLab and Gitea accounts on the You page; Infrared keeps no forge token.
• Break glass: the root password lives only in your vault, every use is recorded, and you can rotate it.
• API tokens act with their owner's live roles. ir open signs a browser in without a password.
• Platform admins create orgs on the install's Gitea or on GitHub, and each org can connect a GitHub organization of its own.

Settings and running an install

• One Settings page that shows each person the panels for their role and org, and says who can change what.
• An install's sign-in notice, usage note, support address, and terms and privacy links, set in its gitops repo and in force within seconds.
• Slack: several workspaces per org, destinations for summary videos and announcements, a Product's own channels, and Share to Slack on any Change.
• A read-only MCP server for Claude Code: status, Products, runs, deployments, incidents, SLOs, DORA, Teams, people and the license.
• A code index with citing code tools for agents and people, and sign-in to the code tools through Infrared with no shared token.
• Encrypted backups to S3, Cloud Storage or Linode Object Storage, checked with a real write before saving, Back up now, and ir restore onto new servers.
• Upgrade with a one-line pull request to the gitops repo, under an upgrade guard; open tabs offer Reload after an upgrade.
• A license installs from Settings, ir, the API or the chart. During the open beta a banner counts down; after it, only new agent steps and promotions to production pause.
• Every install serves its own API reference at /api/docs. Errors are RFC 9457 problem documents, and a stale resourceVersion gets a 409 instead of a silent overwrite.

Install 0.1.0

0.1.0's chart and images are public, with no sign-in. Install it with helm:

helm install infrared oci://us-central1-docker.pkg.dev/darkshift-public/infrared/charts/infrared --version 0.1.0 \
  --namespace infrared --create-namespace --values infrared-values.yaml

The values file, the tokens and the setup wizard are in Install on GKE and Install on EKS. In darkshift's hosted environments there is nothing to install: see Hosted environments.

Upgrade to 0.1.0

An install running a 0.1 pre-release (0.1.0-rc.N) upgrades to 0.1.0 the way it takes any release in the track: through its gitops repo, with the upgrade guard watching. See Upgrades. Your Products, Changes and settings carry over; nothing needs migrating by hand.

Known issues

• Socials and Knowledge show on the rail. In 0.1.0, Socials appears on every rail, and Knowledge on a platform admin's. They are early previews these docs don't cover, and a 0.1 patch takes them off the rail.

Not in 0.1

These are built or being built, and come in a later track: running Infrared on a Mac, a knowledge base page, Socials and social posting, Front Office and Back Office, and daily and custom org summaries beside the weekly one. See the roadmap.