RoleEngineering

Internal automations without the infra

Every 'can you build a quick script' becomes an agent instead of a service you babysit. Dench runs the glue work — syncs, alerts, triage — on its own infrastructure.

#eng-automationEngineeringlive
DenchAgent8:12 AM

Sentry spike triaged

Error rate on /checkout hit 4.1% after this morning's deploy.

  • Linear ENG-482 filedDone
  • Suspect commit a3f21 flaggedDiff
  • On-call pagedSent
Open issue
Triaged 3 min after the alertDench
Built for

Engineers fielding everyone else's automation asks

  • Ops needs a sync, sales needs a report, you need a sprint
  • Cron jobs live on a laptop that sleeps
  • Every quick script becomes a service you maintain

What the Engineering agent actually ships.

  • Glue work as agents

    Describe the sync or alert in plain English — it runs on managed infra, no repo, no pager.

  • Production signals watched

    Sentry, PagerDuty, and CI monitored continuously — incidents triaged and filed before standup.

  • Tickets that write themselves

    Bug reports become Linear issues with logs, suspect commits, and repro steps attached.

How it works

From 'quick favor' to running automation.

  1. Step 01

    Describe it once

    'Sync new Stripe customers to the CRM and ping #sales.' That's the whole spec.

  2. Step 02

    Dench builds and runs it

    Managed infra with retries, logging, and alerting built in.

  3. Step 03

    Watch the first runs

    Every run logged and inspectable — approve before it goes hands-off.

  4. Step 04

    It maintains itself

    APIs change, schemas drift — the automation adapts and tells you what changed.

What it ships

What the Engineering agent actually ships.

  • Triage Sentry errors into Linear

    Logs, suspect commit, owner attached

  • Run scheduled jobs without cron infra

    Retries and failure alerts included

  • Sync data between internal systems

    Stripe ↔ CRM ↔ warehouse, no Zapier

  • Watch CI and flag flaky tests

    Weekly flake report with owners

  • Draft runbooks from real incidents

    Postmortems start 80% written

  • Answer 'how does X work' from code

    Grounded in the repo, not tribal memory

  • Build internal dashboards on request

    From the warehouse, no BI ticket

  • Keep API docs current with the code

    Drift flagged on every release

Integrations

Plugs into the stack you're on call for.

  • GitHub
  • Linear
  • Sentry
  • PagerDuty
  • Slack
  • Vercel
  • AWS
  • Stripe
  • Snowflake
  • Datadog

What Garry Tan, CEO of Y Combinator, says about Dench

Placing agent power on your own computer empowers every user and I’m so here for that. dench.com/claw
Garry Tan

Garry Tan

CEO of Y Combinator

600K+ followers

Questions you'd actually ask

Before you switch.

Only if you ask. By default it works around your codebase — automations, triage, docs — not in it. Repo access is opt-in and read-only first.

Stop maintaining what a sentence could run.

Describe one automation tonight. Retire one cron job tomorrow.

Try Dench