codex-history-ingest

Ingest Codex CLI session logs into the Obsidian wiki with redaction.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Michael1Peng/watson --skill codex-history-ingest-michael1peng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-history-ingest
Source: https://github.com/Michael1Peng/watson/tree/main/.agents/skills/codex-history-ingest
Command: npx skills add https://github.com/Michael1Peng/watson --skill codex-history-ingest-michael1peng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill extracts knowledge from Codex CLI conversation history and distills it into the Obsidian wiki, prioritizing durable insights over operational telemetry.

Core Features & Use Cases

  • Ingest Codex history into the wiki to surface recurring concepts, decisions, and patterns.
  • Use the session index and rollout logs to map IDs to readable thread names and track progress.
  • Support incremental (append) and full ingests with privacy-aware redaction of sensitive content.

Quick Start

Run codex-history-ingest to start integrating your Codex history into the Obsidian wiki.

Frequently Asked Questions about codex-history-ingest

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

FAQPage Schema
How do I ingest Codex CLI conversation history into Obsidian?

To ingest Codex CLI history into Obsidian, run codex-history-ingest to distill durable knowledge from session logs and import your ~/.codex folder directly into the wiki.

Can I extract durable insights from past Codex coding sessions?

Yes, you can extract durable insights from past Codex sessions by mining rollout logs and the session index to surface recurring concepts, decisions, and patterns while filtering out operational telemetry.

Does ingesting Codex session logs into Obsidian redact sensitive content?

Yes, ingesting Codex session logs into Obsidian enforces privacy by applying privacy-aware redaction to sensitive text during both incremental and full history imports.

What is incremental ingest for Codex history and how does it work?

Incremental ingest for Codex history appends new session logs to existing wiki entries by using the manifest and session index to track progress and map IDs to readable thread names.

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

You need an Obsidian wiki setup to import Codex history, as the skill distills knowledge from your ~/.codex folder into the wiki structure to map session IDs to readable thread names.

What is the best way to mine past Codex sessions without including operational telemetry?

The best way to mine past Codex sessions without telemetry is using codex-history-ingest, which prioritizes durable knowledge over operational telemetry by mapping session IDs to readable thread names in Obsidian.