Workflow
From request to merge, every step follows your settings
Pyloxa’s Workflow page lays the whole process out in five parts: who plans, which phases, who does which kind of work, how it’s checked and how it’s delivered. The brain only proposes plans and can’t change these settings. An agent saying it’s done doesn’t count either: your commands have to pass.
- 5 partsPlan, phases, assignment, checks, delivery
- 5Built-in templates, with a diff before you apply one
- 1Automatic fix when a check fails
- 0Merges or pushes without your OK
1. Plan: who’s the brain, and how much you let go
Pick one agent as the brain. It reads the project first, then splits the request into phases and tasks. The routing mode decides whether a plan waits for your approval.
- Suggest, then ask: the brain proposes the plan and who does what. You review it, reassign or edit tasks, and nothing starts until you approve.
- Follow settings only: starts by itself when every task matches a rule, and stops to ask you when one doesn’t.
- Auto within limitsPro: the brain picks from the agents you allow, plans start without waiting for approval, and only manual gates stop.
- When the brain can’t be used, Pro can hand planning to a backup brain. The brain never reviews work it did itself.
2. Phases: each one ends with a check
The brain lays out phases for each request, such as specification, implementation and testing. Before you approve a plan, you can reassign a task, edit its instructions, choose whether each phase waits for you when it’s done, or ask the brain to redraft.
- Use my stages: or set the stages yourself, up to five. For each one you decide who does it, whether it waits for your approval when done, and whether it can be skipped when a request doesn’t need it; the brain plans with only these stages. Free version included.
- Once a plan is approved, a progress bar on the plan card shows each phase’s status and which one you’re on; click a phase to jump to it.
- At the end of each phase, Pyloxa runs a gate on the integrated result. A failed gate is re-run once, then gets one fix task.
- A gate can move on by itself when it passes, or wait for your approval.
- The next phase gets a handoff package from the previous one: the results, the checks that passed and what to watch out for.
- Agent Teams (experimental)Pro: running agents can see the whole team’s tasks, report progress, and stop to ask you when they’re missing information.
3. Assignment: one table decides who does which kind of work
Each row of the assignment table is a kind of work and each column is an agent profile. Click a cell to make that agent primary, add it as a backup, don’t assign it, or open the advanced settings.
- Order of precedence: what you pick by hand on the plan card, then project rules, then global rules, then the default route. Within a level, the first rule that fully matches wins.
- Rules for one project or one phase live in the “Rule list (advanced)” and come before the table. Each row shows which rule decides it.
- When no rule matches, work goes to the default route or Pyloxa stops to ask you; you choose which.
| Kind of work | Claude Code | Codex |
|---|---|---|
| Frontend | Primary | Backup 1 |
| Backend | Backup 1 | Primary |
| Docs | Primary | — |
| Tests | — | Primary |
4. Checks: “done” from an agent doesn’t count
Pyloxa suggests verification commands such as npm run test. You approve each one and can try it in a temporary worktree first; the brain can only use commands you approved.
- When a task finishes, Pyloxa runs the acceptance commands in that task’s worktree and checks required files and the write scope. A task is accepted automatically only if it has at least one objective check, every check passes, and it doesn’t need a person to look.
- If a check fails, the same agent gets one automatic fix. Each task runs automatically at most 3 times.
- Cross-testing: another agent adds tests to finished work, and Pyloxa reruns your commands on the result. The tester can only change test files, and the original agent can’t change the tests it added. In the free version you click “Have another agent test it”; Pro does it automatically by your settings.
- Brain review: the brain checks finished work read-only, and its verdict is labeled as an AI judgment. Tasks that need your own review still wait for you.
- To see the whole check process once first, choose “Start the test drive” on the last step of the setup wizard: Pyloxa creates a sample project with a hidden bug and never touches your projects.
npm run test passed
Within the write scope
Cross-testing: Claude Code added 2 tests, all passing
5. Delivery: you decide what’s merged and pushed
Each task finishes in its own git worktree and branch, and accepted work is merged into the plan’s integration branch. Merging into your branch, pushing and opening a PR all wait for you, and Pyloxa never resolves conflicts on its own.
- Changes to
.github,.claude,.codex,CLAUDE.md,AGENTS.md,.mcp.jsonor the files that define your check commands are never accepted automatically or sent to brain review, and they’re listed again before you merge. - When you open a PR, you can attach a verification card: one table per phase showing who did the work, who cross-tested it, which commands Pyloxa ran and how each result was accepted. When a plan finishes, you can also open it under the plan card and copy the Markdown.
- The card’s closing line is off by default. When you turn it on, it says “Verified with Pyloxa” only if every result passed the commands Pyloxa ran and every gate passed, and “Verification record by Pyloxa” otherwise.
- If you prefer, a whole plan can share one worktree: tasks run in order, and later tasks see the changes accepted before them.
- Pyloxa never runs stash, reset or checkout on your working directory.
Add the points page
Start from a template, and undo it if you don’t like it
Before you apply a template, Pyloxa lists every setting it changes and who gets each kind of work; “Undo last template” takes you back. Pro settings in a template are skipped in the free version, and the diff says so.
| Template | What it does |
|---|---|
| Balanced (default) | Frontend to Claude Code, backend to Codex, each the other’s backup; suggest, then ask. |
| Quick fix | Follows your settings only, in one shared worktree, all on the brain’s profile. |
| Thorough reviewIncludes Pro settings | The brain reviews every task, and frontend and backend work is cross-tested. |
| Share the quotaIncludes Pro settings | Spreads each kind of work across Claude Code and Codex, with automatic fallback when quota runs out. |
| Spec first | Write the spec and wait for your approval, then implement and test; testing can be skipped when a request doesn’t need it. |
My workflows: one for each projectPro
Once it’s set up, choose “Save as my workflow” (up to 20), then pick a workflow for each project: spec first for the API, straight edits for a small tool. Projects without one use the global settings, and rules you set for a project still come first.
- Describe a workflow: say how you want to work and the brain drafts a workflow, shown as a diff first. You choose whether to apply it globally, save it as one of your workflows, or edit the description and draft again. The brain can’t invent agents, and anything it can’t do is written in the notes.
- Version history: every save keeps a version, up to 10 per workflow. Compare any two, or restore one; restoring keeps a version of what you had before.
- Your workflows can go into a dispatch pack to share, and they travel to a new PC with your exported settings. Version history and which workflow each project uses stay behind.
- If you go back to the free version, your workflows are kept and projects use the global settings until you’re on Pro again.
Free and Pro
The free version covers the whole flow. Pro takes over what you would otherwise do by hand.
| Free | Pro | |
|---|---|---|
| Routing | Suggest, then ask; follow settings only | Adds auto within limits |
| Settings | Workflow page, assignment table, rule list, five templates, your own stages | Same as free |
| My workflows | — | Save several workflows, one per project, compare and restore versions, describe a workflow in one sentence |
| Checks | Verification commands, phase gates, brain review, cross-testing on request | Adds automatic cross-testing, with failures sent back for a fix |
| Running | One project working at a time | Several projects at once; Agent Teams (experimental) |
| Delivery | Integration branch, merge, push, PR, verification card | Same as free |
Questions
How does Pyloxa decide a task is really done?
By the verification commands you approved. When a task finishes, Pyloxa runs the acceptance commands in that task’s worktree and checks required files and the write scope. Only a task with at least one objective check, where every check passes and no person needs to look, is accepted automatically; otherwise the same agent gets one automatic fix. A check that didn’t run, was skipped or failed is never marked as passed.
Can the cross-tester change my code?
No. The tester can only write test files (such as *.test.*, *.spec.*, test/, tests/ and __tests__/), and the original agent can’t change the tests it adds. The tester can’t be the profile that did the work, and Gemini CLI can’t be a tester.
Does Pyloxa merge or push on its own?
No. Accepted work is merged only into the plan’s own integration branch. Merging into your branch, pushing and opening a PR are always your call, and conflicts are never resolved automatically. Changes to files that steer agents and automation, such as .github, CLAUDE.md and AGENTS.md, are never accepted automatically.
Who decides how many phases a plan has?
By default the brain decides for each request, and before you approve the plan you can reassign tasks, edit instructions, choose whether each phase waits for you when it’s done, or ask the brain to redraft. You can also switch the Workflow page to “Use my stages”: up to five, and you decide who does each one, whether it waits for your approval and whether it can be skipped. That’s in the free version too.
Is the Workflow page part of the free version?
Yes. The Workflow page, assignment table, rule list, templates, your own stages, verification commands, gates, brain review, cross-testing on request and verification cards are all free. Pro adds my workflows, describe a workflow, auto within limits, automatic cross-testing, several projects at once and Agent Teams (experimental).
Can different projects use different workflows?
Yes, with Pro. Save your current settings as one of your workflows and pick one for each project; projects without one use the global settings. Each workflow keeps up to 10 versions you can compare and restore.
Try it on your own project
Pyloxa is a free Windows app. It runs the Claude Code and Codex CLIs you already use, on your own subscriptions or API keys.