An AI coworker for GitHub, in Slack.

What Doozy can do in GitHub

Doozy works in the repositories you pick with the real git and gh, as the Doozy bot. It reads code, issues, pull requests and CI logs, pushes branches of its own and opens pull requests. It never pushes to main or anyone else's branch, and it never merges or approves.

• Clone and read the repositories you choose
• Read issues, pull requests, reviews and CI runs and their logs
• Push branches of its own, named doozy/…
• Open pull requests from its branches, and update them after review
• Open issues and label them
• Comment on pull requests and issues

Things people ask

In a thread, after @Doozy. It answers in that thread, with what it did.

• You

  @Doozy why is CI red on #418? Fix it on a branch and open a PR.

• You

  @Doozy add a `deleted_at` column to orders with a migration, and update the model. PR please.

• You

  @Doozy which PRs have waited more than two days for a review?

• You

  @Doozy triage today's new Sentry errors and open an issue for each one that's real.

How to connect GitHub

A few minutes, by whoever owns the workspace. No engineer needed.

1. 1

   On the Integrations page, click Install on GitHub. GitHub asks you to pick an account.

2. 2

   Choose the repositories Doozy may use. You can change the list any time.

3. 3

   Switch off any of its actions you don't want, and mention @Doozy with a task.

What stays off, and what's always true

Doozy works like a teammate, so it doesn't stop to ask. You decide what it can reach.

More in Security and AI & Data Use.

Works well with

One ask often crosses tools: a Sentry error becomes a GitHub pull request and a Linear issue. Doozy uses whichever it needs.

• SentryLook into errors, stack traces and releases.
• LinearFind, create and update issues, projects and cycles.
• VercelCheck deployments, builds and logs.
• SlackWhere Doozy works: mention it in a thread and the result comes back there.

Questions people ask before they connect GitHub

Can it merge, or push to main?

No. Those are refused on Doozy's side, not left to a setting. It pushes branches of its own and opens pull requests for a person to review and merge.

Whose name is on the commits?

The Doozy bot's, under the GitHub app installed on your organization, so every change it made is easy to find.

Can Doozy see our GitHub credentials?

No. Every task runs in its own isolated workspace, and credentials stay outside it: they're added to each call on its way out. Nothing it reads or writes there can expose a key.

Will it change things in GitHub without asking?

It works like a teammate, so it doesn't stop to ask, and you decide what it can reach. Tools that delete or overwrite start switched off, you can switch off any other, and every action it takes is on the audit log with who asked.

Who can connect it?

Owners and admins of your Doozy workspace. Members see what's connected and can't change it. Everyone in your Slack can ask Doozy once it's connected.

What does it cost?

Nothing extra. Every integration is included on every plan, and the 14-day trial needs no card.

Something else? Write to [email protected].