Skip to content

docs: Document cross-session conversation recall (session_search)#819

Merged
MervinPraison merged 1 commit into
mainfrom
claude/issue-813-20260623-1139
Jun 23, 2026
Merged

docs: Document cross-session conversation recall (session_search)#819
MervinPraison merged 1 commit into
mainfrom
claude/issue-813-20260623-1139

Conversation

@MervinPraison

Copy link
Copy Markdown
Owner

Fixes #813

New page docs/features/cross-session-recall.mdx documents the session_search tool that graduated from a stub to a working feature in PraisonAI PR #2187. Updated docs/features/bot-default-tools.mdx and docs.json.

Generated with Claude Code

- Add docs/features/cross-session-recall.mdx with session_search graduated
  from stub (PraisonAI PR #2187): discovery/scroll/browse modes, diagrams,
  parameter tables, return shapes, best practices, related links
- Update docs/features/bot-default-tools.mdx: rename section and fix
  session_search description from 'Placeholder only' to working tool
- Update docs.json: register cross-session-recall under State & Sessions

Co-authored-by: Mervin Praison <MervinPraison@users.noreply.github.com>
@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@MervinPraison, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 8 minutes and 31 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9528d114-f9d5-4dd9-920b-cfba5b7f032c

📥 Commits

Reviewing files that changed from the base of the PR and between e201d44 and b60d1a1.

📒 Files selected for processing (3)
  • docs.json
  • docs/features/bot-default-tools.mdx
  • docs/features/cross-session-recall.mdx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/issue-813-20260623-1139

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces documentation for the new 'Cross-Session Recall' (Session Search) feature, updating the bot default tools list and adding a comprehensive guide on how agents can search past conversation transcripts. Feedback on the documentation highlights critical discrepancies with the current codebase: the documented Python examples for session_search do not match its actual function signature (missing required arguments and using unsupported parameters), and the referenced SearchableSessionStoreProtocol and its associated methods are not yet implemented in the SDK.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment on lines +55 to +59
# 2. Scroll — read ±N messages around an anchor
session_search(session_id="abc-123", around_message_id="42", window=10)

# 3. Browse — most recent sessions ("what was I working on?")
session_search()

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The documented usage of session_search does not match its actual implementation in praisonaiagents/tools/session_tools.py.

In the codebase, session_search is defined as:

def session_search(query: str, limit: int = 10, session_id: str = None) -> str:

This leads to two issues in the examples:

  1. query is a required positional argument (it has no default value). Therefore, calling session_search() with no arguments (line 59) or calling it without query (line 56) will raise a TypeError: missing 1 required positional argument: 'query'.
  2. The parameters around_message_id and window (line 56) are not defined in the function signature, which will raise a TypeError: got an unexpected keyword argument.

Consider updating the examples to match the current signature of the tool.

# 2. Search within a specific session
session_search(query="billing migration", session_id="abc-123", limit=10)

Comment on lines +281 to +283
## Advanced: `SearchableSessionStoreProtocol`

The default store implements `SearchableSessionStoreProtocol`, a separate `runtime_checkable` protocol that adds search to any session store backend.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The advanced section references SearchableSessionStoreProtocol and methods like store.search(), store.window(), and store.recent(). However, these are not defined in praisonaiagents/session/protocols.py or implemented in praisonaiagents/session/store.py (the default store only implements SessionStoreProtocol and lacks these search/window/recent methods).

If these features are part of an upcoming PR or a different package version, please clarify that in the documentation to avoid confusing users who try to use them with the current version of the SDK.

@mintlify

mintlify Bot commented Jun 23, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
praisonai 🟢 Ready View Preview Jun 23, 2026, 11:55 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@MervinPraison MervinPraison merged commit 68d9a3e into main Jun 23, 2026
20 checks passed
@MervinPraison MervinPraison deleted the claude/issue-813-20260623-1139 branch June 23, 2026 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: Document cross-session conversation recall — session_search graduated from stub (PraisonAI PR #2187)

1 participant