Imagine a small team preparing a launch announcement. A human sets the goal, an Agent drafts the file, another person reviews it, and the final Markdown file must remain easy to find. Rudder gives every part of that loop a clear home.

​
The work loop through one case

The organization is the workspace for the team. Its goal explains why the launch matters. A project can group the announcement with related launch work, resources, and dates. The operator can begin in Chat and refine the announcement through conversation. If the work needs a named owner, dependencies, status, or a review path, the operator can use an Issue. An Agent is the durable team member responsible for a kind of work. An Agent Run is one bounded attempt by that Agent. The runtime is the execution environment Rudder invokes for the run. These are related, but they are not the same object. The run leaves evidence such as a summary and transcript. The finished announcement belongs with the Chat or Issue as an output. A review decision stays with the work record, so the team can see what was accepted or what must change. Rudder dashboard overview

​
Surfaces you will meet

The Overview summarizes the organization, including operational signals that help the operator see where work is moving or waiting. It does not replace the source Chat, Issue, run, review, or approval.

​
When structure helps

Rudder does not require every task to use every object. A short drafting loop may remain in Chat. A release with dependencies and an independent reviewer is easier to operate as one or more Issues. Projects help when several work items share a result or context. Automations help only after the trigger and output path are predictable. The boundary is simple: preserve enough structure to make the next action and the final result inspectable. Do not create fields or objects that the work does not need. This sequence is independent of the sidebar order:
  1. Create your first organization and finish one small task.
  2. Choose Chat or an Issue for the way you want to work.
  3. Understand Agents and Agent Runs, including the runtime boundary.
  4. Run an Issue from intake to done when explicit coordination helps.
  5. Review agent work and leave the result, evidence, and decision together.

Previous: First Organization

Complete the first work loop before exploring each concept.

Next: Goals, Projects, and Issues

See how direction becomes grouped, durable work.