wingsofsky

Longkeep — AI skill for Claude Code

AI community

Work with AI coding agents on long projects: rules, decisions and plans live as plain Markdown in your repo, so Claude Code, Codex, Gemini CLI or Cursor picks up where the last session stopped.

How to install Longkeep

This entry records only its repository, not the path inside it, so there is no exact command to give. Open wingsofsky/longkeep and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Longkeep does

Work with AI coding agents on long projects: rules, decisions and plans live as plain Markdown in your repo, so Claude Code, Codex, Gemini CLI or Cursor picks up where the last session stopped. Optional: hand subtasks to other agent CLIs with a full record, a snapshot to roll back to and a verdict on each; search past conversations.

Alternatives in AI

  • Late CLI — High-performance AI agent for long-horizon tasks and local models 442 ★
  • Codeflow — OpenVibeCoding is the command tower for AI engineering: plan, delegate, track, resume, and prove long-running 206 ★
  • Zissa Wiki — Zissa Wiki — an LLM-maintained research knowledge base in plain markdown, operated via Claude Code 56 ★

README

Longkeep

**Work with AI coding agents on long projects.**

[![CI](https://github.com/wingsofsky/longkeep/actions/workflows/ci.yml/badge.svg)](https://github.com/wingsofsky/longkeep/actions/workflows/ci.yml)

Longkeep keeps the context of a long project in a complete set of documents, not in any one account, agent or environment. The documents are the contract: every agent session reads them before it starts and follows the same rules, so you can switch accounts, agents or machines and carry on where the last session stopped. The repository contains four modules: context, sessions, delegate and folder. Each module installs on its own, so you choose the ones you need and download only those.

With the delegate module, your main agent hands a subtask to another agent CLI on your machine, and gets three things that running `grok -p` by hand does not give you: a full record of every task (the brief, the transcript and what changed), a snapshot taken before the executor touches your project, so you can roll back, and a check, since the result stays unaccepted until you or your agent read the diff and the test output and record a verdict.

The repository also records what one maintainer learned running long projects with AI agents: keeping the contract short, what counts as done, reviewing with a fresh session or another vendor's model, keeping your own leanings out of a subagent's brief, when subagents can run in parallel, and how to brief a headless agent and check what it hands back. The details are in [working with AI agents](modules/context/en/longkeep-context/references/working-with-ai-agents.md) and [delegation practices](modules/delegate/skills/longkeep-delegate/references/delegation-practices.md).

[中文说明](README.zh-CN.md)

What each module solves

A new agent session knows only the files it reads. On a long project that causes four problems, and each module answers one of them:

Problem Module
A new session, or a new account, forgets the ru