Let Tuti handle your issues and PRs.
Tuti finds the pull requests that need you, reviews them and hands real fixes to your Claude Code or Codex.
See it work.
What Tuti does.
Step by step
- Labels new issues, marks duplicates and asks for missing details.
- Reviews the urgent PR with Claude Code. Remembers your team wants tests.
- Ships the release: notes, tag and a post in #team, with your OK.
- For a failing build or issue, runs Claude Code or Codex and opens the PR.
What you approve
- Merging, closing and deleting.
- A report in chat of what Tuti labeled, commented on and reviewed.
How it works.
Step 1: Sign in with GitHub
Choose which repos Tuti can see.
Step 2: Tell it what to do
“Which pull requests need me today?”
Step 3: Read the report
See what it reviewed and which PRs look safe.
Step 4: Hand off the fixes
Tuti runs your coding agent and sends you the PR.
Things you can say.
Copy one. Type it or say it.
Merging is your call.
Tuti only sees the repos you allow. Merging, pushing to a protected branch and deleting need your approval, and every action is in your history.
How Tuti keeps you safeCommon questions.
How does Tuti connect to GitHub?
With GitHub sign-in. You pick the repos and can revoke access anytime.
Can it run on a schedule?
Yes. Ask for a daily issue check or a Friday reminder about stale PRs.
Does it write code too?
Yes, through your own Claude Code or Codex. See the coding page.
