An AI CTO that turns requests into engineering work

Cabinet's CTO watches your code, builds, and problems, decides the cheapest safe fix, and writes the task so precisely it needs no follow-up. It writes briefs. Nightshift builds them.

What it does

  • Writes the brief

    Each task states the outcome in your words, the steps, three to six checks a reviewer can run, what is out of scope, and the number it should move.

  • Reads before it guesses

    It reads your GitHub changes, issues, and builds and the problems Cabinet recorded, and says what is known about the impact and what is not.

  • Weighs a fix, an undo, or a rebuild

    It compares doing nothing for 30 days, a small fix, and a rebuild in hours and review attention, and prefers the cheapest safe change.

  • Hands the work to Nightshift

    With Nightshift on the team, the CTO files the task and Nightshift prepares the change. An independent review checks it before you see it.

  • Judges build or buy

    It prices a build in hours and monthly dollars and names the point at which you should build it later instead.

  • Watches for trouble

    Where your Google Cloud is connected, Nightshift watches for problems and the CTO reads what it found.

Who it works with

The hires that report to the CTO:

  • Nightshift: An AI software engineer that turns your requests into reviewed changes in your GitHub repositories.
  • QA (coming later): Tests your flows before each release and reports what broke.

On the Owner plan, which has no CMO or CTO, the hires that report to them report to the CEO instead.

Use cases

  • Software company

    A bug report becomes a fix to review

    A support message goes to the CTO. It checks recent deploys, writes the task with its checks, and Nightshift prepares a change for you to review.

  • Shopify brand

    A slow product page

    The CTO asks Nightshift to read the theme repository, then proposes the smallest change and how to confirm it worked.

  • Restaurant or service business

    Fixing the website without an agency

    You say the menu link is broken. The CTO finds the right repository, writes the task, and reports back in the same thread.

  • Team inside a larger company

    A clear backlog

    A product team uses the CTO to turn scattered requests into tasks with acceptance checks, each tied to a number.

Connects to

  • GitHub

    Code changes, issues, and builds

  • Nightshift

    The engineer that builds and investigates

  • Google Analytics

    Events that confirm a change worked

  • Slack

    Where requests and answers happen

On its own, and what it asks first

On its own

  • Reads your repositories and recent builds through GitHub
  • Writes tasks with checks a reviewer can run
  • Asks Nightshift for a read-only look at a problem

Asks you first

  • Anything that merges. On the Trial and Owner plans nothing an agent writes merges without a person; on Team, low-risk changes can merge after review
  • Scope, spending, security, or data choices
  • Changes to your settings or who is on the team

When it shows up

  • Monday morning

    Weekly meeting, with the state of your code and builds

  • Whenever you ask

    Task briefs from any conversation

  • On the date set

    Follow-ups on engineering decisions

  • Optional

    Daily check-in on Team and Pro

Plans

The CTO comes with Trial, Team, and Pro. The Owner plan does not include the CTO role, but Nightshift is available there and reports to the CEO. In the local business setup, the CTO is off until you turn it on.

See pricing

Questions

What does an AI CTO do?

It handles the technical decisions: what to build, buy, or fix, and how to ask for it. In Cabinet it writes engineering tasks and hands them to Nightshift, which prepares the changes.

Can an AI CTO write code?

The CTO itself writes briefs, not code. Nightshift writes the code, in the repositories you choose, as changes that are checked first.

Is it safe to let it near my code?

Nightshift works through a GitHub App you install and only in the repositories you pick. Merges follow your plan's rules, and nothing risky merges without a person.

Do I need to be technical?

No. You describe the problem in your own words and the CTO turns it into a task. You review the change when it is ready.

Give it your website. Come back to a plan.

Questions: hello@agntwrk.com