stacklok / stacklok/mecatl

sessions: search session transcripts to find past discussions

Open
#801 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
152
Forks
16
Avg merge
14h 48m
Merged PRs (30d)
536

Description

Problem

When I remember a topic but not the session where it was discussed, there is no way to locate that conversation from its transcript. Session inventory and replay metadata help identify sessions, but require already knowing which session to open.

Proposed capability

Add transcript-based session search across persisted sessions. Given a query, return matching sessions with enough context to select and resume/replay the right conversation.

Acceptance criteria

  • Search covers persisted session conversation/transcript content, including user and assistant messages.
  • Results identify the session and include a concise matching snippet/context.
  • Results can be narrowed by the existing session metadata where practical (for example workspace, date, or session type).
  • The search surface is available to the applicable clients/API and respects the session store's retention and access boundaries.
  • Define predictable behavior and documentation for empty queries, no matches, and stores/backends that cannot support efficient full-text search.

Notes

This complements #471 (session inventory and replay metadata) and #721 (pin/archive chats): inventory lets users browse known sessions, while transcript search lets them recover a session when they only remember the subject discussed.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the existing session inventory and replay metadata work referenced in #471, then trace the session store and the applicable API/client entry points. Define how transcript content, metadata filters, access boundaries, unsupported backends, empty queries, and no matches should behave. Done means persisted user and assistant messages can be searched and results identify sessions with concise context, with documentation and tests covering the stated behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend-api-design, search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.