← All work
Case study

OdinCode

An event-driven autonomous coding pipeline. A Gmail push becomes a GitHub issue, an agent writes a plan and the code, and a pull request opens.

View source on GitHub →
Role
Creator
Company
Personal project
Stack
Gmail push · Pub/Sub · GitHub · Autonomous agent
5stages, email in to PR out
1written plan before any code
Cappedtool access and turns
The pipeline · email to pull request
Pipeline
  1. Gmail pushAn email arrives
  2. Pub/SubEvent-driven hand-off
  3. GitHub issueCreated automatically
  4. Autonomous agentCapped tools, capped turns
  5. Pull requestOpened for review

The problem

Turning a request into a reviewed change usually takes a person at every hand-off. OdinCode removes the hand-offs and keeps the review: the output is a pull request, not a push to main.

What I built

An event-driven path from inbox to repo

A Gmail push notification lands on Pub/Sub and becomes a GitHub issue automatically.

A plan before any code

Before the agent writes code, it writes a plan: scope, target files, approach and ordered tasks. The plan lives on the issue, where it can be read and challenged.

An agent that opens the PR

The autonomous coding agent works from the plan and opens a pull request for review.

The calls

Call 1 · Constraints

Cap the tools and the turns.

An autonomous agent with open-ended access is hard to trust. Limiting its tool access and its number of turns keeps its behaviour bounded.

Call 2 · Reliability

Idempotent dedup on every event.

Pub/Sub can deliver an event more than once, and retries happen. Deduplication means a retry never duplicates work.

Call 3 · Process

Plan first, then code.

A written plan makes the agent’s intent reviewable before a line is changed, and gives the pull request a reason to exist.