> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fimo.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Automate your project

> Choose between agent bundles, scheduled commands, webhooks, Connections, MCP, and Studio chat.

Fimo has several ways to automate work. Pick the one that matches how the work starts and how much judgment it needs.

| Use               | Choose it when                                                                        | What it does                                                            |
| ----------------- | ------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| Agent bundle      | The work needs a reusable goal, tools, judgment, or review rules                      | Runs a versioned agent definition from your repository                  |
| Scheduled command | One existing command should run on a cron                                             | Runs that command in a selected Branch                                  |
| Webhook           | Project activity should notify another service                                        | Sends an HTTPS request when a selected event occurs                     |
| Connection        | Fimo needs access to an external service                                              | Makes the connected service available to supported Fimo tools           |
| MCP server        | You want to add compatible remote tools to a project, or connect an assistant to Fimo | Connects tools through the Model Context Protocol                       |
| Studio chat       | You want to direct work interactively                                                 | Handles the request in a conversation where you can steer the next step |

These tools can work together. For example, an agent bundle can run on a schedule and use a connected MCP server. A webhook can notify another service after project activity. Chat remains the better fit when you want to guide the work one request at a time.

## Choose a starting point

<CardGroup cols={2}>
  <Card title="Create an agent bundle" icon="robot" href="/docs/agents/create">
    Put a reusable goal and its decision rules in git.
  </Card>

  <Card title="Schedule a command" icon="calendar" href="/docs/agents/schedules">
    Run one project command on a recurring cron.
  </Card>

  <Card title="Send webhooks" icon="webhook" href="/docs/cli/webhooks">
    Send project events to an HTTPS endpoint.
  </Card>

  <Card title="Manage Connections" icon="plug" href="/docs/studio/connections">
    Connect services and remote MCP servers in Studio.
  </Card>

  <Card title="Use MCP" icon="network-wired" href="/docs/ai/mcp">
    Add remote tools or connect an assistant to Fimo.
  </Card>

  <Card title="Work in chat" icon="comments" href="/docs/studio/ai-chat">
    Ask for work and steer it in Studio.
  </Card>
</CardGroup>

## Review autonomous work

Agent runs may ask for a blocking decision or leave completed work for review. [Review agent work and answer questions](/docs/agents/review-and-inbox) explains how continuations, retained work, conflicts, merge, and publish remain separate.