Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · Krate Agent Dispatch
workflow:krate-dispatch-agenta5c.ai
Search record views/
Record · tabs

Available views

II.Record viewspp. 1 - 1
overviewjsongraph
II.
Workflow overview

workflow:krate-dispatch-agent

Reference · live

Krate Agent Dispatch overview

End-to-end workflow for dispatching an AI coding agent within Krate. Triggered by a user command (UI button, kubectl create, PR comment /agent), a schedule (AgentSchedule), or a pipeline step. Steps: 1. Dispatch request: An AgentDispatchRun resource is created with the target repository, branch, prompt, and AgentStack reference. 2. Permission review: The platform evaluates the dispatch against org-level AgentPermissionSets and PolicyProfiles. If the requested tools or resource limits exceed policy, the run is rejected or escalated for org-admin approval. 3. Context bundle assembly: Krate checks out the repository at the specified branch, injects CLAUDE.md and relevant memory snapshots from the company brain, and prepares the agent workspace container. 4. Agent-mux launch: The dispatch controller creates a Kubernetes Job running the agent-mux container with the selected coding agent (Claude Code, Codex, etc.). The session streams output back via SSE. 5. Completion: On agent completion, results are collected — files modified, PR created/updated, tests run. A memory snapshot is generated and stored. The AgentDispatchRun status is updated to Completed or Failed.

WorkflowOutgoing · 5Incoming · 0

Attributes

displayName
Krate Agent Dispatch
description
End-to-end workflow for dispatching an AI coding agent within Krate. Triggered by a user command (UI button, kubectl create, PR comment /agent), a schedule (AgentSchedule), or a pipeline step. Steps: 1. Dispatch request: An AgentDispatchRun resource is created with the target repository, branch, prompt, and AgentStack reference. 2. Permission review: The platform evaluates the dispatch against org-level AgentPermissionSets and PolicyProfiles. If the requested tools or resource limits exceed policy, the run is rejected or escalated for org-admin approval. 3. Context bundle assembly: Krate checks out the repository at the specified branch, injects CLAUDE.md and relevant memory snapshots from the company brain, and prepares the agent workspace container. 4. Agent-mux launch: The dispatch controller creates a Kubernetes Job running the agent-mux container with the selected coding agent (Claude Code, Codex, etc.). The session streams output back via SSE. 5. Completion: On agent completion, results are collected — files modified, PR created/updated, tests run. A memory snapshot is generated and stored. The AgentDispatchRun status is updated to Completed or Failed.
workflowKind
development
triggerType
event-driven
typicalCadence
on-demand
complexity
complex

Outgoing edges

applies_to_domain2
  • domain:platform-engineering·DomainPlatform Engineering
  • domain:software-engineering·DomainSoftware Engineering
involves_role3
  • role:platform-engineer·Role
  • role:backend-engineer·RoleBackend Engineer
  • role:devops-engineer·Role

Incoming edges

None.

Related pages

No related wiki pages for this record.

Shortcuts

Open in graph
Browse node kind