# Copilot sessions

Learn the copilot sessions workflow, fields, resource states, permissions, and troubleshooting in Cypacky Compute.

## Session contents

Each Copilot session is bound to the active space and retains the prompt, cited data, action plan, and result. Use separate sessions for different instances or incidents.

## Session lifecycle

| State                 | Meaning                                              |
| --------------------- | ---------------------------------------------------- |
| Draft                 | Prompt entered, no result generated                  |
| Analyzing             | Copilot is reading configuration, metrics, or events |
| Awaiting confirmation | A state-changing plan is ready                       |
| Running               | Confirmed work request is processing                 |
| Complete              | Result and citations are available                   |

## Procedure

1. Create a session in **Compute Copilot**.
2. Select the space and target instance.
3. Ask a verifiable question and include a time range.
4. Review citations and the plan before confirming.
5. Record conclusions in the timeline for handoff.

## Troubleshooting sessions

- Wrong context: select the space and instance again.
- Insufficient data: narrow the time range or provide an event ID.
- Action not running: check whether the session still awaits confirmation.