gsd-thread

Manage persistent context threads for cross-session work with Codex integration via gsd-sdk and agent router.

Updated May 3, 2026

Search Tags:#context management #work organization #threading #cross-session work #Codex integration

Ready to run

npx skills add https://github.com/ThiagoVitale/endless-crystal --skill gsd-thread-thiagovitale

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-thread
Source: https://github.com/ThiagoVitale/endless-crystal/tree/main/.codex/skills/gsd-thread
Command: npx skills add https://github.com/ThiagoVitale/endless-crystal --skill gsd-thread-thiagovitale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gsd-sdk, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users manage persistent context threads for cross-session work, ensuring that work spanning multiple sessions remains organized and accessible.

Core Features & Use Cases

Persistent Context Threads: Create, list, close, or resume threads that store context for work that spans multiple sessions.
Thread Management: Easily manage threads to track progress, update status, and review information.
Use Case: For a developer working on a project that requires research, design, and implementation over several days, this Skill helps maintain a continuous workflow without losing track of progress.

Quick Start

To start a new thread, use the command: $gsd-thread <description>

Frequently Asked Questions about gsd-thread

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

FAQPage Schema

How do I manage persistent context threads for work spanning multiple sessions?▼

Persistent context threads are managed by creating, listing, closing, or resuming threads that store context for work spanning multiple sessions. This ensures cross-session work remains organized and accessible without losing progress.

Can I translate Claude Code syntax to Codex's agent router for interaction?▼

Yes, Claude Code syntax is translated to Codex's request_user_input and spawn_agent functions for interaction. This requires the gsd-sdk dependency to properly interface with Codex's agent router.

Do I need file system access to create and resume persistent work threads?▼

Yes, file system access is required for thread management. The Skill uses the file system to handle thread creation, listing, closing, and resuming operations for continuous work sessions.

What's the best way to start a new context thread for cross-session work?▼

To start a new context thread, use the command `$gsd-thread <description>` with a description of your work. This creates a persistent thread to track progress across multiple sessions.

Why does cross-session work lose context without persistent threading?▼

Cross-session work loses context without persistent threading because session data is typically ephemeral. Persistent threads store context so that research, design, and implementation progress over several days remains accessible and continuous.

Are there limitations when using gsd-sdk for Codex integration and thread management?▼

The Skill requires both gsd-sdk for Codex agent router interaction and file system access for thread management. Without these dependencies, thread creation, listing, closing, and resuming operations cannot function.