-
Notifications
You must be signed in to change notification settings - Fork 2k
docs: Add 'Connect Your Custom RAG Pipeline to a Letta Agent' tutorial - [DRAFT] #3042
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
cpfiffer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly the only comment I have is about the use of the term stateless, I would stick with just a "simple" agent rather than a stateless one, as it's hard to make a genuinely stateless agent in Letta.
fern/pages/tutorials/letta-rag.mdx
Outdated
| ### Step 2: Create a "Stateless" Letta Agent | ||
|
|
||
| For the standard RAG approach, the Letta agent doesn't need any special tools or complex instructions. Its only job is to answer a question based on the context we provide. We can create this agent programmatically using the Letta SDK. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Stateless is a difficult term to use here, because very few Letta agents are truly stateless. It takes quite a lot of work to turn off all the things we add to your agents. A more accurate term here would be "simple".
|
Are we happy with this one? I like it. |
Please describe the purpose of this pull request.
Is it to add a new feature? Is it to fix a bug?
How to test
How can we test your PR during review? What commands should we run? What outcomes should we expect?
Have you tested this PR?
Have you tested the latest commit on the PR? If so please provide outputs from your tests.
Related issues or PRs
Please link any related GitHub issues or PRs.
Is your PR over 500 lines of code?
If so, please break up your PR into multiple smaller PRs so that we can review them quickly, or provide justification for its length.
Additional context
Add any other context or screenshots about the PR here.