# Coding agents with ubctl

Use the Unbroker CLI and ubctl-ops skill to inspect projects, deploy applications and diagnose failures from a coding agent.

Canonical URL: https://unbroker.cloud/agents
Updated: 2026-10-14
Author: Unbroker

[Open Unbroker Cloud](https://app.unbroker.cloud/login)

[Deployment tutorial](https://docs.unbroker.cloud/guides/install-agent-skill)

## Build with Unbroker

- **From code to a running service:** Give the agent a repository, destination and deployment task through ubctl.
- **The same resources as Cloud:** Inspect and operate the projects you see in the visual console.
- **Verify the outcome:** Wait for a deployment to finish, inspect logs and check the application response.

## Deploy and inspect services through ubctl

Your coding agent can help implement a feature and take it through the next operational step. With ubctl and the official Unbroker skill, that step can be a deployment, a project inspection or a diagnosis of a failed release.

You supply the intended organization, project and permitted changes. The agent works with the same Unbroker services you can inspect in Cloud.

To deploy with Claude Code, start with [Deploy with Claude Code](https://unbroker.cloud/deploy/claude-code). The [implementation tutorial](https://docs.unbroker.cloud/guides/deploy-with-claude-code) has the prompt and the wait command. Codex uses the same skill with a different install target: [Deploy with Codex](https://unbroker.cloud/deploy/codex). From Cursor's terminal, or the documented MCP config, start with [Deploy an app built with Cursor](https://unbroker.cloud/deploy/cursor). Token scope, where the secret lives, and what a rollback skips are in [Letting a coding agent deploy safely](https://unbroker.cloud/blog/coding-agent-deploy-safely). For a Railway comparison, use the [Railway alternative](https://unbroker.cloud/alternatives/railway) page.

## Supported agent tasks

### Deploy an application

Ask the agent to inspect the repository, identify the framework and configure the intended service. It can trigger the release and wait for the terminal deployment state instead of stopping when the job is merely queued.

### Investigate a failed release

The CLI exposes deployment output, runtime logs and service metrics. The skill guides the agent through inspecting evidence so it can distinguish build, startup and application failures.

### Understand the project

Start with a read-only task: list projects, inspect a service or review recent deployments. It is a practical way to connect your coding environment to the application infrastructure.

## Keep the visual console in the workflow

Cloud remains the place to see the project, enter secrets and inspect resources directly. The agent uses your CLI authentication context and existing permissions, so you can move between interfaces as the task changes.

Resource creation and changes can generate usage charges. Give the agent concrete targets and an explicit scope for the work; keep credential values in the appropriate authentication or configuration interface.

## Connect your agent to Unbroker

Install ubctl, authenticate to the right organization and add the ubctl-ops skill for Claude Code or Codex. The setup tutorial includes a first read-only task, then links to deployment and diagnosis workflows.

## Choose your plan

Agent operations use your authenticated ubctl context. API tokens require Pro; the token scope and organization permissions control what the agent can do.

[Current pricing](https://unbroker.cloud/pricing)

## Related solutions

- https://unbroker.cloud/deploy/nodejs.md
- https://unbroker.cloud/solutions/api-with-postgres.md
- https://unbroker.cloud/deploy/docker.md