Find the files your next prompt needs.
Choose a local repository, inspect its files and ask for context suggestions. Select what belongs in your prompt, then copy stable file tags or export documents. A local architecture scan can add module health to the same explorer.
Announcement. Station 10 reads repositories. It does not edit them. It has opinions and keeps them to itself.
What happens in this stationNine things, in the order you would meet them.
- Live
- Beta
- Insider preview
- Planned
- Status to confirm
Find the repository inside a parent folder.
Scan a parent folder to depth two. Each find shows repository-marker evidence, such as .git or package.json. The scan states hit caps and never descends into a repository it already found. One click starts indexing a find.
Index the repo and see what was left out.
Choose a local repository and watch real phases and file counts. Above 10,000 files, indexing takes a source-first, shallow-first subset instead of refusing the repo. Stop preserves the last good index.
Your repository supplies its own denominator.
Look at one index in five ways.
Compact, Detailed, Tree, Graph and Architecture show the same repository index. Search, filter and select files without changing the repository underneath. Keyboard selection and virtual scrolling keep the explorer usable beyond the first screen.
Read the actual file before choosing it.
The preview reads real file content through the app's preload bridge. Syntax presentation is configurable. Open a candidate file and check what it contains before adding it to the context you export.
Ask which files belong in the prompt.
Describe the work in plain language. Suggestions rank files from imports and naming, with confidence, relationship evidence and required-file status. Path tie-breaking is deterministic. You choose the files; the ranking does not guarantee complete context.
Follow a weak module back to its files.
If a local SMARCH scan covers this repo, Architecture shows module health, scores, warnings and weakest bricks. Click a weak brick to filter the explorer. Repository counts come from its own bricks; wider portfolio totals carry a separate label.
Most users have no local scan. The empty state treats this as ordinary.
Copy the context you selected.
Copy or export chosen files as stable repository-relative @tags or documents. A tag such as @src/renderer/App.tsx names the file without a machine-specific path. You take the result to your prompt; automatic submission to a coding agent is not established.
Keep local repository work going offline.
Local indexing, browsing, selection and export continue when disconnected. Network-backed enrichment waits for reconnection. This is a local repository workflow, not a promise that indexes or filesystem access match across desktop and web.
Ask the agent to index a real path.
Registered commands let the Core Agent open and organize repository work, index a path, cancel indexing or open the native directory picker. Indexing requires rootPath. Failures remain visible. C0:REP does not establish file editing, shell execution or Git commits.
This map lists nine commands. The Core Agent inventory lists ten. Parity needs checking.
What this station hands onAnd what it takes in.
- Local repositoryC0:REPNative directory selection starts main-process indexing of a real path.Beta
- C0:REPYour promptSelected files become stable @tags or documents. You choose where to use them.Beta
- SMARCHC0:REPAn existing local scan adds repository-matched module bricks, health and warnings.Live
- C0mpC0:REPA project capsule's repository address offers the next step: index it in C0:REP.Live
- C0:REPC0mpAn indexed repository becomes an outbox capsule proposal. The owner promotes it; an unindexed repo is refused.Live
- The agentC0:REPManifest commands open, index and cancel repository work through the registered adapters.Beta
- C0:REPC0:CODEThe admin-v2 artifact dock can open C0:REP as a real module beside a coding pane.Insider preview
- SettingsC0:REPThe same metadata supplies nine setting groups in global Settings and the module panel.Live
The same CLI change, twice.Choose context for a coding prompt.
Separate apps
- Find the repository in a file manager.
- Browse candidate files in an editor.
- Write the paths and import relationships in a notes app.
- Copy the selected context into a coding assistant.
You collect paths and relationship notes by hand.
Station 10
- Choose the repository and describe the CLI change.
- Inspect suggestion evidence and preview the files you want.
- Copy the selected @tags or export documents for your coding prompt.
One index for selection. You still decide what the prompt receives.
Facts the lab is oddly proud of
- 10,000Above this file cap, the indexer ranks a subset and labels the omissions. A large repo is not refused.
- Depth 2Repository discovery stops at depth two and never recurses into a repo it has already identified.
- FourMissing architecture has four states: no scan, a scan that misses this repo, unreadable, or too large.
- ProjectThat word marks a repository-specific setting override. Unmarked values are global defaults.
Not yetPlanned, and listed here so nobody has to guess.
- Whole-repository coverage above the capThe index is a ranked subset above 10,000 files.
- An architecture scan for every userThe overlay needs an existing local SMARCH scan that covers your repo. A bundled cloud scan is not established.
- Editing files and making commits hereIt does not establish editing, shell execution or commits.
- Repository and index sync between devicesAn index lives on the machine that made it. Nothing carries it to your other computers yet.