Results for “session-id”

Search locally saved Codex session history stored in SQLite and session_index.jsonl, with filters for provider, time range, and archived status.

Search and retrieve past work from claude-mem's persistent cross-session memory database using a three-layer workflow: search, timeline, and fetch.

Search and analyze conversation history stored in session JSONL files using jq and shell commands.

Maintains a persistent session memory across Claude sessions by loading project state at startup, capturing errors and decisions during work, and writing structured handoff summaries at session end.

Generates a copy-paste handoff prompt for starting a new session by collecting current session context, project files, and git state.

Start-of-session routine — load context, check state, suggest next task. Use at the beginning of a fresh session or after a context reset.

Search and explore coding session history across multiple AI agents, including Claude Code, Codex, Cursor, Gemini CLI, and Aider, with commands for indexing, searching, viewing, and exporting conversations.

Keeps long AI sessions on track by tracking decisions, detecting scope creep, and flagging drift before it costs work.

At the start of a session, reads the session baton file to restate the goal and next task, and opens any doc listed under "Read first" before confirming the next step with the user.

Runs an interactive weekly review session to assess accomplishments against stated goals, identify missed items, and plan the next week with a structured report and accountability question.

Simulator.Company meeting specialist — scheduling and configuring meetings / video / SIP rooms. In Simulator a meeting is an actor of the Events system form with data.scheduleMeeting=true (no chatType); the actor IS the room. Use when the user wants to "schedule a meeting", "create a call/video room", "set up a recurring meeting", "make a persistent meeting room", "add an agenda", "set a moderator", "get a join link", "invite people to a meeting", or work with SIP/video rooms. Activate on "schedule a meeting", "create a meeting", "set up a call", "recurring meeting", "weekly meeting", "standing room", "meeting agenda", "join link", "invite to the meeting", "запланувати зустріч", "створи мітинг", "повторювана зустріч", "щотижнева зустріч", "постійна кімната", "агенда зустрічі", "посилання на зустріч", "запроси на мітинг", "запланируй встречу", "создай митинг", "повторяющаяся встреча", "постоянная комната", "агенда встречи", "ссылка на встречу". Also for reading a call's transcription — "transcription", "what w

Analyzes past agent sessions to identify recurring failures and skill gaps, then automatically creates or patches skills and runs self-evolution to fix them, tracking improvement over time.

Local CLI issue tracker for todos, follow-ups, structured records, and the canonical pattern for decomposing multi-step work into a parent + subissues with acceptance criteria, dependency edges, and priority. Use when the user mentions a task to remember, a bug to track, an open question, anything that needs to outlive the current turn, or when planning multi-heartbeat work that needs `chainlink issue ready`-driven pickup across sessions. Includes guidance on writing descriptions future-you can act on (handles, success path, failure path) and idempotency tactics for actions that might fire twice (boundary firing, overlapping heartbeats, retried subagent completion). Pairs with five-whys (chainlink is the storage backend for RCA trees). Storage is local — issues live under a `.chainlink/` directory in the operator's repo.