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

# Maintenance and Knowledge

> Assign recurring work to a teammate and keep durable reference documents available across conversations.

## Schedule recurring work

Use **Maintenance** for a repeated check or a one-time scheduled instruction.
An Intake schedule can bring findings into a collection as suggestions.

1. Write a concrete instruction and define what counts as a useful result.
2. Choose the timing and, for Intake, the destination collections.
3. In **Run with**, assign a Team member from the project or choose
   **Manual / external agent**.
4. Check that the assigned member is signed in and has the required access.
5. Inspect the occurrence's result and conversation after it runs.

Automatic assigned work runs while MTS is open and the Mac is awake. A schedule
does not grant additional permissions. Missed dates are collected into a catch-up
run; a busy member's work can queue.

A good first schedule checks one bounded source and reports either relevant
changes or that nothing needs attention. For example, an agent with an approved
issue-tracker connection can suggest new bugs for a selected project.

**Pause automatic maintenance** holds new starts; it does not stop work already
running. Use **Stop** for an active occurrence. Inspect partial results before
retrying work that might already have changed an external service.

## Keep reference material in Knowledge

Open **Knowledge** in the sidebar or use the books button in a member's chat.
A member's library holds Markdown documents across that member's conversations.
The owner can manage access and grant other members read or write access.

An optional organization library supports shared references. Agent access is
explicit: choose who can read and who can write.

Good candidates include:

* Product decisions and constraints that should survive a new conversation.
* Setup instructions verified against your environment.
* Links and short summaries of completed investigations.

Chat history is not automatically copied into Knowledge. Ask the teammate to
save the durable result, with its sources, when it will be useful later.

Knowledge is reference content, not a permission grant. In the current version,
Knowledge tools are available to embedded Team conversations; external MCP
connections do not expose the Knowledge library.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.