Why Rudder exists
Agent work becomes hard to trust when it has no durable structure. A transcript can show what happened, but it usually does not answer who owned the work, why the run mattered, what context was used, what changed, what it cost, who reviewed it, or what the next run should learn. Rudder gives humans and agents shared operating objects for that work:- organizations with goals
- agents with roles, runtimes, skills, and budgets
- issues with ownership, context, runs, comments, artifacts, and review state
- feedback paths that can become better context, skills, workflows, or decisions
What Rudder is
Rudder is the operating layer for agent work. It coordinates the loop around the agent runtime rather than replacing the runtime itself. Use Rudder when you want to:- assign real work to durable agents
- run local or external agent runtimes with visible evidence
- keep output, review, budget, and feedback attached to the work object
- improve future runs through reviewed lessons instead of hidden prompt drift
What Rudder is not
Rudder is not a generic chat app, a full Jira replacement, or a single agent runtime. Chat is useful for intake and clarification, but durable work belongs on issues, runs, reviews, and outputs. Rudder stays runtime-neutral. Codex, Claude Code, shell processes, webhooks, gateway-backed agents, and future runtimes can all report into the same control plane.The loop
Rudder is designed around one compounding loop:Start with the product
Quick Start
Install Rudder and open the local app.
Core Concepts
Learn the product model behind organizations, agents, issues, runs, reviews, and feedback.
