Running agent work
Use Redgold agents to build and evolve a fully managed application: describe an outcome, organize the work, review changes and verify the deployed behavior. Redgold provides the workspaces and supporting infrastructure and operates the application's pipelines, data and deployment. Fleet management is how you keep several pieces of that work moving coherently.
These guides describe the managed workflow. Workstream scheduling and fleet controls depend on the environment enabled during onboarding; they are not a promise that every account has an unrestricted fleet API. The assigned-agent REST guide documents the current customer control boundary.
The pieces you work with
| Concept | What it represents | Support-app example |
|---|---|---|
| Application | Running behavior, schemas, pipelines and data | A support queue with automated triage |
| Workstream | A continuing objective grouping related issues | Improve urgent-request handling |
| Issue | A bounded outcome with acceptance and dependencies | Preserve urgency when requests are retried |
| Agent | The worker assigned to investigate or change the app | Implement and verify duplicate handling |
| Slot | Assigned execution capacity | An environment in which an agent can run |
| Workspace | Repository checkout and working files | Schema, transform, manifest and tests |
| Session | A conversation and its tool activity | The implementation run and review feedback |
| Delivery | Reviewed revision through deployment and verification | The updated support route serving users |
An issue can outlive a session, and a workstream can involve several issues and agents. A running agent may be waiting on a test or decision; its process state alone does not tell you whether the application objective is complete.
Follow one application change
- Define the workstream and issues: state the outcome, split independent work and record dependencies.
- Understand agent lifecycle: distinguish queued work, startup, active execution, waiting and completion.
- Supervise and recover: inspect evidence and intervene at the right boundary.
- Follow an app workstream to delivery: a worked example covering a blocked decision, parallel work and deployment verification.
Working with external systems
Agents can also maintain an authorized external repository, review its pull requests and use its existing checks. Managed applications can connect to external APIs and data sources. Specify which parts Redgold operates and which remain external when defining the workstream; an external repository connection does not automatically make its hosting a managed Redgold deployment.
Start with coding agents for a single task or architecture for how agent work connects to the managed application runtime.