Runner turns the accounts you already use into a day already in order.
Connect GitHub once to give Runner the shape of your product, bring every meeting into My Day and keep every email in its familiar address and thread.
Your product, already taking shape
Connect GitHub and Runner builds a sourced first draft of what you sell, how your team works and how the workspace should feel. You begin with decisions, not data entry.
- Sync when you chooseYou press sync — Runner never watches your repository — and it records the commit it read beside every suggestion, so the source is always one click away.
- Start with decisions, not setupEvery field arrives as an editable proposal with its source beside it. Confirm what fits and keep moving.
Runner uses the structure and instructions in one named commit to shape the first draft. It reads dependency names without their versions and configuration keys without their values; a committed .env is never fetched, and no repository text reaches the model.
Why your code stays yours
A sync is a button an operator presses, not a watcher over your code. It records what it read, and it decides nothing — your product type is not set until you press Set product type. A model reorders and explains a shortlist the rules already made; anything else is discarded rather than used, and every run is stored with its model and cost. It writes back one thing: an issue on a record you approved. It never commits, branches, or opens a pull request.
fernhollow/orchard-billing
PublicmainSignals Runner found
- instruction files
- dependency names
- configuration keys
- an accent colour
Runner reads dependency names without their versions, configuration keys without their values, and the commit it read them at. A committed .env is never fetched, and no repository text ever reaches the model.
Your project
Suggestions ready to review
- Product typeStrong match
- Direct commerceFrom a dependency name
- Instructions in effect1 open conflict
- One file governs the root, another its own directoryFrom your instruction files
- Workspace accent
- Taken from your own stylesFrom a stylesheet
- Draft subject lineReady for your review
- What Orchard Billing does todayFrom your repository, at this commit
Your product begins to take shape
Runner suggests what you sell and shows where it got that. Your answer is saved only when you confirm it, and if your code says too little it says so and suggests nothing.
Your team's instructions come with it
Every sync maps each instruction file to the part of the repository it guides. When two clash, Runner shows you both instead of choosing — and what they say is never treated as permission.
The first campaign starts with context
Every draft names what it was drawn from and the commit it was read at. It is offered, never inserted: you choose what goes into your campaign and edit it in your voice.
It even feels like your product
Runner carries in the accent colour it finds when you connect, and never over a colour you already chose. If it cannot find one, it says it picked rather than claiming a match.
Walk in knowing where the day starts
Today's meetings arrive in My Day beside the next actions and work Runner already has moving. Open one view and know where your attention matters.
- Your day stays yoursEach person connects their own calendar, so everyone in the workspace opens a day arranged around their own meetings.
- Your calendar becomes useful contextRunner reads the relevant window from your primary calendar and puts each meeting beside the account, brief and next action it belongs to. It is a reader — nothing here creates, moves or cancels an event.
Calendar access is personal and read-only, and Runner gives each meeting the account context that helps you walk in prepared. Not connected yet? My Day shows no meetings rather than guessing, and a provider hiccup mid-session leaves you an empty list rather than an error.
Keep every message unmistakably yours
Write the campaign or reply in Runner. It leaves from the Gmail address your customers know, stays in the thread and appears in Sent. To them, it is simply you.
- Send from the account people knowCampaigns and replies leave from your Gmail address and appear in Sent with the rest of your work. Connecting Gmail to send asks for exactly that and nothing more — Runner never reads the mailbox on it.
- Bring replies back to the same recordA separate inbox connection lets Runner place replies beside the customer, campaign and next action they belong to.
Runner already keeps sending and inbox access as two independent connections. Google verification and the annual CASA review are part of the inbox rollout, with SOC 2 readiness on the roadmap.
Connect once. Start every day ahead.
Tell us what you already use and we will show you how Runner turns it into one working day. Access is by application while the product is young.
Apply for access