Update agent using langchain v3
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No files or tests are named; start by locating the agent implementation and the current LangChain v2 dependency. Review the LangChain v3 migration guidance, then verify that the agent, document splitter, and memory choices work with v3 and that the existing checks pass.
Written by the indexing model from the issue text.
Description
We still rely on langchain v2 while there is a new v3 since some time, introducing breaking changes. We should update our agent to use the newer version of langchain, and possibly update also some other choices that were made in past (e.g., the document splitter or the memory).
- Dominant language
- Python
- Stars
- 46
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SAP/STARS
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Pydantic issues Open
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
backend
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
backend
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100