codex-history-ingest

Ingest Codex conversation history into the Obsidian wiki.

Updated Feb 2, 2016
One-click install
npx skills add https://github.com/zjykzk/blog --skill codex-history-ingest-zjykzk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-history-ingest
Source: https://github.com/zjykzk/blog/tree/main/.agents/skills/codex-history-ingest
Command: npx skills add https://github.com/zjykzk/blog --skill codex-history-ingest-zjykzk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ingest Codex CLI conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Codex sessions for knowledge, import their ~/.codex folder, extract insights from previous coding sessions, or says things like "process my Codex history", "add my Codex conversations to the wiki", or "what have I discussed in Codex before". Also triggers when the user mentions .codex sessions, rollout files, session_index.jsonl, or Codex transcript logs.

Core Features & Use Cases

  • Ingest multi-session Codex history to distill durable knowledge for Obsidian
  • Support delta-based ingestion by comparing manifests and file metadata
  • Redact sensitive content and surface recurring topics with provenance markers

Quick Start

Instruct the system to ingest Codex history into the Obsidian wiki using the default append mode.

Frequently Asked Questions about codex-history-ingest

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

FAQPage Schema
How do I import Codex CLI conversation history into an Obsidian wiki?

Yes, the ingestion workflow supports delta-based processing by comparing manifests and file metadata, ensuring only new or modified Codex session data is imported into Obsidian rather than reprocessing the entire history.

Can I redact sensitive content when importing Codex transcripts into Obsidian?

Yes, the Codex history ingestion workflow includes privacy redaction features to sanitize sensitive content before it is written to the Obsidian wiki, ensuring confidential data remains protected during the knowledge extraction process.

How does Codex session clustering work when extracting insights for Obsidian?

The ingestion workflow applies topic clustering to analyze multi-session Codex transcripts, surfacing recurring themes and adding provenance markers to trace the extracted knowledge back to the original rollout files.

Do I need an existing Obsidian vault to import my Codex history?

Yes, an Obsidian wiki or vault is required as the destination for the ingested Codex session data. The workflow operates in append mode by default, adding distilled knowledge and topic insights directly into your existing wiki structure.

What Codex files are required for Obsidian history ingestion?

The workflow processes the ~/.codex directory, specifically targeting rollout files and session_index.jsonl logs. These multi-session transcript files contain the conversation data needed to extract insights and generate knowledge for Obsidian.