Bring your repository
Start with an existing local Git repository. Create a separate worktree for the task so the main checkout stays intact.
Repository + task branchYour next coding task.
A clearer path to review.
An open-source agent workspace for local and cloud developer workflows.
Bring the repository, task, and proposed changes into one place.
Local firstHuman reviewedMIT licensed
A repository-to-diff workflowINTERACTIVE CONCEPT
rez1 / sample-repository
EXAMPLE / BUG FIX
Illustrative taskFix email validation
THE TASK
Reject invalid email addresses before saving a user profile. Preserve the existing behavior for valid addresses.
SCOPEsrc/profile.ts
VALIDATIONtests/profile.test.ts
The design pauses for approval before running commands.
Local plan: work in an isolated Git worktree.
This interactive illustration shows the intended experience. It uses sample data and does not execute code or call an AI model.
WHY WE’RE BUILDING REZ1
Delegating the task
is only the beginning.
The real work is keeping context, execution, and review connected.
Coding agents can move quickly. Developers still need to understand what changed, what ran, and whether the result meets the original task. Switching between a chat, a terminal, and a diff makes that harder.
We’re designing rez1 around one complete loop: give an agent a bounded task, follow its work, and make an informed decision about the changes.
BUILT WITH THESE DEVELOPERS IN MIND
Independent buildersOpen-source maintainersSmall engineering teams
THE FIRST RELEASE
One task. Four deliberate steps.
Our initial milestone is a local repository-to-diff workflow.
Each step keeps the next decision visible.
Define the outcome
Describe the change, its scope, and how to validate it. Begin with one agent integration and a focused objective.
Context + acceptance criteriaFollow the work
See the files read, edits proposed, and checks requested. Approve commands before execution and keep actual results visible.
Activity + command approvalsReview the diff
Compare the proposed changes with the task and its test results. Decide what to keep before merging or pushing.
Changes + human reviewA WORKSPACE THAT RESPECTS YOUR WORKFLOWMore autonomy.
More autonomy.
Clearer boundaries.
Start local. Build outward.
The first runtime is planned for your machine and tools. Isolated cloud environments come after the local loop is dependable.
Explore the architectureKeep the evidence together.
A useful review needs more than a patch. The task, tool activity, command output, and test results should be available together.
Read the MVP specificationBuild it in the open.
The foundation is MIT licensed. Follow the decisions, raise an issue, or contribute to a workflow you want to use yourself.
See how to contributeOUR PLANNED CLAUDE INTEGRATIONReason about the code.
Reason about the code.
Keep people in the loop.
We’re developing rez1 workspace, an open-source coding-agent workspace for local and cloud developer workflows. Our first milestone is a local repository-to-diff workflow, with a planned Claude integration for coding tasks and human review of proposed changes.
The integration design connects Claude to a bounded set of repository tools. The local coordinator would handle tool approvals, execution, and the review state.
Read the integration designIntegration planIN DESIGN
- 01
Understand the task
Provide the objective and relevant repository context.
- 02
Request tools deliberately
Read files and propose edits within the task workspace.
- 03
Validate with approval
Ask to run checks and record their actual outcomes.
- 04
Return a reviewable result
Present the diff, checks, and unresolved questions.
The Claude adapter is planned. No integration or partnership is claimed.
PROGRESS YOU CAN FOLLOWA small first release.
View the public roadmapA small first release.
A bigger direction.
01
Project foundation
AVAILABLE TODAYWebsite, source repository, and the specifications for the first workflow.
- Public MIT-licensed repository
- MVP scope and architecture proposal
- Contribution and security guidelines
02
Local task-to-diff loop
NEXT MILESTONEOne complete coding task in an isolated local workspace.
- Repository selection and task worktrees
- Claude adapter, activity, and approvals
- Diff review, checks, and cancellation
03
Cloud environments
LATERExtend the same task and review model to disposable remote environments.
- Per-task execution boundaries
- Credential, network, and resource controls
- Consistent local and remote task history
No agent runtime has shipped yet. We’ll publish release updates in the repository as the implementation develops.
THE PROJECT BEHIND THE WORKSPACEIndependent.
Independent.
Open source.
Built with intention.
rez1 started with a simple question: what should the workspace around a coding agent look like?
The project began in November 2025. The website and public repository launched in October 2026.
We’re beginning with the foundation rather than promising every workflow at once. The goal is a small, understandable system that helps developers move from a task to a change they can confidently review.
IslamRezwanProject maintainer · GitHub profile
PROJECT STARTNovember 2025
CURRENT STAGEFoundation & design
SOURCE LICENSEMIT
A FEW GOOD QUESTIONS
Before you dive in.
What exists now, what comes next,
and how to get involved.
Can I run a coding agent in rez1 today?
The current release is the project foundation: this website, the public repository, and design documentation. The local agent runtime is the next milestone. The interactive example on this page is an illustration, not a live agent.
What will the first version do?
Open an existing local Git repository, create an isolated task worktree, run one agent integration with visible activity and command approvals, and present the resulting diff and checks for human review.
How will rez1 use Claude?
We plan to use Claude for repository exploration and coding tasks through a tool-enabled adapter. The local coordinator will manage tool permissions, command execution, cancellation, and review. This integration is not implemented yet.
Will it work locally and in the cloud?
The first runtime is local. Cloud execution is a later phase that needs isolated environments, per-task credentials, quotas, and cleanup. The goal is to keep the same task and review experience in both environments.
Is the project open source?
Yes. The current website and project documentation are available under the MIT license in the public repository. Model services and third-party dependencies have their own terms.
How can I help?
Read the MVP specification, open an issue with a developer workflow you want to improve, or contact the maintainer. Focused feedback and small contributions are welcome while the local workflow takes shape.
LET’S BUILD A BETTER AGENT WORKFLOWWhat would you
What would you
delegate first?
Share a workflow, ask about the project,
or help shape the first release.