OSAgentOSAgent

Morning read

Start the day knowing what actually needs you.

One read. What changed since you last looked, what is stuck, and the one thing waiting on a decision only you can make. Every line opens into the evidence underneath it.

Don't reconstruct the week. Read it.

The shape of it

Three counts, then the detail — only if you want it.

Example

Open any line below. The rows on this page work the same way they do in the product.

osagent · morning read

Monday · 9:00 AM

4 sources connected
things changed
3things changed
blocked
2blocked
decision needs you
1decision needs you
PAY-3Payments retry moved from in review to blocked.Changed2m ago2 sources

The pull request that carried it went red on Wednesday and has had no commits since.

  • github · PR #1284Pipeline failing on the contract test since Wed 09:41.
  • slack · #billing“Retry is blocked on the payments-webhook contract.”

confidence · high

ONB-7Onboarding gained a requirement after the plan was set.Changed1h ago2 sources

A scope change was agreed in a meeting and written into the spec, after the estimate it invalidates.

  • meeting · product sync“We're adding SSO to onboarding before launch.”
  • doc · onboarding specRequirement added Wed 14:20. Estimate unchanged since Mon.

confidence · high

REL-2Release branch has had no deployment this cycle.Changed3h ago1 source

Every previous cycle on this project deployed at least two days before the date.

  • github · release branchLast deployment recorded 11 days ago.

confidence · high

REL-2Rollout coordination has no owner.Blocked18m ago2 sources

It was raised twice in Slack and never picked up. No person is attached to it in the record.

  • slack · #rollout“Who's taking rollout coordination?” — no reply, twice.
  • workspace memoryNo owner resolved. OSAgent is not guessing one.

confidence · needs review

PAY-3Contract change has been waiting on review for five days.Blocked4h ago1 source

Two other pieces of work name it as their dependency, so the wait is not local to one branch.

  • github · PR #1271Review requested Fri. No review submitted since.

confidence · high

PRC-1Two live answers exist for enterprise pricing.Needs a decisionyesterday2 sources

A later conversation contradicts an earlier written decision, and the earlier one was never retired.

  • doc · pricing v2Per-seat, with a floor. Marked decided three weeks ago.
  • slack · #gtm“We agreed we're going platform fee + usage.” Last Thursday.

confidence · needs review

the rail is confidence, the chip is status — they never mean the same thing

Instead of

The three things a morning read replaces.

Not fourteen dashboards

A dashboard shows you a number and leaves the interpretation to you. This says what changed and why it matters, in a sentence.

Not sixty unread messages

The messages are the raw material, not the summary. Reading them all is the work OSAgent already did.

Not a forty-five minute status meeting

A meeting whose only output is context is a meeting that a shared record makes unnecessary.

The point is not that the digest is short. It is that the long version is one click away, and you get to decide whether you need it.

How it works

Assembled from what already happened.

  1. Nobody writes it

    There is no form, no standup bot, no end-of-day update. The digest is built from Slack, GitHub, docs and meeting transcripts your team already produced.

  2. Only what moved

    A line appears because something changed since you last looked — not because a project exists.

  3. Ranked by what needs a person

    Decisions first, then blockers, then changes. A day where nothing needs you is a short read, and that is the correct outcome.

  4. Openable to the source

    Every line carries its evidence, and every piece of evidence names the tool it came from.

Who this is for

Anyone whose first hour is spent finding out.

  • FoundersYou are across five functions. This is the version that fits in a coffee.
  • Engineering leadersKnow the blocker before the standup, not during it.
  • Product leadersSee the scope change on the day it happened, not at the review.
  • Chiefs of staffThe weekly summary is already assembled, with its sources attached.

Why you can trust it

A summary you can audit is a different object.

The reason to trust a digest is not that it is well written. It is that you can open any line and find out whether it is true.

Cited, or absent

A line without evidence behind it does not make the digest. Silence in the record is reported as silence, never filled in.

It never modifies your work

OSAgent reads the tools your team uses to build the digest. OSAgent never modifies your work — no branches, review comments, ticket changes, status changes, or source-data edits or deletes.

Yours, not your team's

By default the digest appears in your OSAgent workspace and is not posted into a channel. An admin can enable delivery, and then it is sent only to destinations your team has explicitly authorized — never over anyone's head.

Proposals stay proposals

The decision line is a prompt for you, not an action taken. Nothing moves until a person with the authority accepts it.

What's next

See what your Monday would have said.

OSAgent is in a private pilot. In a walkthrough we read a week you already lived through — including the lines we would have left out, and why.