Skip to content

Find a past session

Every prompt you send Docs Agent runs in a session. Search finds any session in your organization’s history, including work you never turned into a pull request, so you can pick up where you left off.

You can find a session two ways:

  • Search by keyword: match on what was said in the conversation.
  • Paste a link: jump from a pull request, merge request, or ticket to the session behind it.

You can also filter the sessions list by source or status.

  1. Open the editor. The Sessions section in the sidebar lists your sessions.

  2. Press ⌘K (Ctrl+K on Windows and Linux) to open search, or click the Search sessions button at the top of the sidebar.

  3. Type your query. Results open in a focused view centered on the page.

The Sessions list stays as it is while you search. Results appear in the focused view, not by filtering the list underneath. To close the view, press Escape, click outside it, or select a result. Your query stays in the search field so you can refine it.

Type at least three characters to search. Search matches your query against:

  • The session title
  • The title of the documentation pull request the session produced
  • The conversation: both your messages and the agent’s replies

Results are ranked best match first. Each result shows the session title and a snippet of the matching text, with the matched words highlighted. An attribution label tells you where the match came from:

LabelMeaning
you askedThe match is in one of your messages.
agent repliedThe match is in one of the agent’s replies.

Select a result to open that session in the editor.

Paste a URL into the search field to find the session it relates to. Search resolves these links:

Paste thisFinds
A GitHub pull request URLThe session triggered by that pull request, or the session that produced it
A GitLab merge request URLThe session triggered by that merge request, or the session that produced it
A Jira ticket URLThe session linked to that ticket
An EkLine session URLThat session directly

Link search matches exactly, so a single paste takes you to the related session or sessions. Search shows the matches and lets you choose one. It never opens a session for you.

You can paste a messy URL. A link that points at a pull request’s Files tab or a specific review comment still resolves. Self-managed hosts such as GitHub Enterprise and self-hosted GitLab work the same as github.com and gitlab.com.

The header of the search view reports how many results it shows and how many sessions matched, for example 50 of 214 sessions · best match first. The view shows up to 50 results. The second number counts everything that matched, not only the sessions already loaded in the Sessions list.

  • No matches: when nothing matches, the view says so and names your query.
  • Older sessions not searched: for a large history, keyword search covers the most recent sessions and shows a notice when older ones fall outside that range. Add more distinctive words to your query to surface the session you want.

Click Filter sessions (the filter icon next to the Sessions heading) to narrow the list:

  • Quick views: Needs attention shows sessions that an integration or a schedule started and that are not marked done, leaving out pull request reviews where the agent found no docs update was needed. Started by me shows sessions you started. One quick view applies at a time.
  • Source: shows sessions by where they started: Chat, GitHub, GitLab, Slack, Discord, Scheduled, Jira, or Journeys. You can select more than one. The menu lists only the sources among the sessions already loaded.
  • Hide done: hides sessions marked as done. To mark one, open its actions menu in the list and click Mark as done.

Filters apply to the sessions already loaded in the list, not to your whole history. To search your whole history, use search by keyword. Click Clear all to remove every filter.

Built on Potluck Docs, our open source template.