Assist agents with agent-cli

rac is the command name for Redgold's agent CLI. In a managed Redgold environment, a trusted agent or operator can use it to inspect capacity, start another agent, send bounded work through a ticket, observe progress, and stop work that should end. This is an allowed agent-assistance path when the caller has an assigned environment and the corresponding fleet permissions.

The CLI is an operational surface. An sk-rg- API key on a laptop does not grant fleet access. Customer applications should use the owner-scoped MCP tools or the managed-onboarding /v1/agents/* REST routes unless Redgold has provisioned a managed shell with rac access. The agent routes are absent from the generated public allowlist in the V1 route reference, so they remain outside the self-service public API contract.

Inspect available agents

rac fleet status

The status view identifies running slots, their current state, branch, context usage, and last activity. Use it before assigning work so two coordinators do not target the same slot.

Start an assisting agent

Allocate a slot from an allowed group and give it one bounded task:

rac agent spawn --group d-pod \
  --prompt "Review the API documentation examples and report inaccurate requests. Do not edit files."

The command returns the allocated slot and a command identifier. Keep the prompt scoped to an independently verifiable result. The parent agent remains responsible for reconciling the answer with other work and verifying any combined change.

When a specific assigned slot is appropriate, pass it positionally:

rac agent spawn d0-ag1 \
  --prompt "Run the focused documentation contract test and report the failing assertion."

Slot names and group names come from the environment operator. A caller cannot use this command to acquire a repository or tenant outside its configured scope.

Drive work from a ticket

Tickets give assisting agents a durable task description and acceptance criteria:

rac issue create \
  --title "Verify public API snippets" \
  --body "Check each curl request against its published route and record the result."

Inspect the returned ticket before dispatch:

rac issue view <ticket-id>

In environments configured for executor dispatch, an operator can assign the ticket to a warm executor:

rac issue execute <ticket-id> --profile fast

Dispatch availability and profile names are environment policy. The ticket records the assignment and result, which makes this path suitable for work that needs to survive one interactive session.

Observe and stop

Controller logs provide the lifecycle result for the pod that owns a slot:

rac agent logs <pod>

Destroy an agent after its task is complete or when its scope is no longer valid:

rac agent destroy <slot>

Cancellation and destruction have different meanings. Cancellation targets a queued control command by command id; destruction ends the assigned agent slot:

rac agent cancel <command-id> --slot <slot>

Use the identifier returned by the original command. Record incomplete verification in the parent task before ending an assisting agent.

Access and safety boundaries

• Fleet and ticket visibility is limited by the authenticated Redgold identity.
• Repository credentials are supplied by the managed environment according to its repository assignment.
• Secrets stay in the platform's credential system and out of prompts, tickets, logs, and command arguments.
• Production changes, access grants, merges, and irreversible operations remain subject to their configured approval policy.
• The complete CLI contains deployment and platform-administration commands. Those commands belong to environment operators; this page intentionally documents only the agent-assistance subset.

For customer-controlled delegation without managed CLI access, use Drive an agent session from an MCP client. For repository event automation, see GitHub App repository automation.