First repository task¶

With a model connected, ask Colossus to map a repository before giving it a change to make. This first task should leave you with a short explanation of the codebase, file paths you can inspect, and an idea for what to do next.

1. Open your repository¶

Open a terminal in the root of the repository you want to inspect, then run:

colossus models route primary
git status --short

The model route should name the provider and model you selected, rather than echo. If it does not, follow Connect a model for this workspace. Keep the Git status output so you can compare it after the task; existing changes are fine.

2. Ask Colossus to explore¶

Choose the interface you prefer:

colossus tui

colossus run "Map this repo. Cite files and tests. Suggest a first task. No edits."

Colossus should describe the main components, point to the test entry points, and support its findings with paths in your repository. If the answer is too broad, ask it to inspect the cited files and name the exact functions or modules behind its claims.

3. Check the result¶

Open a few of the cited files to confirm the map. Then compare the repository status with the output you saved before the task:

git status --short

The status should be unchanged because the request asked for inspection only. The active access and approval settings and sandbox still govern tool authority; choose an isolated workspace profile if you want that boundary for later tasks.

What's next?¶