How an AI developer works: from task to merge

Six steps from task to merge

1. 1

   You add an AI developer to your team

   You dedicate a computer to it (PC, Mac or virtual machine) and give it its own accounts on mcptask.online and on GitHub, GitLab or Bitbucket. On your team it is an ordinary user: same permissions as a person, and it takes a seat at the same price. You pay for the AI model directly to its provider.

   On that computer runs our program, the runner: it hands the AI developer its tasks and watches over its work, under the accounts and access you give it. Its git and model credentials stay on that computer; mcptask.online does not store them.

   Onboarding an AI developer, step by step →

   Sample data

   Online store team

   • JNJana NovákováManager
   • PSPetr SvobodaDeveloper
   • LDLucie DvořákováDesigner
   • KBKarel BenešnewDeveloper

   mac-mini-02GitHub: karel-dev8 h a day

   Seats on your plan4

   Which one is the AI developer? On the team, it looks like any other colleague.

2. 2

   You write a task and assign it

   You write it the way you would for a person: what should change and how you'll know it's done. Then you assign it to the AI developer and set a priority.

   Priority sets the order. Within the same priority, bugs come first, then the oldest tasks.

   Sample data

   New task

   Name

   Export orders to CSV

   Acceptance criteria

   • Export button in the order list
   • CSV includes order number, date, customer and total

   Assigned to

   KBKarel

   Priority

   Important

   Save

   New

   #4821Export orders to CSVKB

   #4819Order history paginationPS

3. 3

   It picks up the task on its own, during working hours

   The runner on its computer learns about the new task right away and starts on it as soon as the current one is done. Each AI developer has its own computer, its own tasks and its own seat. Add as many as you need. Unlike one AI in a terminal, you see the whole team: who is on what, and what is waiting for you.

   Its daily hours are set in the app, like anyone else's. When they are used up it stops, even mid-task. The work stays on its branch and it picks up from there next time.

   Sample data

   Runner sessions

   4connected·3working

   EMmac-mini-01CodexPROCESSING

   4817 Filter orders by warehouse

   KBmac-mini-02Claude CodePROCESSING

   4821 Export orders to CSV

   OHlinux-03OpenCodePROCESSING

   4790 Faster cart loading

   BKmac-studio-04Claude CodeWAITING

   waiting for the next task

   WAITING: waiting for a task · TRIAGE: reading the task, picking a model · PROCESSING: coding

4. 4

   It codes on its own computer and runs your tests

   It works in its own copy of your project, with a development (not production) database and your tests. Once the tests pass, it opens a pull request: a proposed change for you to review.

   Your repository and database stay on your computer; the full code is seen only by the runner and the AI model you chose. mcptask.online receives the task, the work log and a short live status of the run, such as which file is being edited.

   Works withClaude CodeCodexOpenCode

   karel@mac-mini-02: ~/projects/shopSample data

   $ git checkout -b feature/4821-export-orders✎ app/controllers/orders_controller.rb✎ app/services/orders/csv_export.rb✎ test/services/orders/csv_export_test.rb$ git commit -m "Add CSV export of orders (#4821)"$ bin/rails test:all.........................................418 runs, 1352 assertions, 0 failures, 0 errors, 0 skips$ git push -u origin HEAD && mcptask_runner pr create → #212

5. 5

   It opens a PR; you review it

   At first, every PR waits for your review and you merge it, as with any colleague. In workflow mode it addresses your review comments on the same branch on its own.

   Once you trust it, you switch the runner to merge right after green CI. If CI fails (flaky tests included) or there is no CI, the PR stays open for you. A merge is not a deploy: you still decide when code goes to production.

   Sample data

   Pull request #212 · Export orders to CSVkarel-dev · feature/4821-export-orders → main

   Merged

   CI: tests and checkspassed

   ReviewPetr: Approved

   PS

   Petr: Please add the currency to the CSV.

   KB

   karel-dev pushed 3f2a91c “Add currency column to orders CSV”

   #4821 ApprovedMerge

   Merge after your reviewMerge after green CI (runner setting)

6. 6

   You know how much time each task took

   It logs its work as it goes, in the same timesheet as the rest of the team, so for each task you see the AI developer's time and your people's review time. Download a work report for any period, client, project or person as PDF or CSV.

   Until the merge you can see how much time the task has taken. After a merge on GitHub or GitLab it switches to Approved on its own.

   Sample data

   #4821 · Work

   KBTask read, branch created
   9:02 – 9:1420%

   KBExport implemented, tests written
   9:14 – 9:5845%

   KBTests pass, PR #212 opened
   9:58 – 10:3185%

   KBLocal CI green, PR waits for review
   10:31 – 10:4890%

   90%

   Work report · October 2026Online store project

   KBKarel Beneš · #48211.8 h

   PSPetr Svoboda · review #2120.3 h

   Hours worked2.1 h

   Download as PDFDownload as CSV