From commits to status update

Your day's commits, turned into a recap your manager can read in a minute.

Recap Agent reads your GitHub activity for the day, writes a concise, leadership-friendly summary, and sends it from your own mailbox, but only after you approve it.

Sign in with GitHub, Google or Microsoft.

To: engineering-manager@company.comAwaiting your confirmation
Daily Report: 2026-10-12

Summary

Implemented the billing API refresh and improved test coverage for the onboarding flow. Most of the work focused on stabilizing the latest release candidate.

Done

  • Added a safer invoice status sync and cleaned up error handling in the billing workflow.
  • Improved onboarding validation and expanded regression tests for account setup.

Notes

  • One larger refactor touched the payment integration and should be watched during deployment.

Built for the end-of-day update

Short, factual and written from what the commits actually show. No invented context, no filler.

Grouped by outcome
Related commits are grouped into themes and described by what changed, not by which file was touched. Merges, version bumps and lockfile churn are left out.
Personal and organization repos
Cover the repositories you own, the organizations you belong to, or both in one recap.
Any day, not just today
Generate a recap for a past date when you missed an update or need to catch up.
26 languages
Write the recap in your manager's language. Code identifiers, repo names and technical terms stay as they are.
Sent from your own mailbox
Connect Gmail or Outlook and recaps go out from your address, directly through Google or Microsoft.
Nothing leaves without your approval
Every recap waits as a draft until you preview and confirm it. Automatic sending is an explicit, per-schedule opt-in.

How it works

Four steps, and you stay in control of the last one.

  1. Step 1

    Connect your sources

    Authorize GitHub so commits can be read, and add your Groq API key for the summary.

  2. Step 2

    Generate or schedule

    Create a recap on demand, or pick the days, time and timezone it should be prepared.

  3. Step 3

    Review the draft

    Read the recap, choose the mailbox and the managers who receive it, and confirm.

  4. Step 4

    Send it

    The recap is sent from your connected mailbox and every attempt is logged.

Prefer the terminal?

The same recap generator ships as an open-source CLI. Run it with npx, authenticate with GitHub's device flow, and print the recap straight to your terminal.

terminal
npx recap-agent \ --repo-type "user,org" \ --language fr \ --day 2026-10-13 \ --groq-api-key $GROQ_API_KEY

Spend the last minutes of your day on code, not on the status update.

Sign in to get started