golast

Recover the last actionable request from a crashed Codex session.

30|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/haibindev/golast --skill golast
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golast
Source: https://github.com/haibindev/golast/tree/main
Command: npx skills add https://github.com/haibindev/golast --skill golast

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Golast recovers the last actionable request from a crashed or compacted Codex session for the current workspace, enabling you to resume work exactly where you left off when starting a new session.

Core Features & Use Cases

  • Start-only gate: only triggers at the beginning of a fresh session.
  • Deterministic recovery: reads Codex's local state, locates the last meaningful user or assistant message, and returns a structured result.
  • Output fields & guidance: exposes fields like resolved_request, needs_more_context, supporting_context, and context_expanded_upward to drive next steps.

Quick Start

Type the golast trigger at the start of a new Codex session to resume the previous work and continue seamlessly.

Frequently Asked Questions about golast

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

FAQPage Schema
How do I recover the last actionable request from a crashed Codex session?

You can recover the last actionable request from a crashed Codex session by triggering the golast command at the start of a new session to read local state and surface the previous work context.

What fields are returned when restoring a previous session context?

Restoring a previous session context returns structured fields including resolved_request, needs_more_context, supporting_context, and context_expanded_upward to drive your next steps.

Can I resume a compacted Codex workspace session across related threads?

Yes, you can resume a compacted Codex workspace across related threads by triggering the recovery process at the beginning of a fresh session to locate the last meaningful user or assistant message.

Does session recovery work if I paste the skill link mid-session?

Session recovery only applies when you paste the skill link at the beginning of a fresh session, as the start-only gate prevents triggering after the session has already begun.

How does analyzing rollout data identify the last meaningful user message?

Analyzing rollout data identifies the last meaningful user or assistant message by deterministically reading Codex's local state to locate the final actionable request for the current workspace.