codex-history-ingest

Ingest Codex CLI conversation history into Obsidian wiki pages.

Updated Apr 27, 2014
One-click install
npx skills add https://github.com/Nirajkashyap/nirajkashyap.github.io --skill codex-history-ingest-nirajkashyap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-history-ingest
Source: https://github.com/Nirajkashyap/nirajkashyap.github.io/tree/main/.agents/skills/codex-history-ingest
Command: npx skills add https://github.com/Nirajkashyap/nirajkashyap.github.io --skill codex-history-ingest-nirajkashyap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ingest Codex CLI conversation history into the Obsidian wiki to distill durable knowledge from past sessions.

Core Features & Use Cases

  • Import Codex session data from ~/.codex into the wiki, surfacing reusable insights across projects.
  • Support incremental (append) and full ingests guided by .manifest.json and index files to keep the wiki up to date.
  • Apply privacy-conscious processing by redacting sensitive content and attaching provenance to updated pages.

Quick Start

Instruct the agent to ingest Codex history into the wiki using the wiki-history-ingest codex route.

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?

To import Codex CLI history into an Obsidian wiki, instruct the agent to use the wiki-history-ingest codex route. This processes your ~/.codex directory and surfaces reusable insights as wiki pages.

Can I incrementally append new Codex sessions to my knowledge management wiki?

Yes, you can append new Codex sessions incrementally to your knowledge management wiki. The process uses a .manifest.json and index files to track updates, keeping your pages current without full reprocessing.

Does Codex history ingestion support redacting sensitive content for privacy?

Yes, Codex history ingestion supports privacy-conscious processing by redacting sensitive content. It attaches provenance to updated wiki pages to ensure your distilled knowledge remains securely grounded.

What is the best way to mine Codex conversations for reusable project insights?

The best way to mine Codex conversations for reusable project insights is to ingest the session data from your ~/.codex folder. This distills durable knowledge from past sessions into organized wiki pages.

How does provenance anchoring work when ingesting session history into a wiki?

Provenance anchoring works by attaching source tracking metadata to updated wiki pages during session history ingestion. This grounds your distilled knowledge, ensuring each page traces back to its original Codex conversation.