duzgunberke/ekip

Claude plans and reviews. Agents on other quotas do the work, each starting from the project's own memory.
English · Türkçe
> [!NOTE]
> Status: v1.1, used every day by its author on 15 projects. macOS first; the hub runs on any Linux VPS with Docker.
## Why
Claude Code's limit goes mostly to reading: files, logs, history, the same context again in every
session. ekip changes who does what:
Claude only decides. It understands the request, splits it, picks a worker for each part and
reviews the result. Reading and typing go to agents on other quotas: Antigravity, Codex, Copilot,
and about 60 free-tier models behind one endpoint.
Context is prepared once. Every project gets a memory: past sessions in a vector database, an LLM
wiki built from its docs, a code graph and its own skills. Workers start from that instead of
re-reading the repo.
You see everything. Each worker gets a terminal pane, each request becomes a task with live
steps, and a web panel shows runs, quotas and which model a new task would go to.
> [!TIP]
> 58% was the worst case: two days of building ekip itself and indexing 15 projects cold, work only the lead could do. The next day it was 81%.
> Measure it on your own work with ekip savings: it reads your Claude sessions, the workers' logs and the free pool, day by day.
## How it works
text
you › make two promo videos, fix what's left in storefront-web, add passkeys to payments-api
lead › 3 tasks · videos → Antigravity + film skill · storefront fix → Codex + its memory · passkeys → Copilot
reviews the diffs and renders, reports what shipped, what was verified, what is left
## Joins projects already in flight
You don't start from zero. When ekip registers a project it imports your past Claude Code sessions
for it, indexes the code into a graph, builds a wiki from its docs and extracts skills (how this
project builds, releases, fixes its usual problems). The first task you give is already informed by
everything you decided before.
Repeated work can become a real project-local Claude Code skill: ekip skill learn PROJECT reviews
run history and saves proposed SKILL.md files as candidates; inspect them with ekip skill candidates
and explicitly install one with ekip skill accept PROJECT NAME. ekip skill prune PROJECT only
reports stale TencentDB skills and never removes local skill files.
## Memory that follows your message
Run ekip review [--project NAME] [--base REF] to run relevant project checks and get two read-only reviews of changed files. Use --checks-only for checks alone, and ekip review profile NAME --refresh to regenerate the project's review lenses.
Open Claude in any folder and mention a project, even with a typo. ekip finds it, searches that
project's memory for your message and adds what matters, in about a second.
How memory works and why vectors matter, in depth: docs/memory.md and the author's
2023 article Vektörel Database nedir, ne işe yarar? (in Turkish).
## See it
Tasks · every request as live steps; a step that stops moving is flagged
Pools · who is limited, and where a new task would go
Code map · every project indexed into a graph
Terminal · the same tasks in a pane next to your Claude session