Project memory + coordination for coding agents

Agents write code. Evor keeps the project together.

Keep using Claude Code, Codex, or whatever comes next. Evor remembers how the project works, knows what your team is changing, helps delegate tasks, and coordinates work before agents collide.

Join early access See the workflow

Local-first. Git-anchored. No new IDE.

rsearch / claudeevor connected

you › add resumable upload recovery

evor project memory

✓ map current at main@82af31

UploadSession · PipelineWorker

evor team check

Alice is modifying UploadSession

branch: metadata-v2

overlap: HIGH

claude › I’ll confirm scope before changing it.

✓ coordination confirmed

Alice → metadata representation

You → restart recovery + tests

✓ worktree evor/82-restart-recovery

claude › ready to work

Why Evor

Every developer has an agent. Those agents still work alone.

They relearn the same codebase, duplicate investigations, and discover conflicts after code is written. Evor adds the missing project layer underneath them.

01 / memory

Stop rescanning the repository

Evor keeps a compact project map tied to Git and refreshes only the parts that changed.

02 / awareness

Know what is already in flight

Branches, tasks, affected components, decisions and published findings are visible before work starts.

03 / delegation

Give work to a teammate

Create a task for another developer, include the relevant project context, and let their coding agent pick it up.

04 / coordination

Split work before agents collide

Overlapping agents confirm scope first, then continue in the same workspace or an isolated worktree.

Before implementation

project memory

task intent

team overlap

delegate / coordinate

worktree

implement

PROJECT UNDERSTANDING

A living model, not another giant context file.

Architecture, components and important flows are stored as small addressable nodes with source references and freshness.

Git-anchored project map
Incremental refresh
Static facts before model summaries
Branch deltas instead of duplicated maps

WORK PREPARATION

Agents check the team before they touch the code.

Evor detects the same task, overlapping symbols, files, APIs or project areas before implementation begins.

Same-task duplication prevention
Agent-to-agent scope confirmation
Persistent task constraints
Conditional Git worktrees

TASK DELEGATION

Create work for a teammate without rewriting the context.

Ask your coding agent to create a task for another developer. Evor attaches the relevant project state, constraints, dependencies and expected outcome.

Assign to a developer identity, not an agent session
Recipient can accept, reject or clarify scope
Task appears in the teammate's next agent session
Progress and handoff remain queryable

Team model

Your agent stays yours. Project knowledge becomes reusable.

Evor nodes connect explicitly. Personal notes and checkpoints stay local. Shared decisions, published findings, branch presence, messages, and delegated tasks move only where intended.

Rabin

Claude Code · local Evor

↔

Project knowledge

shared facts · decisions · activity

↔

Alice

Codex · local Evor

The first agent learns the codebase. The next one should not start from zero.

Architecture

Local by default. Central coordination only when the team needs it.

Evor works with one developer, direct trusted peers, or an optional coordinator for membership, presence, message relay and project-wide activity. Git remains the source of truth for code.

Private stays localScratch notes, personal checkpoints and raw agent conversations are not project-shared by default.

Shared knowledge is attributedRemote facts preserve source and revision; deterministic facts can be re-verified locally.

No distributed database requiredNodes exchange selected messages, manifests and knowledge objects instead of cloning one another's state.

The agent remains the interfaceClaude Code and Codex keep doing the engineering. Evor prepares and remembers the work around them.

Engineering history

Ask what happened without reading yesterday’s chat.

Evor keeps structured project activity so developers and agents can query work by task, person, branch, component, file, decision, status or time.

ASK EVOR

“What changed in ingestion this week?”

See completed work, current branches, delegated tasks, decisions, findings, coordination and verification—not a wall of terminal events.

EXPLAINABILITY

“Why did you create another worktree?”

Important Evor actions can be traced back to project state: dirty workspace, independent task, peer overlap, or coordination outcome.

Early access