> ## Documentation Index > Fetch the complete documentation index at: https://qodex.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Missions and agents > Use Qodex agents on the Autopilot page to keep API tests, security checks, and bug follow-up running without starting from a blank chat each time. # Missions and agents Missions are repeatable Qodex jobs for work that should happen more than once. In the web app they appear as **agents** on the Autopilot page. Use an agent when you want Qodex to keep a product area healthy over time, such as writing and replaying API tests for a collection, running API security checks, exploring for bugs, or following up on new bugs. ## Find your agents In the sidebar, open **Autopilot > Agents**. The page lists: * **Switched on**: agents that run on their trigger. * **Switched off**: agents you added but paused. * **Add an agent**: the library of agents you can add to the project. What agents produce, such as proposals, questions, and updates, lands as cards under **Autopilot > Tasks**. See [Autopilot](/docs/autopilot) for the board. Agents only run while Autopilot is on for the project. If it is off, an agent's page says **Autopilot is off for this project** until an admin turns it on. ## Add an agent from the library Each library card shows what the agent does, what it runs against (a collection, a flow, or an endpoint), and its default trigger. | Agent | What it does | Default trigger | | - | - | - | | Auto-fix bugs | Reads the code behind an open bug and opens a pull request with a fix for a person to review. | Manual | | API security sweep on a flow | Checks the endpoints one user flow calls against the OWASP API Top 10 and reports only what it can prove. | Manual | | API security checks | Tests a collection's endpoints against the OWASP API Top 10 every night and proposes security tests. | Daily | | Daily API tests | Writes and runs API tests for a collection every morning and keeps the ones that pass. | Daily | | Explore for bugs | Uses the product like a patient tester every night and files the bugs it can reproduce. | Daily | | Fill coverage gaps | Finds the endpoints in a collection that no test touches and writes tests for them. | Manual | | Tests for new production errors | Watches your error tracker every hour and drafts a test for each error seen for the first time. | Hourly | | Nightly regression | Replays a collection's saved tests every night and tells you what broke and what merely went stale. | Daily | | Performance watch on an endpoint | Times one endpoint every night and flags it when it drifts slower than its baseline. | Daily | | Replicate bugs on staging | Writes a test that shows each new bug on staging, runs it, and records whether the bug is really there. | On a new bug | Click **Add** on a card. You can edit the default instructions and choose which connectors the agent may use before you add it. ## Configure an agent Click an agent to open its page. From there you can: * Switch it on or off with **Enabled**. * Click **Run now** to start it immediately. An agent that works on one bug asks you to pick the bug first. * Read **Run history** for every run and open the chat behind it. * Set the **Trigger**: **A bug is opened**, **A bug is reproduced on staging**, **On a schedule**, or **Only when I press Run now**. Bug triggers can be narrowed with **Severity includes** and a daily run cap. Schedules offer presets or a **Custom schedule**. * Choose what it **Runs against**, such as a collection, flow, or endpoint. * Edit its **Instructions**: project-specific rules, constraints, and preferences. * Pick its **Connectors**: the observability tools, **Environment** (or **The project default**), and **Code** access it may use during a run. Click **Save** to publish trigger, target, and connector changes. Instructions save from their own editor. ## Run now Click **Run now** when you want an agent to run immediately, without waiting for its trigger. This is useful after importing a new collection, merging an API change, changing auth settings, or finishing a product area that needs fresh coverage. ## The Auto-fix agent **Auto-fix bugs** pushes a branch and opens a pull request on your repository, so only a project admin can add it, change it, switch it on, or run it. Every member can read its page. Once it is added and on, project admins also see **Fix in code** on open findings, which sends that bug to the agent. See [Triage workflow](/docs/findings-triage-workflow). ## Collection sync Keeping an API collection in line with your code is set per repository rather than as an agent. Open **Code > PR review**, go to **Settings**, choose the repository, and open the **Automation** tab. Under **Collection sync**, turn on **Sync on merge** and pick the collection. When a pull request merges into the default branch, Qodex works out what changed and brings the collection back in line. When sync finds new or changed endpoints, review the catalog rows, open important requests in the [API Playground](/docs/api-testing-playground), and promote stable requests into [API scenarios](/docs/api-testing-scenarios). ## Review before promotion Agents are designed to do the repetitive work while keeping you in control of what becomes active. When an agent proposes scenarios, catalog changes, or follow-up work, review the card on **Autopilot > Tasks** before relying on the result in schedules, CI, or merge gates. Keep drafts as drafts until the request shape, auth profile, assertions, and environment are correct. ## Where agents fit Agents do not replace scenarios or test runs. They help create and maintain them. * Use [scenarios](/docs/concepts-scenarios) for reusable test logic. * Use [test runs](/docs/run-tests) to execute scenarios and review results. * Use [endpoint catalog](/docs/api-testing-endpoint-catalog) to understand API coverage. * Use agents when Qodex should repeatedly keep those assets up to date. ## Related See the API map that collection sync keeps current. Turn synced requests into reusable tests. Run the scenarios that agents help maintain. Give agents stable product context and testing rules. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.