kickoff

Coordinate Codex session start and resumption with a JSON manifest.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/almazom/agents_slash_skills --skill kickoff-almazom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kickoff
Source: https://github.com/almazom/agents_slash_skills/tree/main/kickoff
Command: npx skills add https://github.com/almazom/agents_slash_skills --skill kickoff-almazom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Simplify running or resuming long-running Codex sessions by wrapping the local kickoff runtime, maintaining a JSON stop-contract and an auto-continue loop, and supporting optional --goal, --thread-id, and --mattermost flags with a project-local fallback via kickoff-slash.

Core Features & Use Cases

  • Thin wrapper over /home/pets/TOOLS/kickoff_slash/kickoff-sdk to manage long-running Codex sessions.
  • Preserves stop-contract state and keeps auto-continue between turns for seamless interaction.
  • Supports optional --goal, --thread-id, and --mattermost, and falls back to kickoff-slash for project-local interactive hook mode when needed.

Quick Start

Start a new managed Codex run with kickoff-sdk by specifying --max-turns and a working directory path such as --cwd /abs/path/to/repo

Frequently Asked Questions about kickoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate long-running Codex sessions locally?

Resume Codex sessions through the kickoff runtime by passing --thread-id with your --cwd repo path. It preserves the stop-contract state and continues the auto-continue loop, picking up long-running workflows exactly where they left off.

Can I send Mattermost notifications during a Codex session?

Use kickoff-slash for project-local interactive hook mode when kickoff-sdk does not fit your workflow. Kickoff-slash provides a fallback mechanism to coordinate Codex session management directly within the repository context.

What is a stop-contract in Codex session management?

A stop-contract in Codex session management is a structured JSON manifest produced by the kickoff runtime. It preserves state and enables the auto-continue loop between turns, ensuring long-running sessions maintain seamless interaction without manual restarts.

What are the limitations of managing Codex sessions with kickoff?

Kickoff limitations include its dependency on a local runtime at /home/pets/TOOLS/kickoff_slash and its specific flag set like --max-turns and --cwd. It is designed for long-running Codex sessions requiring persistent state, not short isolated queries.