Operator
Runs one task from start to finish. It sends the work to the agents, puts a decision packet in front of you whenever the choice belongs to a person, and judges when the result can be delivered. It writes no code and pushes nothing by hand.
Agents do the work. Your team decides what ships.
Viberr is a self-hosted workspace for small engineering teams that deliver software with coding agents. Agents carry each task from its goal to a pull request, and engineers keep the flow, the review and the merge.
MIT licensed. Runs in one container with Docker Compose.
BoardEpicsReview queueControllerAgentsPolicyGitHubActivitySettings
Triage
VIB-166Manual re-scan & state reconciliationwaiting on a human
VIB-168Agent profile templates (eligible stages)waiting on a human
Ready
VIB-148Validate PAT scope before GitHub syncwaiting on a human
In Progress
VIB-151SACompress long-running task timelinesagent working
VIB-153Operator brevity guardrail for packetsagent working
VIB-160MYRehydrate specialist from canonical filewaiting on you
Review
VIB-142#318AKAttach execution workspace to task runtimewaiting on you
VIB-145#311Board card SSE revalidationagent working
Done
VIB-139#298EDSeparate human RBAC from agent capability policymerged
VIB-141#287MYTyped important-event schemamerged
Controller · Viberr Core
Every task gets an operator
Describe the work in a new task and the Operator starts at once. It scopes the goal, hands it to specialist agents and comes to you when the choice is yours.
Specialists
A Developer, a Reviewer, or any agent you define. On a board with a repository, the agent that delivers works in the task's own git checkout, and each supporting agent in a clone of its own. Its profile grants the MCP servers, knowledge bases and skills it may use, and it can be given a headless browser. Runs go through the official Claude and Codex SDKs.
Controller
An agent you talk to, one click away from a board or a task's page. Ask it about the instance or have it act for you. It works under your permissions and no others, and it can lay work out as epics.
Attach execution workspace to task runtimeLet the operator attach a single GitHub repo to a task, create the task-key branch, and reflect branch + PR state back into the canonical task file without treating GitHub as the source of truth.StageReviewStatusinput required
Completion reportfrom OperatorAccept completion, or send back for one fix?The developer specialist reports the workspace attach flow is implemented and the review PR is open. All requested files changed and validation evidence is attached — but the PAT used in the run is missing
pull_request:write, so PR status can't auto-sync after merge. Completion still requires explicit human acceptance.Changed9 files · +412 / −87Validationunit + integration green; 1 snapshot updatedBranchvib-142-attach-workspace · syncedFlagPAT scope missing pull_request:write
1Accept completionMark task done and merge the review PR. Human-authorized.2Request one editAsk the developer to widen PAT scope before acceptance.3Block on policyHold until Elif updates the project credential policy.Current state
StageReviewOwnerAKArda KayaRepoakin-ozer/viberr
Details
PriorityUrgentLabelsruntimegithub
Execution profile
OperatorDeveloperCodexReviewerClaude
Timeline
Arda Kaya@operator if the PAT scope is the only blocker, let's widen it rather than block the whole task.CodexImplementationCompletion reportImplemented repo attach, branch creation, and PR-sync projection. Validation green except one snapshot intentionally updated.unit/policy_gate_test6 passedintegration/pr_sync_test11 passedCodexImplementationOpened PR #318 from
vib-142-attach-workspace into main.Policy enginePolicy violation: active PAT is missing pull_request:write. Auto-sync after merge will fail.ClaudeReview & validationQuality flag: snapshot task_projection.json changed — confirm the new compact shape is intended before review.OperatorTransition request: move VIB-142 from In Progress to Review. Branch healthy, evidence attached.OperatorRe-engaged Claude (Reviewer) as reviewer; re-anchored on task.md before review.CodexImplementationBranch work complete. Handing back to operator for the review boundary.Arda KayaTook task ownership — owner is the human reviewer and acceptance authority for this task.BoardEpicsReview queueControllerAgentsPolicyGitHubActivitySettings
ControllerManaging the Viberr Core board with your own permissions.New conversation
Nothing asked yetAsk a question or ask for a change: boards, tasks, epics, users, resources, agents. Everything runs with your own permissions, and refusals say why.
What's waiting on me, and what's waiting on an agent?Which tasks have been open longest, and why?Draft a task this board is missing, but don't create it.
Ask the controller, or tell it what to do…Acts with your permissions · refusals say whySend
Conversations
Knowledge base
The server opens the pull request
On a software board every task has its own branch. Viberr's server pushes it and opens the review pull request, and an agent never does either. The Reviewer judges one revision, and its verdict stays tied to that revision. Moving the task to Done merges the pull request, and Viberr asks you to confirm first.
Results without a repository
A board can deliver results instead of code. The deliverable is then the files the agent saves on the task, such as an estimate or a report, and a person reviews and accepts them with no repository.
1Task branchOne per task
2Pull requestPushed and opened by the server
3ReviewVerdict bound to the revision
4DoneA person confirms the merge
People and agents answer to separate policies
Project roles decide what each person may do, and agent capabilities decide what each agent may do. Every boundary between two stages says whether the operator may cross it alone, needs a person's approval, or leaves the move to a person. Each action under governance is recorded twice: as a row in the audit log and as a typed event on the task's timeline.
Triageautothe operator may crossReadyapprovala person approves the operator's requestIn Progressapprovala person approves the operator's requestReviewhumana person decidesDone
Example boundaries. Each project sets its own.
What you get by hosting it yourself
Your work stays in plain files
Projects, tasks and epics are markdown files on your own disk. Open them, grep them or edit them by hand. When a file is malformed, Viberr shows a diagnostic you can read and does not crash.
Everyone brings their own agent account
Everyone links a Claude or Codex account of their own. The cost of a run goes to the owner of its task, and the cost of a controller turn to whoever asked. Viberr never stores a vendor sign-in token.
One process, no extra services
A single Node process serves the app, the stream of live updates and the background services. You run no database, cache or queue next to it.
What the first version leaves out
Viberr runs on a single node. It sends no email, so notifications stay in the app. The app speaks plain HTTP, so TLS has to end at a reverse proxy you put in front of it. Chromium is the only browser it declares support for.
Start with two commands
Have Docker installed, with Compose 2.24 or later. You write no .env file and create no volume.
git clone https://github.com/akin-ozer/viberr.git && cd viberrdocker compose upThen open http://localhost:3000 and sign in with the one-time password you will find printed in the log. Home lists the setup steps that remain: a GitHub connection, your own account, a Claude or Codex account and a first project. A board that delivers results needs no GitHub connection.