The project board that writes itself.

Your engineers work through AI coding sessions. Truestate records what those sessions built each day, by feature, with hours, and lets you talk back. Nobody moves a card.

Get early accessSee how it works
truestate.space/s/demo#today
Truestate
Team board
16 Sept 2026

Updated automatically by each engineer's sessions. Days close at midnight New York. Last activity 16 Sept 2026.

0
Hours
57
Tasks done
49
Commits
8
In motion
Today
16 Sept 2026
Aatir
Owner and engineer
0 h

0 updates across 0 stories, 49 commits, 0 hours.

49 commits
Technical details
Intervals (New York)
16 Sept 202618:4218:42
Commits
  • 8b515a1
  • 432edd9
  • d518774
  • aa2e4aa
  • e132030
  • a55561d
  • 1ec79f0
  • aaa112b
  • 34e2a52
  • af7d389
  • 530109a
  • 220d884
  • a7af4eb
  • e3ec9bc
  • 07e95c5
  • 640c69e
  • f7c5de3
  • 0b2f0b9
  • ad4a1da
  • aa9bb98
  • 1f56811
  • 90c0993
  • 39835c0
  • 713fd5f
  • e730d03
  • 511f997
  • 7334e31
  • 17ce126
  • fe33b14
  • 16bf313
  • 1ac194e
  • 37ff3ba
  • e69523e
  • 7017260
  • 37ce8ed
  • 05d23f7
  • 0d7af5d
  • e9e5512
  • e6aa6b4
  • 1dc2be6
  • 5ba402a
  • e4b1d99
  • 044c139
  • e3cde8b
  • 29ead0b
  • 14fb868
  • e34724c
  • 9806b5a
  • 7c6f6b3

Live: this is Truestate's own board, today.

Jira assumes a human updates the card.

On a team building with AI agents, the work happens while the human is away.

So the board decays, and the people who need it stop trusting it.

Three moments, no typing.

  1. session opens

    Day start

    When an engineer opens a coding session, Truestate creates the day, reads what people asked for, and tells the session where it left off.

    Day start for Alex, 2026-09-11 (Eastern). Created tracker/log/2026-09-11/alex.json.Last shipped: 2026-09-10: Done: Month picker; 4 commits (4 commits)Blocked: noneToday: Continue 012-billing-exports: CSV emitter | Start 012-billing-exports: PDF bundleAssigned to you on the board: 1 open task (#41 Add a search box to the invoice list). Open change requests: 0.Record task status in tracker/stories/ as you work. The day closes automatically at 00:05 Eastern; say "day end" to close early.
  2. session works

    Record as you go

    Every task the session starts, blocks, or finishes is written to the repository in the same commit as the code. Hours come from the session's own clock.

    Billing exports

    3 of 6 done. Working on: PDF bundle.

    In progress
    In progress
    • PDF bundle
    Blocked
    • None
    To do
    • Email the file when it is ready
    • Close
    Done (3)
  3. midnight

    The day closes itself

    At five past midnight the day is finalized for everyone, pushed, and the board is current before you open it.

    Alex
    Engineer
    5 h

    3 updates across 1 story, 3 commits, 5 hours.

    Billing exports
    • Done: CSV emitter
    • Started: PDF bundle
    • 3 commits: feat(exports): CSV emitter; feat(exports): PDF bundle scaffolding
    3 commits
    Next
    • 012-billing-exports: PDF bundle
    Technical details
    Intervals
    11 Sept 202609:0211:40
    11 Sept 202610:1014:02
    Commits
    • d161ee2
    • 9c4b0aa
    • 3e8f1c0

Open one page each morning.

truestate.space/s/demo
Truestate
Team board
16 Sept 2026

Updated automatically by each engineer's sessions. Days close at midnight New York. Last activity 16 Sept 2026.

0
Hours
57
Tasks done
49
Commits
8
In motion
Today
16 Sept 2026
Aatir
Owner and engineer
0 h

0 updates across 0 stories, 49 commits, 0 hours.

Plan
  • Pick the next open task from tracker/stories/ or the inbox
49 commits
Technical details
Intervals (New York)
16 Sept 202618:4218:42
Commits
  • 8b515a1
  • 432edd9
  • d518774
  • aa2e4aa
  • e132030
  • a55561d
  • 1ec79f0
  • aaa112b
  • 34e2a52
  • af7d389
  • 530109a
  • 220d884
  • a7af4eb
  • e3ec9bc
  • 07e95c5
  • 640c69e
  • f7c5de3
  • 0b2f0b9
  • ad4a1da
  • aa9bb98
  • 1f56811
  • 90c0993
  • 39835c0
  • 713fd5f
  • e730d03
  • 511f997
  • 7334e31
  • 17ce126
  • fe33b14
  • 16bf313
  • 1ac194e
  • 37ff3ba
  • e69523e
  • 7017260
  • 37ce8ed
  • 05d23f7
  • 0d7af5d
  • e9e5512
  • e6aa6b4
  • 1dc2be6
  • 5ba402a
  • e4b1d99
  • 044c139
  • e3cde8b
  • 29ead0b
  • 14fb868
  • e34724c
  • 9806b5a
  • 7c6f6b3

Live: this is Truestate's own board, today. Use the tabs, the day arrows, and the names.

  • Today. One card per person. What moved, what is blocked, hours with the intervals behind them.
  • Phases. The whole build as one bar. Click a phase for the features inside, in plain words.
  • Stories. One row per feature. Progress, what is being worked on, who owns it.
  • People. Every person's page. Their tasks, their features, their hours.

Your feedback becomes work. Without a meeting.

Pin a note on the live product

Circle the thing that is wrong. It becomes a task with a screenshot, on the right page, for the right person.

/portalPinCircleArrow
Approve deliverable
1
The approve button is easy to miss. Make it the main action on this page.
Saves a screenshot and becomes a task
Save note

Animation: a pin is placed on the approve button of the live product, a small form opens beside it with the note text, and the note is saved as a task with a screenshot.

Ask the repository

Type a question. An agent reads the codebase and answers in plain language within minutes. No engineer interrupted.

Ask the repository
Is the client portal ready for the Hartwell demo on Friday?
Nearly. Clients can sign in, see open work, and approve a deliverable as of today. Two things are not ready: comments on a deliverable are still to do, and storing signed approvals is blocked on a decision that is waiting for Maya. If that decision lands tomorrow, the demo can show the full approval flow.
Answered in 3 minutes

Answer decisions in one click

Decision papers arrive as cards with a recommendation. Agree, or say what you would rather. Answer ten in one sitting, on your phone.

Decide: where signed approvals are stored
  • Where should a signed approval be stored?

    Recommended: In our own database, with a copy of the PDF in object storage. Simplest to audit.

    AgreeSomething else
  • Should clients be able to download their signed approvals?

    Recommended: Yes, from the portal, as a PDF with the signature block.

    AgreeSomething else
1 of 2 answered. You can send some now and the rest later.Send

Hand out work

Assign a task to a person. Their next coding session picks it up as the day's work.

Give someone a task
Add a search box to the invoice list
Alex
Due 18 Sept 2026
Assign a task
Next morning in Alex's session: Assigned to you on the board: 1 open task

Hours you can defend.

Every hour is a timed interval from a real session, not a guess from commit times.

Engineers control their own clock.

Any correction is signed.

Alex
Engineer
5 h

3 updates across 1 story, 3 commits, 5 hours.

Billing exports
  • Done: CSV emitter
  • Started: PDF bundle
  • 3 commits: feat(exports): CSV emitter; feat(exports): PDF bundle scaffolding
3 commits
Next
  • 012-billing-exports: PDF bundle
Technical details
Intervals
11 Sept 202609:0211:40
11 Sept 202610:1014:02
Commits
  • d161ee2
  • 9c4b0aa
  • 3e8f1c0

Teams that do not bill by the hour turn hours off with one setting.

Built for the people who asked for the software.

Agencies and studios

Your client is the product owner. They see the daily record, leave notes on the live build, and sign off on hours without a status email.

Founders with a small team

The morning record replaces the standup. Ask replaces the interruption.

Teams already on git native trackers

Keep how your engineers work. Give the rest of the company a page.

$ npx @truestate/cli init$ npx @truestate/cli installDay start for Alex, 2026-09-11 (Eastern). Created tracker/log/2026-09-11/alex.json.Last shipped: 2026-09-10: Done: Month picker; 4 commits (4 commits)Blocked: noneToday: Continue 012-billing-exports: CSV emitter | Start 012-billing-exports: PDF bundleAssigned to you on the board: 1 open task (#41 Add a search box to the invoice list). Open change requests: 0.Record task status in tracker/stories/ as you work. The day closes automatically at 00:05 Eastern; say "day end" to close early.

For engineers

One command in the repo, one on your machine. Then never type status again. The record is JSON in your repository, validated by one schema, with git as the audit trail. Sessions on one machine coordinate with each other. Nothing ships to production from a scheduled job.

Works with Claude Code today. More runtimes coming.

Simple pricing. Early access is free.

Free

Indicative

One repository, up to three people

The CLI, the hosted board, tasks, Ask through your own workflow

$0

Team

Indicative

Up to ten people, several repositories

Live product notes, hosted answering, weekly digest

from $20 per person per month

Agency

Indicative

Client share links, hours reports, exports, unlimited repositories

Everything in Team, for studios building for clients

Talk to us

Prices are indicative during early access. Early access teams keep their rate for a year.

Questions

Where does my data live?

In your repository, as JSON files under a tracker folder, plus GitHub issues for tasks, notes, and questions. Truestate stores accounts and an audit log, nothing else. Git history is the audit trail and you can leave with everything at any time.

Which coding agents does it work with?

Claude Code today. The scripts need only a session start hook and a session end hook, so adapters for other runtimes are on the roadmap and arrive as those runtimes expose the same two events.

Do product owners need GitHub accounts?

No. Sign in is by email. A product owner opens the board, leaves notes, asks questions, and answers decisions without ever seeing GitHub.

Is this surveillance?

No. Hours come from a clock the engineer controls and can turn off, every figure has timestamps behind it, and any correction is signed. The point is a record the team owns, not a manager watching. Teams that do not want hours switch them off with one setting.

What if a session crashes or someone forgets to close a day?

The nightly close finalizes every day for everyone at five past midnight. An interval left open by a crashed session is closed at the last commit after it started, so it never claims time it cannot prove.

Can I self host?

Yes, a template is planned. The hosted board is the same app, so nothing about the record or the scripts changes between the two.

See what your build actually did today.

We will email you once, when your invite is ready.