Commit approved work straight to a branch instead of opening a pull request, and attach
screenshots and files to a task so the AI can read them while it plans.
Direct commit
Each repository can now deliver work in one of two ways: open a pull request (the default), or commit directly to a branch you choose.
The branch must exist on GitHub when you save the setting. Switching back to pull requests clears it.
The approval email, the approvals inbox and chat messages say clearly when approving will commit directly, and to which branch.
If the target branch is ahead of your default branch, the approval request tells you by how many commits, because the plan was made from the default branch.
A direct commit happens only after validation passes, the same as a pull request.
Auto-approved tasks never commit directly. They open a pull request into the target branch instead, because nobody saw the direct-commit warning.
After a direct commit, Dualzo emails you and records it in the audit log. For tasks started from a GitHub issue, it also comments on the issue with a link to the commit.
If GitHub refuses the commit, the work stays on its own branch. You can take it over as a draft pull request or run it again.
Attachments
Attach up to 4 images (PNG, JPEG, GIF or WebP, up to 4 MB each) when you create a task. The AI looks at them while it writes the plan.
Attach up to 3 files (PDF, text, Markdown, CSV, JSON, YAML or XML, up to 10 MB each), such as specs, logs or sample data.
If the model you picked can't read a type of attachment, Dualzo tells you so you can switch models. It doesn't plan without them.
Open attached images, PDFs and text files in a preview on the task page. Text is shown as plain text and never run. Other file types download.
Attachments are kept for 365 days after a task finishes, and for as long as the task is still active.
Documentation
The documentation is now public and linked from the home page, so you can read it before you sign up.
Fixes
Fixed an error that could stop you from setting a new password after a password reset.
Credits spent on a run stopped by an AI provider error are now always refunded. Before, the refund could be skipped when a workspace's admins had email notifications turned off.
An AI provider's rate limit, quota, billing or low-balance errors are handled by the Dualzo team. Credits for the run are refunded, and you get an in-app notification instead of a failure email.
Fixed an error that could stop attachments from uploading.
Version 1.0
First release
The first production release of Dualzo. Connect a GitHub repository in any language and turn
issues or in-app tasks into reviewed plans. Once a person approves a plan, Dualzo runs it with
the AI model you pick, checks the result in a sandbox using your repository's own commands,
and opens a pull request. Every step is recorded.
Highlights
From GitHub issue to pull request, with a person approving the plan before any code is written.
Works with repositories in any language.
No pull request is opened while your own lint and test commands are failing.
Choose Claude, Codex or Gemini for each task.
Scheduled tasks, suggested tasks and automatic fixes for failing CI.
A complete audit trail for every step.
Tasks and planning
Start a task by adding a label to a GitHub issue (you choose the label for each repository), or create one in the app.
Two ways to start: review and approve the plan right away, or begin with a draft and refine it before planning.
Each plan lists ordered tasks with acceptance criteria, the files expected to change, the commands to run, rollback notes, and a risk level.
Dualzo works out the confidence score (0–100) and the effort level itself. The AI model does not score its own plan.
Pick Claude, Codex or Gemini for each task, and set a default model for each repository.
Starter templates for common work: performance, security and design.
Approval
Approve, Reject or Modify a plan by email or in the app. Approval links are signed, can be used only once, and expire.
Modify sends your instructions back to the planner and produces a new plan for approval.
An approvals inbox, and one approval for all of the AI's clarifying questions at once.
Approval requests and decisions can also be posted to Slack, Microsoft Teams or Google Chat.
Optional auto-approve for tasks you create in the app and for scheduled tasks.
Execution
Tasks run one at a time on their own branch, with a commit after each task. Only one execution runs on a repository at a time.
Pause a running execution and resume it later. It continues from the last finished task.
A live task view shows the agent's activity on one side and the code changes on the other.
A task that needs more capacity can be moved up to a higher effort level.
Validation sandbox
After each task, your repository's own install, lint, typecheck, test and build commands run in a throwaway container.
Network access is on only while dependencies install. The file system is read-only and resources are limited.
Encrypted environment variables per repository, for tests that need them.
If a check fails, the AI gets up to two attempts to fix it. If those fail, the task stops so a person can review it.
A pull request cannot be opened while validation is failing. This is enforced in code.
Pull requests and failure review
Each pull request comes with a description: a summary, the changes made in each task, validation results, a testing checklist, rollback steps and a link to the audit trail.
Dualzo tracks when a pull request is merged, closed or reopened.
When a task fails, a review page shows the plan, each task's status, the failing output and the full diff.
From there you can abandon it (the branch is deleted), edit the plan and run it again, or take over with a draft pull request marked as unvalidated.
Continuous AI
Scheduled tasks that run daily, weekly or monthly. You can pause, resume or delete them.
Suggested tasks based on the TODO and FIXME comments in your code (you turn this on per repository).
Automatic fix tasks when GitHub Actions fails on your default branch (you turn this on per repository).
Repository understanding
Works with any language. Built-in support for PHP, Node and TypeScript, Python, Java and other JVM languages, Go and Ruby, with a general mode for everything else.
Indexing only reads your code and never runs it. It re-checks only the files that changed, each time you push to your default branch.
Dualzo detects your validation commands and an admin confirms them before any task can run.
An AI-written summary of your repository's architecture, updated when your code changes.
Repository Knowledge: notes from your team that are included in every plan for that repository.
If a repository has no .gitignore, Dualzo offers to help you add one.
GitHub
Connect through a GitHub App and choose exactly which repositories Dualzo can see.
Connect several repositories and installations. Empty repositories can be given a first branch.
Every webhook is checked against its signature. Access tokens are short-lived and never written to logs.
Workspaces and team
Sign up with email and password (with email verification), or with Google or GitHub.
A workspace is created for you when you sign up, and you can switch between workspaces.
Invite teammates by email. Admins manage billing, members and repositories.
Each member chooses which email notifications they get. In-app notifications are kept for 7 days.
Every workspace's data is kept separate from every other workspace.
Audit trail
Every webhook, plan, approval, task, validation run and pull request is recorded in an audit log that can't be edited.
A workspace audit page with filters, plus a timeline for each execution.
Audit entries are kept for 90 days.
Plans and credits
One Team plan at $119/month with 5 seats included. AI model usage is included.
New workspaces get 300 free credits. No card and no trial clock.
Credits are charged based on what each run actually costs. You see an estimate before you approve and the actual amount after the run.
Payments are handled by Paddle, and invoices are available in billing settings.
Known limitations
Only GitHub is supported for now. GitLab and Bitbucket are not.
Repository understanding works the same way for every language. Deeper analysis for specific frameworks is planned.
A repository without a test command can run only in reduced validation mode, and every pull request it opens says so.
Ship AI-written code you can actually trust.
Team plan — $119/month, 5 seats included. AI model usage included.
