Portrait of Semih Mutlu

Semih Mutlu

I treat agents as infrastructure. Hermes, Herdr, and Cursor run on my Fedora machine, in the same room as the work.

Movies Wrapped is live. I did product work at Madlen. I study CET at Boğaziçi, and I am a movie enjoyer.

How I work

A day looks like this: Hermes is already on, cron, bots, desktop, memory. A job that needs code goes to Herdr. Herdr opens Cursor. Cursor runs OMP with one writable owner per path, then writes back.

  1. 01

    Hermes

    Always-on layer. Bots and the desktop app: cron, memory, the day-to-day operator.

  2. 02

    Herdr

    Workspace multiplexer. Panes, prompts, waits. Where the coding agents sit.

  3. 03

    Cursor

    Writes the code. From Herdr I orchestrate OMP sessions, one writable owner per path.

  1. 01 / INTAKE

    A job arrives

    A request enters through the always-on layer: memory, cron, bots, or the desktop app.

  2. 02 / ROUTE

    The workspace gets a lane

    Herdr gives the work a pane and an owner. OMP sessions do not share a writable path.

  3. 03 / VERIFY

    The result earns its receipt

    The agent runs the narrow check: tests, build, route smoke, or a read-back from the real system.

  4. 04 / ESCALATE

    Boundaries stay human

    Deploys, secrets, public copy, and irreversible git actions stop for a decision instead of guessing.

  • Autonomous

    Local verify-and-fix.

  • Draft-first

    Anything public: tweets, portfolio copy.

  • Escalate

    Deploy, secrets, irreversible git.

I left Claude Code and Codex as daily drivers because spreading one task across tools lost context. Autonomy with receipts, not autonomy on trust.

What gets written back

  • AGENTS.md

    Shared rules every agent reads before acting.

  • AgentMemory

    Decisions and rules in a filesystem that survives sessions.

  • Receipts

    A read-back from the real system, not a claim.

Every repeated mistake becomes a written rule. Shared AGENTS.md and AgentMemory are the filesystem that survives sessions. I do not get wiser; the files do.

Maker of Movies Wrapped

Movies Wrapped turns a Letterboxd export into a film-identity product: stats, share cards, a personal data story. It is live at movieswrapped.com.

Product work at Madlen

At Madlen I did product QA and UX across an AI EdTech platform. One concrete change: tool-specific waiting states instead of a generic spinner. The pattern stayed. I also reviewed sessions, reported issues, and retested fixes. AI-assisted analysis, human judgment on what shipped.

cc-lens

A local-first usage dashboard that reads Claude Code history on disk and never uploads private logs. Small, inspectable, privacy-bounded.

View cc-lens on GitHub →

Boğaziçi CET

Boğaziçi University, Computer Education and Educational Technology.

Letterboxd

I watch too many films and write them down. That habit is why Movies Wrapped exists.

letterboxd.com/semihmutsuz →