What the Bot does
- Open Linear, GitHub, or Jira for the issue you name.
- Reproduce on the computer. Screenshot. Write steps.
- Draft a fixture. Do not patch production.
Engineering · A computer, a ticket, a fixture
Bug reproduction
Reproduce the bug from the report. Write steps, expected vs actual, and a minimal fixture. Do not change production.
The ticket says 'doesn't work'. Someone has to actually click it. That someone can be a Bot with a computer.
Never without you
- Merge or deploy
- Change production
- Close the issue
First message
Talk first. The first message is a real task — not a template to configure.
Bug reproduction
Reproduce this bug. Steps, expected vs actual, screenshot. Do not change production.
Message Bug reproduction
Tools this job uses
Connect them when the Bot hits a wall. Nothing goes live until you say so.
FAQ
Why not just Copilot?
Copilot edits code. This Bot has a computer and the ticket. It clicks the product, then writes the fixture.
Also hire
Other jobs
Hire for the work. Each Bot is a person in the sidebar.
GitHub and Linear, in English
Shipping updates
What shipped, what is stuck, what needs you. No merge, no deploy.
What changed. What needs you.
Chief of staff
A source-linked digest of Slack, inbox, calendar, and notes — only the items that map to this week’s priorities. Does not send. Does not move meetings.
Tickets to action
Support triage
Cluster bugs and feedback from Zendesk, Intercom, or Linear. Draft replies and issue notes. Do not close tickets without you.
Briefs and change lists, not live clicks
Ad campaign management
Build campaign briefs, creative variants, and a change checklist from performance. Live edits wait for you.
Hire the first one
Meet your first Bot.
Name, optional job, how it should work. Open the thread. The first message is a real task.
Request an invite