I kept re-explaining my project to Codex, so I built Cricino

Description and use

Cricino streamlines project context handoff between Codex sessions by centralizing decisions and pending work, though it does not enforce checks or guarantee code quality.

Problem

The author struggled to remember project decisions and handoffs between Codex sessions, leading to repeated explanations and scattered reasoning.

Outcome

Cricino reduces the need for repeated explanations, centralizes decision tracking, and improves handoff quality between Codex sessions, though it does not enforce checks or guarantee code correctness.

Workflow

• 1. Run Cricino installer to ask project-specific setup questions.
• 2. Define project goal, scope, approval actions, checks, and storage locations for decisions and unfinished work.
• 3. Create a concise entry record summarizing current decision, parked work, next task, and verification status.
• 4. At session end, update the handoff record with changes, checks run, failures, and next steps.
• 5. In the next Codex session, read the updated record to resume work without re-explaining context.

Evidence

I was still the person connecting all the pieces.

Source

The assistant has something concrete to read. I have something concrete to review.

Source

Cricino includes a guide, templates and an optional installer.

Source

It doesn't guarantee correct code, compliance, or a bug‑free release.

Source