Outdated "RAG Chatbot on your Docs" guide on langbase.com
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- cli, documentation
Research direction
Locate the source for the Langbase onboarding guides and inspect the BaseAI CLI v0.9.34 flow and generated config. Update the outdated Step 3, document changing the git.include glob patterns, and review the other onboarding guidance and code examples for the stated .env and OpenAI key requirements.
Written by the indexing model from the issue text.
Description
Couldn't find the docs source to make the changes myself, hence opening the issue.
Step 3 in the guide states:
STEP #3 Specify File Extensions
Next, it will ask you which files extensions you want to track. Since we are creating a memory for docs, you can provide a comma-separated list of file extensions like
.mdx,.mdto track markdown files.
However, the current BaseAI CLI (v0.9.34+) does NOT prompt for:
- Directory path to track
- File extensions to track
In version 0.9.34 (November 26, 2024), the memory configuration was simplified. This simplification was updated in the baseAI docs atleast but not in the Langbase onboarding guides leading to uncertainty and friction in the onboarding steps about whether we are using the correct version or if the setup is working properly.
Expected Fix
This among several other details like needing to create .env file for API keys, needing OpenAI keys to start deployment are few more issues which makes me think the onboarding guide is infact outdated and needs some love. Ideally, I would
- Remove Step 3 about file extensions prompt
- Add a step explaining how to modify the
git.includeglob patterns in the generated config file - Review all other onboarding guides and any code examples
- Dominant language
- TypeScript
- Stars
- 92
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 CommandCodeAI/langbase-examples
-
http 500 response Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
CommandCodeAI/langbase-examples#47 · 1 comment ·
All issues in CommandCodeAI/langbase-examples
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100