Open Source
Now in early access — limited design partner spots

Shared brain
for every AI session

Zero cold start. No duplicate work. No wasted AI spend.

Open source • Bring your own keys • Limited pilot spots

evols • session end

✅ Session complete: retention pain points mapped

Added to team knowledge base:

→ 5 insights on SMB churn triggers

→ 2 product decisions: onboarding over activation

→ Interview framework filed under /customers/smb/

Retrieved from team knowledge base:

→ Tom's pricing research (847 tokens — saved ~6,800)

→ Jordan's onboarding drop-off analysis (623 tokens — saved ~5,200)

Quota: ████████░░ 68% used • resets in 4h 12m

Background task: PRD-47 gap analysis queued ↗

84%
of technical workers use AI daily
75%
say tools focus too much on individuals
~300K
tokens saved weekly per 10-person team
+15%
effective quota extension

Open Source

Read every line. The MCP server, CLI, and hooks are fully open. No black boxes handling your team's knowledge.

View on GitHub

Bring Your Own Keys

LLM calls go directly from your machine to your provider. Evols never proxies or stores your inference traffic.

Self-Hostable

Run Evols on your own infra. Your team's knowledge graph never leaves your environment if you choose not to.

Self-host docs
The problem

Six ways teams waste
their collective AI investment

AI tools are built for individuals. Teams using them collectively suffer compounding failures that no single tool today addresses.

Handoff Tax

Context built once, rebuilt constantly

PM research, engineering decisions, UX insights — every teammate rebuilds from scratch. The same 12,000 tokens of context compiled daily across every role.

Invisible Waste

Duplicate work nobody sees coming

Two engineers solve the same infra problem. Three PMs research the same competitor. Work collides at review — after the tokens are burned.

Quota Blindness

Capacity burns or expires, both wasted

Some teammates hit session lockouts mid-task. Others let quota reset unused. No tool shows collective AI capacity across the team.

Low-Value Output

Polished output, shallow substance

AI drafts look complete. Teammates spend time verifying, rewriting, clarifying — the hidden rework tax on every AI-assisted deliverable.

Tool Fragmentation

Debugging across too many layers

Agentic systems span models, orchestrators, APIs, logs, dashboards. When something breaks, engineers reconstruct what happened from scratch.

Cost Blowups

Token costs grow faster than value

Teams underestimate how fast inference costs scale. Productivity gains get erased by optimization work and unplanned budget pressure.

The solution

One install. Everything connects.

No manual configuration. Evols configures hooks, MCP server, skills and team context.

terminal

$ curl -fsSL https://api.evols.ai/api/v1/install/script | sh

$ evols login

$ evols install

✓ Hooks registered • MCP server active • Team context loaded

✓ Done. Your team's knowledge base is ready.

01

Session starts

Evols fires the SessionStart hook. Team knowledge base context is injected immediately. No cold start. No accumulation period. Day one.

02

Every prompt, enriched

UserPromptSubmit hook checks for redundant work. Injects relevant prior context. Tracks session token usage client-side in real time.

03

Session ends, team gets smarter

Stop hook syncs outcomes to the team knowledge base. StopFailure hook detects rate limits and queues work for the next window.

Capabilities

Four capabilities.
One compounding system.

Day one
full context

Zero Cold Start

New teammates inherit the team knowledge graph on day one. No setup, no accumulation period — full context from the first session.

~8×
token efficiency

Auto-Compiled Knowledge

Every AI session contributes to a shared team knowledge base automatically. Query it instead of rebuilding it — at 8× fewer tokens.

0
duplicate sessions

Redundancy Prevention

Detect duplicate AI work before tokens are burned — not after the work collides at code review or the decks land in the same meeting.

+15%
effective quota

Quota Visibility

See collective team AI capacity in real time. Redirect expiring quota to backlog tasks before it resets unused.

SOC 2
in progress

Governance & Access

Project-level and role-level context permissions. Teams control who sees what knowledge — built for orgs that handle sensitive context.

1 cmd
to activate

Works Where You Work

One CLI install activates everything. MCP server and hooks are wired automatically into Claude Code, Cursor, Zed, Codex, and Antigravity.

FAQ

Common questions

What is Evols AI?

Evols is a team AI brain that gives every member shared context across Claude Code, Cursor, Zed, and other AI coding tools. It eliminates duplicate work, provides zero cold start for new teammates, and shows collective AI quota usage in real time.

How does Evols reduce AI token costs?

Evols stores AI session outputs in a shared knowledge graph. Instead of each teammate compiling the same context from scratch, they retrieve it at approximately 8× fewer tokens per session — cutting redundant usage across the whole team.

What AI coding tools does Evols work with?

Evols works with Claude Code, Cursor, Zed, GitHub Copilot (Kiro), Cline, and Codex via a single CLI install that registers MCP server hooks automatically.

What is the AI handoff tax?

The handoff tax is the wasted time when context built in one AI session cannot transfer to the next person. A developer's findings, decisions, and reasoning disappear when the session closes — forcing every teammate to start from scratch and compile the same tokens over and over.

How do I install Evols for my team?

Run: curl -fsSL https://api.evols.ai/api/v1/install/script | sh, then evols login and evols install. Hooks and MCP server are registered automatically into Claude Code, Cursor, and Zed.

Validation

The gap is publicly named
at the highest level

"I think there is room here for an incredible new product instead of a hacky collection of scripts."

AK
Andrej Karpathy
AI Researcher • April 2026

"We're stopping at individual productivity. One department doesn't know what the other one does. That's where it cracks."

SP
Sven Peters
AI Evangelist, Atlassian • March 2026
📰

Token exhaustion documented by BBC, Forbes, MacRumors — March 2026

💡

VCs calling team context infrastructure "the next big thing in AI" — Forbes, April 2026

🔴

GitHub Copilot Workspace shut down. No replacement exists.

Stop rebuilding what
your team already knows

Sessions should compound, not disappear.

Active with Claude Code, Copilot, Kiro, Cursor, and Cline