Codex Continuity Kit
Jayboss-lab/codex-continuity-kit
Preserve contexto e continuidadade em projetos com agentes de IA entre sessões
Ver no GitHubKit de documentação e templates em markdown para manter projetos com agentes de IA estruturados e contínuos entre sessões. Usa arquivos de memória estruturados para evitar perda de contexto quando sessões terminam ou falham, permitindo retomada limpa do trabalho.
Instalação
npx convez-ai Jayboss-lab/codex-continuity-kit1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Retomar trabalho de agentes de IA após interrupção de sessão
- Documentar decisões e próximos passos de projetos automatizados
- Facilitar handoff entre sessões de diferentes agentes ou equipes
- Manter memória estruturada de exploração e progresso do projeto
Veredito

Solução prática e minimalista para um problema real: perda de contexto entre sessões de agentes. Abordagem baseada em markdown puro é agnóstica e facilmente adotável, mas depende de disciplina manual para funcionar bem. Útil para equipes usando Codex, Claude Code ou Aider.
README
A tradução para o português deste README ainda está na fila.
Codex Continuity Kit
A practical documentation and template kit for keeping Codex and AI coding-agent projects safe, structured, and continuous across sessions.
Tagline: Stop losing context between agent sessions.
The Problem
AI coding agents like OpenAI Codex CLI, Claude Code, and Aider are powerful but stateless. When a session ends or crashes, the context — what was explored, what decisions were made, what files were touched, what the next step was — disappears. The next session wastes time re-exploring the same territory. Teams cannot pick up agent-driven projects cleanly.
The Solution
Use structured markdown files as reusable project memory. Fill them as you work. The next session — or the next team member — reads them and resumes without starting from scratch.
No CLI to install. No framework to adopt. No special tools. Just markdown files you commit alongside your code.
Quick Start
- Copy the templates you need from
templates/into your project root. - Rename them by removing
.templatefrom the filename (e.g.AGENTS.template.md→AGENTS.md). - Fill in the placeholders as you work.
- Commit them with your code. They are part of your project docs now.
Which templates do I need?
| Template | When to use it |
|---|---|
AGENTS.md | Once per project. Defines how agents should behave in this repo. |
SKILL.md | Once per reusable task pattern. Defines a skill the agent can invoke. |
CODEX_HANDOFF.md | After every session. Captures what happened and what's next. |
POST_RUN_REPORT.md | After significant milestones. Summarises decisions and rationale. |
GOAL_PROMPT.md | Before starting a new task. Structures the goal you feed to the agent. |
See docs/how-to-use-this-kit.md for a full adoption guide.
What this kit includes
- 5 templates for agent instructions, goal prompts, session continuity, and milestone reports
- 3 example projects showing how the templates look in practice
- 3 maintainer checklists for safe sessions, project continuity, and handoff hygiene
- Issue templates for requesting new templates or reporting problems
Examples
Browse examples/ for realistic, filled-in templates across three project types:
examples/basic-project/— A CLI task trackerexamples/ui-project/— A React component libraryexamples/research-project/— A data analysis repo
All examples use fictional projects. No proprietary or private data is included.
Compatibility
These templates are plain markdown with no executable code. They should work with:
- OpenAI Codex CLI (the original target)
- Claude Code
- Aider
- Any agent that can read markdown context files
- Human developers reading them directly
No guarantees are made for any specific agent. If a template doesn't work well with your tool, open an issue.
Contributing
See CONTRIBUTING.md.
New template suggestions, bug fixes, and example additions are welcome. This is a maintainer-maintained set of conventions, not a product.
License
Roadmap
See ROADMAP.md for planned additions and future directions.