Skip to content
devtwin

Introduction

devtwin is a local command-line tool that keeps what you know about a project, and how you like to work, in one private place on your machine. It then hands that context to whichever coding agent you open next.

The idea is to clone the developer, not just the repository. A repository tells an agent what the code is. It rarely says why a decision was made, what is still unknown, or where the last session stopped. devtwin keeps that knowledge between sessions and between agents.

Your first brief in five minutes

Section titled “Your first brief in five minutes”

You need Git and Node.js 22.13 or later. Clone the kit and check that it runs:

Terminal window
git clone https://github.com/sundharesan11/devtwin.git
cd devtwin
node bin/devtwin.mjs version

Then follow the Quickstart. It builds a throwaway repository in a temporary folder, onboards it and prints its brief: the short, source-linked summary you give an agent at the start of a session. If you just want to see the result, its fast path does everything in one paste.

What it gives you

Section titled “What it gives you”

Context that survives the session

Record facts, decisions, constraints and open questions for a project. Each new session starts from a short, source-linked brief instead of a blank page.

The same context for every agent

Claude Code and Codex read the same brief, through the same CLI. Switching agents does not mean re-explaining the project.

Lessons at the right moment

A lesson is one “do” or “don’t” tied to paths, packages or topics. The devtwin hook shows it to the agent when it reads or edits matching code. Join your org’s hub to share approved lessons with colleagues.

The right account per organization

Identity routing will pick the right GitHub and Slack account for each organization you work for. The guide covers the design and what exists today.

Your own harness

Keep a private personal profile, watch release announcements for your stack, and turn generic skill templates into your own private skills.

How you use it

Section titled “How you use it”
  1. Onboard a repository. devtwin reads a few files, such as the README and package manifest, and shows you what it would record. You approve that exact plan.
  2. Read a brief at the start of a session and give it to your agent, or let the bundled devtwin-resume skill fetch it.
  3. Record decisions and findings as you work, so the next session has them.
  4. Learn as you go. Agents propose lessons at the end of a task. You accept the ones worth keeping, for yourself or for your team.
  5. Export a handoff when you want to pass selected records to someone else.

Every write is previewed first and applied only when you ask. See How it works for the full picture.

Your data stays on your disk

Section titled “Your data stays on your disk”

The kit you clone is public code: the CLI, schemas, generic templates and tests. Everything you add, such as project records, your profile and drafts, lives in separate private folders outside that clone, with private file modes. Nothing is synchronized from your private store into the public kit, and nothing is sent to a hosted service. If you join an organization hub, a Git repository your organization hosts, only the lessons you accept and short “working on” notes go to it.

devtwin also never writes into the project repositories it reads. What it learns goes into your private store, not into the repository.

Where to go next

Section titled “Where to go next”
QuickstartOnboard a throwaway project and read your first brief.
InstallationRequirements, the self-check and a devtwin alias.
How devtwin comparesAGENTS.md and CLAUDE.md, built-in agent memory, and devtwin side by side.
Use it with coding agentsInstall the bundled skills for Claude Code and Codex.
Lessons and agent hooksDeliver lessons to agents as they work, and review what they propose.
Organization hubShare approved lessons and working-on notes with colleagues.
Personal harnessSet up your profile and make private skills from templates.
FAQShort answers to the questions people ask first.

The source is on GitHub under the Apache-2.0 license.