- Connect your coding agent from the repository root and verify the destination project.
- Ask the agent to run the installed Overmind setup workflow. On clients with slash commands, use
/overmind setup. - Review the discovered product purposes. A capability should describe work such as routing a support request; internal workers or model roles do not automatically need separate capabilities.
- Review the source-backed entry points, prompts, tools, branches and expected outcomes. Repair unmapped transitions from the code before syncing.
- Review
overmind.tomland the endpoint, project and metadata to be uploaded. The workflow runsovermind chassis, authors the map and runsovermind sync. It does not upload a repository archive, but captured prompts and source metadata are included. - Verify the successful sync and read
overmind://project/current?project_id=PROJECT_IDor inspect the Agent page. Check capability IDs and repository provenance.
.overmind/credentials.toml and credential-bearing client configuration out of version control.
After changing source code, refresh the scan. If the checkout changed during scanning, repeat it so the retained provenance describes the code actually inspected.
Next, instrument the application. A scan alone does not emit traces.