🔍
AI EngineeringTypeScript

Session History

by slopus

Session History is an AI Engineering skill for Claude Code, published by slopus in happy.

23.3K stars2K forkson slopus/happyAdded 2026/08/14Repository updated 2026/08/10
claude-codeclaude-desktopclaude-mobilecodexcodex-clihacktoberfest
Install in seconds
Install Session History
Copy Session History into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/slopus/happy/tree/main/.agents/skills/sessions ~/.claude/skills/sessions

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/slopus/happy.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
.agents/skills/sessions/SKILL.md in slopus/happy
Installs to
~/.claude/skills/sessions
Collection
One of 9 skills cataloged from this repository
Category
AI Engineering2451 skills

What Session History does

Session History searches and asks questions about past coding agent sessions across Claude Code, Codex, and Cursor. Use it to find what was worked on, what was tried before, or how a problem was investigated in previous sessions.

Session History is cataloged under AI Engineering on DirSkills. Session History comes from a repository tagged claude-code, claude-desktop, claude-mobile, codex and codex-cli.

Commands Session History provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

  • /sessions
  • /ce-sessions

Frequently asked about Session History

  • What else does slopus publish alongside Session History?

    Session History is one of 9 skills that DirSkills catalogs from slopus/happy, the repository it ships in. Its siblings there include Agent Browser, Control Flow and Local Development. Each one is a separate skill with its own page in this directory, installs the same way Session History does, and is maintained by slopus in that same repository. The rest of the collection is listed on the slopus/happy page.

  • How does Session History compare to other AI Engineering skills?

    Session History ranks #256 by stars among the 2451 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Session History against them. Open each page to compare what they document and how they install.

More from slopus/happy

Session History is one of 9 skills cataloged on DirSkills from slopus/happy.

See all 9 skills
🌐
2w ago

Agent Browser

Agent Browser opens pages in a real browser so an AI agent can test them. Use it when you need to interact with websites, fill forms, capture screenshots, or compare page states.
Automation
23.3K2K
🔀
2w ago

Control Flow

Control Flow analyzes and designs control flows and data structures, producing compact ASCII tree diagrams showing triggers, call chains, payload shapes, state mutations, and re-render effects. Use when asked to diagram, trace, visualize, or design a flow or data structure.
Quality
23.3K2K
🛠️
2w ago

Local Development

Local Development guides building, installing, testing, and running the Happy monorepo CLI, server, mobile app, and desktop app locally. Use when the user types /dev or asks how to build, start dev, install locally, or run a package.
DevOps
23.3K2K
🛠️
2w ago

Maintain

Maintain manages open source issue triage and project board workflows for the slopus/happy repository. It clusters issues, finds duplicates, checks if bugs are fixed on main, drafts closing comments, and always requires maintainer approval before posting or closing.
Automation
23.3K2K
📊
2w ago

Metrics & Grafana

Metrics & Grafana queries Prometheus metrics and manages Grafana dashboards as code for Happy infrastructure. Use it for live investigation, monitoring, or adding and modifying dashboard panels.
DevOps
23.3K2K
💡
2w ago

Office Hours

Office Hours is a manual-only YC-style product diagnostic that asks startup founders forcing questions to expose demand reality, and helps builders brainstorm side projects, hackathons, and open source, saving a design doc before any code is written.
AI Engineering
23.3K2K