Review changes with Redpact
Configure project dependencies and review worktree changes through execution evidence and application screens.
Start with the Redpact in-app workspace beside your GPT conversation. Install the App Page Plugin and open Redpact from Apps in sidebar, or install the web runtime with npm/pnpm. The full app provides project/worktree navigation and evidence, and the web review screen handles execution approval and results. Chat MCP returns structured evidence and review links.
Redpact is a local development review tool for people working with coding agents. Define the project's runtime needs, run tests against the working checkout, and inspect code changes, test intent, observed results, and application screenshots together.
When an agent reports completion, you should be able to see what changed, whether the requested behavior was checked, and what the application looked like. This guide follows that process.
From project setup to change review
flowchart TD
P["Connect project"] --> D["Define app and dependencies"]
D --> W["Choose execution worktree"]
W --> E["Prepare environment and execute tests"]
E --> R["Review diff, intent, results and screens"]
R --> F["Request another change"]
F --> WThe agent investigates the repository and writes configuration, code, and tests. Redpact performs the selected execution and records evidence. You judge whether that evidence adequately covers the request.
Two questions to understand first
Which environment ran the code? Shared settings define the app's database, cache, and external API options. All worktrees share one fixed dependency configuration; execution uses that checkout's files. Shared configuration does not imply shared runtime resources or data. Start with Dependencies and worktrees.
What supports the completion claim? A diff shows code changes, tests show intended checks and their results, and captures show application states during execution. Review your first change connects these in one example.
Questions and evidence
| Question | Evidence to inspect |
|---|---|
| Which checkout contains the requested change? | Actual worktree and diff |
| Which dependencies were used? | Configured services and dependency kinds, recorded environment information |
| Were success and error behavior checked? | Test source, case intent and assertions |
| How far did execution actually get? | Recorded case and step results, diagnostics |
| What did the user see? | State-specific captures from the actual application |
| Was the revised code executed again? | New execution identity and recorded source |
Passing tests establish that their assertions were satisfied. They do not automatically judge presentation or discover missing requirements. Current files can change after execution; read the recorded source when interpreting results.
Start with your project
- Install and connect the local server and agent.
- Connect and configure your project using the actual repository.
- Run your first test to create execution evidence.
- Use Reading results and Writing verification to cover your own change.
Redpact is pre-release. This site describes the current local implementation. The documentation site itself does not connect to your projects.