NocoBase Studio

Agents keep the work moving. Your team stays in control.

NocoBase Studio is the governance platform for people and agents building software together. It brings Claude Code, Codex, and OpenCode into one agent team that moves issues forward on its own. Progress is clear at a glance, and people make the key decisions.

Try It Online View Editions & Pricing

Runs on your own serversWorks with Claude Code, Codex, and dozens of other coding toolsAvailable in the commercial editions

My issuesL

My issues

Search issues…All projectsAny executorNew issueC
Needs you2
Customer tiers & owner-change approval
CRM-135·Waiting for your sign-off
Overnight ticket routing
SUP-88·Question: which shift gets them?
In progress14
Deal stage board
CRM-144·Codex building
Refund ticket SLA alerts
SUP-91·Claude Code testing
Probation review reminders
HR-45·Claude Code reviewing
Done41
JKMoveSStarEnterOpen/Search
3 / 16CRM-144·NocoCRMIn progressStarAsk agent
Deal stage board
OwnerLLeo WalkerExecutorCCoordinatorETATonight 23:40
PlanStep 3 of 5 · 2 agents in parallel
Stage rules and 6 acceptance scenariosCCClaude Code
Stage field and data migrationCXCodex
Drag-and-drop and stage permissions7 files changedCXCodex
Tests for the 6 scenarios31 / 38 passingCCClaude Code
Code review by another vendor’s modelCCClaude Code
PR #2212 branchesPreview · crm-144
ActivityDescriptionSubtasks 5Code & deploysRuns 9
C
Coordinator gave steps 2–3 to Codex and step 4 to Claude Code in parallel
CX
Codex is building drag-and-drop; 31 / 38 tests passing

Agent team

An agent team that keeps work moving.

Studio connects agents across many machines and schedules them centrally. They move many projects and issues forward in parallel, around the clock.

NocoBaseStudioRuntimesL

Runtimes

23:40 · The team is offline. Agents on 9 runtimes are still moving 24 issues across 4 projects

On around the clock
NameStatusTools · running / limit
Server 01Team · linuxOnline 4/4
Codex 2/2Claude Code 2/2
Server 02Team · linuxOnline 4/4
Claude Code 2/2OpenCode 2/2
Server 03Team · linuxOnline 3/4
Codex 2/2Claude Code 1/2
Leo’s MacPersonal · macOSOnline 2/2
Claude Code 1/1Codex 1/1
Maya’s workstationPersonal · linuxOffline · 3h ago
Claude Code 0/1
4 more runtimes · 11 issues running
CCoordinatorAssigns the work
CRM-144Step 4: write tests

CCClaude Code on Server 02

SUP-91Fix review comments

CXCodex on Server 01

HR-45Code review by another model

CCClaude Code on Server 04

ITAM-12Asset audit import

CXCodex on Server 03

CRM-147Solution design

OCOpenCode on Server 02

Agents on many machines

Connect Claude Code, Codex, and other agents on your team’s computers and servers, and Studio finds the coding tools and models signed in there. Say what each agent is good at, enable it, and it joins the agent team.

A coordinator assigns the work

A coordinator agent assigns design, development, testing, and review by what each agent is good at. It writes no code and merges nothing; a person always accepts the work.

Many issues at once

Each issue has its own branch, and every run works in a separate worktree, so many issues move at once without colliding. Add machines to run more in parallel.

My sessions

In Studio, talk with the agent on your own computer to discuss and clarify requests, record issues, and follow their progress. Once an issue starts, the coordinator agent puts the agent team to work.

Progress

Progress at a glance.

Project progress, issue activity, agent workload, and model usage are all clearly visible. You can see at a glance where every issue stands and what comes next.

NocoBaseStudioDashboardL

Dashboard

How delivery goes, how the agents perform, and what is stuck.

7 days30 days90 days
Issues completed168vs 137 before
Median cycle time1.6 daysvs 2.3 days before
Completed by agents93%vs 88% before
Cost per issue$3.90vs $4.30 before
Model usageTokens used by agent runs, and the estimated cost at current prices
ModelRunsInputOutputEst. cost
CCClaude · Opus 5.541284.1M6.2M$296
CXCodex · GPT-5.5538109.6M7.9M$258
CCClaude · Sonnet 5.536648.7M3.4M$85
OCOpenCode · DeepSeek V420135.2M2.6M$13
Total1,517277.6M20.1M$652
NocoBaseStudioMy issuesSUP-91L

Refund ticket SLA alerts

OwnerAAva ClarkeExecutorCCoordinatorProjectSupport desk
In progress
Now

Claude Code is writing tests for the 4 timeout scenarios

Running for 12 minutes · on Server 03

Next: once the tests pass, a different model reviews the code, then it goes to Ava for sign-off.

PlanStep 3 of 5
SLA rules and 4 timeout scenariosCCClaude Code
Ticket fields and timeout alertsCXCodex
Tests for the 4 timeout scenarios12 / 16 passingCCClaude Code
Code review by a different modelCCClaude Code
Sign-offAAva
C
Coordinator gave step 3 to Claude Code
CX
Codex finished step 2 and opened PR #318

Project progress

Each project’s progress, plus issues completed, cycle time, the share completed by agents, and cost per issue, compared with the period before.

Issue activity

Every issue shows at the top which step it is on, which agent is working on it, and what comes next.

Agent workload and model usage

See which issues the agents on each machine are working on, and how many tokens each model has used at what cost.

Decisions

Decisions backed by evidence.

When a decision needs a person, agents attach detailed reports, checklists, screenshots, and recommendations, so even business experts who don’t code can make the call.

NocoBaseStudioMy issuesCRM-135L

Customer tiers & owner-change approval

OwnerLLeo Walker · Sales directorExecutorCCoordinator
Waiting for your sign-off
Delivery reportTests 35/35 · code review passed

Customers are tiered by the last 12 months of contract value: A from $1M, B from $200k, recalculated on the 1st. Changing a Tier A owner needs the sales manager’s approval.

Acceptance checklist6 / 6 passed
$1M lands in Tier AScreenshot
$999k lands in Tier BScreenshot
Tiers recalculate on the 1st
Changing a Tier A owner asks for approvalScreenshot
The new owner is told once approved
Reps without access never see the buttonScreenshot
Screenshots4 images
Customers
East Energy¥ 1,050,000A
Qiming Health¥ 999,000B
Voyage Logistics¥ 386,000B
Scenarios 1–2 · the ¥1M line
Owner change needs approvalTier A · East Energy
CancelSubmit
Scenario 4 · approval asked
CAgent’s recommendation

Approve. After recalculation Tier A grows from 212 to 236 customers; the list is attached.

ApproveSend back

Report and checklist

Every hand-over says what changed and how it was verified, with an acceptance checklist item by item.

Screenshots and previews

Each scenario comes with screenshots, and when you want to try it yourself, a separate preview environment is ready.

Accept or send back

With the evidence in hand, accept the work or send it back. Say why, and the agents carry on from there.

Business experts

Business experts who don’t code can make the call.

Business experts describe what they need in plain words, answer the agents’ questions, and check the result in a preview with real data. Environments, branches, tests, and releases are handled by the agents and Studio.

Tech leads set the rules and approve releases. Business experts own the requirements and the sign-off.

Supplier tiering · PUR-23

Owner: Ethan Cole, procurement lead · no code, from request to release

Live
Ethan doesAgents and Studio handle
AskDescribes the tiering rules in plain wordsAgents turn them into rules, test scenarios, and issues
BuildAnswers 2 questions: score weights, exempt suppliersCode, pull request, automated tests and checks
VerifyWalks real suppliers through the previewA separate preview, with checklist and screenshots
ReleasePicks the release timeThe tech lead approves; it can roll back to the last release

Before work reaches a person, Studio coordinates checks and reviews.

Every change follows the same path. It reaches a person only after its tests and code review pass, and reaches production only after a person approves. If something goes wrong, roll it back.

  1. 1

    Branch and worktree

    Each issue has its own branch, and every run works in a separate worktree. Pull requests from that branch link to the issue.

  2. 2

    Test and review

    CI runs checks and tests, then a different model reviews the code, from another vendor when one is available.

  3. 3

    Preview

    When needed, a pull request gets its own preview environment for a person to try and sign off.

  4. 4

    Merge and release

    Merged after sign-off, and the issue is done once all its pull requests merge. Releases to production need a person’s approval.

  5. 5

    Roll back

    If anything breaks, go back to the last release.

Know-how

Know-how stays with the team.

Requirement context, business documents, and lessons learned are scattered across chat sessions on different computers. When people or agents change, they are hard to find. Studio captures methods and experience in skills, the knowledge base, and project memory, so a new person or agent can pick up where the last one left off.

NocoBaseStudioProjectsNocoCRM customL
SkillsHow the work is done
studio-developmentDevelopment rulesv12 · Global
studio-reviewReview rulesv7 · Global
studio-testingTesting rulesv5 · Global
crm-fieldsCRM fields & namingv3 · This project

Every run carries them: global → project → workdir

Knowledge baseBusiness material
Discount approval rulesVerified
Customer tier definitionsv4
Sales processv2
Contract template.pdfFile
L

Leo uploaded 2026 pricing policy.pdfText extracted, ready for agents to read

Project memoryWhat agents learned

Run the migration before tests, or the stage field is empty and 2 of 6 scenarios fail.

CXCodex · CRM-144Project

Strip +86 from phone numbers before import, or dedupe misses them.

CCClaude Code · CRM-152Project

Check dark mode in every review; the customer has flagged contrast twice.

CCClaude Code · CRM-139Feedback

Kept in the repo’s .nb-studio/memory and read before each issue

CRM-160 changes handsMMayaCXCodexArrives with 4 skills, 14 documents and 9 memories. Nothing to re-explain

Skills

Skills hold how work gets done. Write down how you clarify, build, review, and release, at the global, project, or working-directory level, and every run carries them.

Knowledge base

The knowledge base holds business documents. Requirements, business rules, contract templates, and other material are written or uploaded by people, and agents read them as they work.

Project memory

Project memory holds what agents learn on their own. It lives in the project’s repository, is reviewed and merged with each issue’s pull request, and is read before the next issue starts.

Open source and self-hosting

Self-hosted. Your code and data belong to you.

Core and Solution are free and open source. Studio is available in the commercial editions.

Self-hosted

Core, Solution, and Studio all run on your own servers. Your code and data belong to you.

Your choice of models and agents

No vendor lock-in. Works with Claude Code, Codex, and other coding tools, and with a wide range of models.

Apps run independently

Once released, your business apps run on their own. Day-to-day business requests never go through Studio.

View Editions & PricingThe code agents write is built on NocoBase Core