Set up a project

1. Open your project

Complete Installation.
Open the repository in Codex, Cursor, or Claude Code.
Use the same setup request for a new or existing project:

2. Answer the setup questions

New project: describe who it is for, what you want to build first, and any constraints.
Existing project: the agent reads your code, tests, and instructions before suggesting changes.
Choose the Integrity workspace and Team for this project.
Confirm the proposed workflow: Branch for code, or Revision for documents such as Word and Excel files. See Choose a workflow.
Confirm the proposed setup when the agent asks.

3. Review and save

The agent shows the proposed changes before you approve them.

Project context in .integrity/project.md names the project's purpose, Integrity workspace, and default Team.

Project rules use Integrity's layout, not a copy of another repository's rules:

.agents/rules/index.yaml is the registry that says which rules exist and when they apply.
.agents/rules/ holds the actual rule files. Those files are yours: coding conventions, safety limits, and review expectations for this repository.
Existing instructions such as AGENTS.md stay in place. Setup indexes them so the agent can select the right files. It does not replace them with Integrity's own engineering rules.

If you already have a mature repository, see Adopt an existing project. For what the registry is, see Project Foundation and rules.

When you're happy with the changes, ask the agent:

How code changes reach your project

During setup, review which branch receives completed work and whether a pull request is required.
Coding tasks use separate Git worktrees when concurrency, isolation, or project policy requires them. Short safe changes can use the current checkout while preserving unrelated work.
The agent checks and commits its changes, then integrates them according to your repository settings.
Required reviews still apply. Updating the remote branch may run your existing CI or deployment automation.
If checks or integration fail, the agent preserves the work and explains what needs attention.

In a Revision project there are no task branches, worktrees, or pull requests: the agent edits the real files in your checkout and commits each step. See Choose a workflow.

Next step

Continue to Build your first project.