Atlas Scout

View saved version →

---
name: atlas-scout-code-navigation
description: Use Atlas Scout for local structural code navigation involving definitions, symbols, callers, references, dependency paths, architecture, traces, or edit impact. Use when asked where a symbol is defined, who calls or uses a function, what implements an interface, what breaks if code changes, or how a codebase is organized.
---

# Atlas Scout code navigation

Atlas Scout provides local structural-index evidence for code-navigation tasks. Select a matching
Scout capability when it fits the user's requested evidence:

- For a broad task or unfamiliar subsystem, call compact `fast_context` once for a source/test
  shortlist and exact ranges.
- `symbol_outline` lists declarations and exact ranges in a known file.
- `symbol_search` locates definitions and returns stable symbol ids.
- `symbol_references` returns indexed callers, references, and implementations.
- Graph, trace, path, architecture, and edit-impact tools return their corresponding bounded
  structural evidence.
- Omit `detail` and `limit` on initial discovery. Read useful cited ranges before another broad
  navigation call, and stop when the evidence is sufficient.

Text search remains useful for literals, regular expressions, generated or malformed code,
unsupported or partial language coverage, and focused completeness checks. Other development tools
remain appropriate for builds, tests, package managers, Git, servers, metrics, and runtime
diagnostics. Check Scout's coverage and trust metadata before treating an empty result as
exhaustive, and choose whichever available tool best fits the user's request.

View saved version →

---
name: atlas-scout-setup
description: Install, configure, verify, troubleshoot, or remove the Atlas Scout runtime and Codex integration when the user asks for Atlas Scout setup help.
---

# Set up Atlas Scout for Codex

Atlas Scout requires a separately installed `atlas-scout` executable. Never download or execute a
binary, alter operating-system security controls, or change the user's Codex configuration without
their explicit approval.

1. Check whether `atlas-scout` is already on `PATH` with `atlas-scout --version`.
2. If it is absent, ask the user to review <https://atlasscout.dev/docs>, including the preview and
   platform-safety disclosures. The supported installer is <https://atlasscout.dev/install.sh>.
3. After approval, download the installer to a temporary file for inspection before running it.
4. Verify the runtime and workspace:

   ```bash
   atlas-scout --version
   atlas-scout doctor --workspace /absolute/path/to/project
   ```

5. When this plugin was installed from the Zaguán Labs Codex marketplace, its bundled `.mcp.json`
   starts `atlas-scout mcp`. Start a new Codex thread and confirm the Atlas Scout tools are present.
6. If the server cannot start, check the executable path and run `atlas-scout doctor`. If Atlas Scout
   was also registered manually, remove or disable the duplicate so only one server starts.

Installing or removing this open plugin wrapper does not install or remove the proprietary Atlas
Scout runtime, and removing the runtime does not delete workspace indexes unless the product
documentation explicitly says so.