Chat with your server operator
Keep server administration outside coding projects. Ask a Claude or Codex operator chat to investigate a problem, provision an approved service or repair a connection, then follow the request and its result.
Automatic operational tasks require a matching deployed controller, MCP, host/runtime and verified task-launch capabilities. Each task keeps an isolated read-only conversation; exact selected permissions and scope stay fixed. Diagnostics publish findings, repairs need fresh endpoint evidence, and declared remote TCP access needs its exact SERVICE grant and managed-guide proof. Applied, blocked and failed outcomes remain distinct; requester notification and native acknowledgement are separate from completion. Legacy prose enters exact-scope triage without inventing execution authority. Native Claude Remote Control depends on account eligibility and a current scoped link; restricted workers are excluded. Codex experimental daemon/pairing is not integrated or enabled.
How it works
Work in one Main conversation
Keep server administration outside coding projects in one repository-free Main conversation with your configured host, account and model defaults. Core creates and clears operator task executors and policy reviews itself; chats from earlier versions stay as legacy chats you can stop and delete.
Start with a balanced model
First setup offers Balanced model from this account. It lowers a premium native default to the balanced tier and skips quota-exhausted models; explicit choices and inherited preferences still win.
Find requests needing you
Control Room has its own human-attention count. Open the current approval or chat without sending input or losing your draft. Running tasks and completed history stay out of the count.
Recover scoped MCP access
Matching controller and host versions prepare a session-bound caller for eligible managed Docker sessions on a new provider start or existing broker recovery. Native metadata and guide receipts establish readiness; the running client’s tool list stays separate.
Fall back to another subscription
Keep an ordered fallback list in Settings → Control Room. When the selected subscription is exhausted, Main continues its own conversation on the next ready account at its next idle point, and new task sessions never start on the exhausted account.
Route each messenger explicitly
Choose Control Room as a connected bot’s destination or keep regular session controls. Changing the console view leaves that destination alone; revoking Control Room authority removes the route without disconnecting the bot.
Use your provider for dictation
devctrl has no voice input of its own; dictate through the provider’s own remote control. Replies can still be read aloud with the client device’s installed voice.
One isolated chat per approved operation
Approved system tasks get a separate read-only chat. Keep human conversations and messenger routes separate, and inspect pauses or cancel work before submission.
Send operational work to the server operator
Ask the configured server operator to investigate or repair an existing granted service. Reuse the exact approved action, track the durable request and inspect its verified outcome. Diagnostics publish findings; repairs also require a fresh endpoint check. Requires matching deployed operator and MCP modules.
Return the outcome to the requesting session
Every completed, blocked or failed task records an outcome and queues an update for the session that requested it. A saved result and confirmation that the agent received it remain separate.
Bind execution to the approved action
A typed operational descriptor identifies one requested action and its intended result. It always requires manual danger review. Removing that action also removes its execution authority. Other users retain administrator execution review.
Open the native Claude conversation
Open or copy a current scoped Claude link without sending input or replacing a draft. Restricted workers are excluded; Codex pairing stays inactive.
Keep running guides current
Compatible deployed hosts update the affected guide section when the managing route changes. File update and native notification have separate receipts; the provider keeps running. Physical host commands still need a configured and verified tooling namespace.
Try the interface
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Watch the workflow
Loading the recorded terminal…
Release videos
- devctrl 0.41.0: Decide a held secret in Control Room, and spot each kind at a glance chapter at 0:54 on YouTube
- devctrl 0.38.0: Decide a command review from Needs attention chapter at 0:00 on YouTube
- devctrl 0.26.0: Codex and Claude dialogs in Needs attention chapter at 0:59 on YouTube
- devctrl 0.23.0: Control Room setup steps make a deployment one prompt chapter at 0:55 on YouTube
- devctrl 0.15.0: Control Room recovers from provider errors chapter at 0:00 on YouTube
- devctrl 0.14.0: Send an undelivered task result again chapter at 0:00 on YouTube
- devctrl 0.14.0: Release a task held for administrator review chapter at 0:33 on YouTube
- devctrl 0.3.0: Control Room attention when a Host loses its gateway chapter at 0:49 on YouTube
- devctrl 0.1.171: Approval notices in Main chapter at 0:00 on YouTube
Put your server to work.
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.