A task
On a task's page the dock is anchored to that task. Every turn opens with a fresh read of the task's own file, beside its stage, its owner, the agents engaged on it, its branch and pull request, and whatever it is waiting on.
Ask where you work. It acts with your permissions.
The controller is the one agent every signed-in person on a Viberr instance can talk to. It answers questions about your projects, carries out what you ask within exactly your own permissions, and plans work into epics.
On a board it offers to ask
- 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.
Get startedRead the controller docs
It runs on your own Claude account. It has no tool to merge or to accept.
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
ControllerViberr Core
Knows the Viberr Core board: stages, members, open tasks, epics · acts with your permissionsAsk about the Viberr Core board or say what to do on it: tasks, epics, agents.
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 here…Acts with your permissionsSend
It starts from the page you are on
Open the dock and the controller is already bound to what you are looking at. Each turn begins with a read of that place, which the server takes as the turn starts.
A board
On a project's other views the dock is bound to the board. It reads the stages and the boundaries between them, the members, the open tasks and the open epics with their progress. The project also has a Controller page of its own, fourth in the rail, and that page has no dock.
The instance
On the other pages that carry the dock it speaks for the whole instance: the projects you can see, your role in each and what is happening there. The instance has a Controller page of its own too, at /controller.
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
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
Home › ControllerAKControllerManaging this instance 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 blocked across every project I can see?What did agent runs cost this week, by project?Show me the agent profiles on this instance and what each can do.
Ask the controller, or tell it what to do…Acts with your permissions · refusals say whySend
Conversations
It can do what you can, and no more
The controller has no authority of its own. A change it makes on a board passes the same role checks as the page you would have made it on: a contributor's controller can file a task, and starting an agent on one takes a maintainer. When the server refuses, the controller tells you so. Every write is audited under your name with the controller named as the instrument, and a comment it posts for you says it was posted for you.
What it has no tool for
Merging a pull request, accepting a completion, answering a decision packet and moving a task into the final stage are not in its toolkit. Ask for that last move and it points you to the task page. It has no tool that deletes a project, a task or a user.
Does when you askCreate a taskMove a task to another stageComment on a task for youStart an agent on a taskSchedule a runInvite a memberSet a stage boundary
Has no tool forMerge a pull requestAccept a completionAnswer a decision packetMove a task into the final stageDelete a project, a task or a user
Each change is checked against your role on the project.
It plans work into epics
Describe an outcome and the controller can lay it out as an epic: a named body of work inside one project, with the tasks that belong to it. Each task says what it waits on, and Viberr starts it when that work is done. The epic itself orders nothing and holds nothing back. Its status is yours to set, and its progress is counted from its tasks.
A next step for when a task is accepted
The controller can leave a conversation its next step for the moment a task is accepted. Viberr then starts that turn itself, as the person who asked.
1EpicA named body of work in one project
2TasksEach belongs to one epic at most
3WaitsA task names the work it waits on
4ReleaseViberr starts it when that work is done
What holds in every conversation
It runs on your own Claude account
A turn uses the Claude account of the person who asked. The instance has no account of its own, so a colleague who has not connected Claude never stops you from asking.
Your conversations stay yours
A conversation belongs to whoever started it. A project's other members cannot read it, though an org admin can. Viberr never deletes one on its own.
You can steer a turn while it works
Send a message while the controller is working and it joins the turn at its next step. Queue it and it is answered in a turn of its own.
Tell it what you want done
On a running instance the controller's round button sits at the bottom right of a board, a task's page and most other pages. The sign-in page, your profile and your notifications have none, and neither do the two Controller pages. Open it and ask in your own words. The documentation's own example:
create a task on WEB to add rate limiting to the login formWEB is a project's key. The task the controller creates gets an operator of its own, like any other task. More about the agents