01
Plan the work
Shape issues with workflow statuses, priorities, labels, assignments, relations, sub-issues, comments, and attachments.
Local issue & project workspace
Project work,
local by default.
Clone keeps issues, projects, planning, and automation beside the repository they belong to. Your records stay in SQLite. No hosted account required.
Run from your repository
npx @andrestobelem/clone --local
Creates ./.clone/Separate workspace per repositoryIgnore .clone/ in Git
View on npm
macOS · Linux · Windows
Product
Issues
All issuesActiveBacklogFilter
In progress 3
PRO-18Package the desktop release◆AM
PRO-22Polish responsive navigation◆JM
Todo 4
PRO-27Publish the first release◆SK
PRO-31Write the migration guide◆AM
Local and running127.0.0.1:4173
Issues✦Projects✦Cycles✦Views✦Automation✦Snapshots
What is inside
The planning surface,
without the platform overhead.
Clone brings the parts of a modern issue tracker that matter for focused work into one local process.
02
See the horizon
Coordinate projects, milestones, dependencies, cycles, progress, and updates without leaving the workspace.
03
Built for agents too
The browser and CLI use the same actions. People and external agents keep distinct actor identities and history.
The local contract
You own the work.
Clone holds the shape.
One process
The browser UI, CLI, and scheduler use the same Python actions and local records.
One workspace per repository
Run Clone with --local. SQLite, snapshots, attachments, and backups stay in that repository's .clone/ directory.
Complete snapshots
Stable JSON snapshots make records reviewable, portable, and compatible with Git.
Loopback only
The server binds to 127.0.0.1 by default. Clone is personal software, not a hosted collaboration service.
Open source · MIT
Keep the plan
close to the work.
Clone is available as a public npm package. Run it with npx and --local to create an independent workspace inside the current repository.