Working with Local Projects

Every conversation in CodeProso belongs to a project folder. The assistant’s file tools are scoped to that folder.

Opening a project

Choose Open folder… and pick the root of your repository. CodeProso then:

• builds a repo map — the structure of files and top-level symbols,
• reads git state — current branch and changed files,
• restores your previous sessions and pinned files for that folder.

What CodeProso can access

The local file tools can read, search and edit — inside the project only.

• Files matched by .gitignore are skipped by search and the repo map.
• Reaching outside the project folder always requires your confirmation.
• In Plan mode, edit tools are disabled entirely.

Pinning files

Pin files you want in context for the whole session — an architecture doc, a schema, a style guide. Pinned files appear in the sidebar and are sent with each request.

Use @ in the composer to reference a file for a single message.

Formatter and tests

Open Settings → Tools and set commands for your project:

Formatter:     npx prettier --write
Test command:  npm test -- --run

After applying a change, CodeProso runs the formatter on touched files and can run your tests. Results appear on the diff card; in Agent mode, failing output is read and fed into the next attempt.

Terminal commands

CodeProso can run commands in an integrated terminal. By default it asks before running anything, and always asks for commands that reach outside the project. You can change this under Settings → Tools.