# User guide
Documentation for people using magi-code: available features, setup, configuration, behavior, and common workflows. Implementation detail stays in the technical reference.
## Start here
1. [Install magi-code and connect a provider](getting-started.md).
2. [Learn Mission Control](mission-control.md).
3. Open a repository and describe the work you want done.
## Core features
| Providers, models, reasoning, and Fast mode | [Providers and models](providers-and-models.md) |
| Global, project, and temporary settings | [Configuration](configuration.md) |
| Saved sessions, context, compaction, rewind, export, and summaries | [Sessions and context](sessions.md) |
| Worktree diffs, review comments, and prompt suggestions | [Review and history](review-and-history.md) |
| Repository instructions, skills, prompts, and primary-agent profiles | [Customize agent behavior](customization.md) |
| Side conversations and delegated subagents | [Side agents and parallel work](agents-and-delegation.md) |
| Built-in tools, shell access, web research, images, and safety | [Tools and safety](tools-and-safety.md) |
| MCP, LSP diagnostics, hooks, and Jev | [Integrations and automation](integrations.md) |
| Themes, motion, panel layout, and terminal images | [Appearance and terminal features](appearance.md) |
| Errors and recovery | [Troubleshooting](troubleshooting.md) |
Each feature guide explains what feature does, how to enable or configure it, how it behaves, and when its technical reference matters.
## Safety
Magi-code can edit files and run shell commands. Review requested changes and command output. Shell guardrails are not an operating-system sandbox, so isolate repositories you do not trust.
Keep API keys, OAuth data, and other secrets out of prompts, instruction files, settings, review comments, and shared session exports.
## Need exact behavior?
User guides cover practical settings and normal behavior. Use the [technical feature reference](../features/README.md) for exhaustive keys, precedence, file formats, hard limits, storage contracts, failure semantics, and implementation details.