You: Ship annual billing for Pro before the Dec 15 price change, with the docs and #launch ready.
Adapt for engineering
Give engineering work an agent of its own.
Build agents that investigate bugs, review code, and post team updates. Connect GitHub, your issue tracker, and Slack.
Annual billing for Pro
Code review
A first pass on code review. Findings beside the code.
An agent reads the diff, runs your checks in a sandbox, and leaves the decisions to your engineers.
eng-reviews
Review PR #2481 and QA the preview.
Read the diff across 12 files. Reviewed by severity, then ran a browser pass on the preview.
Nice. Leave the P1 as an inline comment on the PR.
Done. Added an inline comment on useResults.ts:84 with a suggested fix and linked the failing repro.
Browser QA
QA previews in a real browser. Check the flow users take.
Give an agent a preview URL and a scenario, and it returns screenshots and findings for an engineer.
eng-reviews
QA the login flow on the preview and screenshot every step.
Ran the login flow end to end in headless Chromium. Here are the results with screenshots attached.
Any regressions vs last week?
None. All 8 checks pass and load time held at 278ms—12ms faster than the previous deploy.
“Earlier I had to spend all this time fetching this data, or working Codex to it. Now I can do it in Slack, and everyone can see the data.”
Udhav GoenkaCTO, Orion SleepBug triage
Turn bug reports into tickets. With the evidence attached.
An agent tries to reproduce the report and drafts a ticket with the logs and code references.
bugs
Filters reset to default whenever results refetch. Repro on prod.
Reproduced it. Root cause is a stale closure in the results hook. Filing it now.
Perfect—add it to this sprint.
Done. Added ENG-1042 to the current sprint and linked the PR that introduced the regression.
Stay in flow
Engineering updates on a schedule. Pulled from your tools.
A daily digest of deploys, open pull requests, and failed checks, posted to your team channel.
engineering
Post a daily deploy summary every weekday at 9am.
Scheduled. I’ll pull from GitHub, Linear, and Slack and post the summary to #engineering each morning.
Add anything that broke in CI overnight.
Added. The digest now flags failed CI runs and links the offending commit and author.