Skip to content

docs: improve README - #2

Open
webbrain-one wants to merge 1 commit into
aspekts:mainfrom
webbrain-one:webbrain/readme-improvement
Open

docs: improve README#2
webbrain-one wants to merge 1 commit into
aspekts:mainfrom
webbrain-one:webbrain/readme-improvement

Conversation

@webbrain-one

@webbrain-one webbrain-one commented Aug 12, 2026

Copy link
Copy Markdown

Makes one small, focused improvement to the existing README.

Summary by CodeRabbit

  • Documentation
    • Corrected the example API request to use the proper HTTP method, endpoint, port, JSON header, and cookie structure.

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The README adds two leading blank lines and corrects the example API request to use POST, port 8000, JSON content type, and structured cookie and formkey fields.

Changes

README API example

Layer / File(s) Summary
Correct API request example
README.md
The example request now uses the /chat/capybara endpoint on port 8000, a JSON content-type header, and corrected cookie and formkey fields. The README also begins with two blank lines.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the README documentation update, which matches the main change in the pull request.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@coderabbitai coderabbitai 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.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 55: Update the README curl example to include the required bot field in
its JSON request body, using the expected bot identifier while preserving the
existing cookie, formkey, and message fields.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 514994ae-4c79-4172-9aa9-f9627deccdd3

📥 Commits

Reviewing files that changed from the base of the PR and between 7785ab6 and 0156f12.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
### Example
```bash
curl http://127.0.0.1/chat/capybara -d '{"Cookie: m-b=xxxx" , "formkey: xxxxx", "message":"What is the meaning of life?"}'
curl -X POST http://127.0.0.1:8000/chat/capybara -H "Content-Type: application/json" -d '{"cookie": "m-b=xxxx", "formkey": "xxxxx", "message": "What is the meaning of life?"}'

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Include the required bot field in the request body.

api.py:17-21 declares bot as required, and api.py:23-88 reads options.bot. This request omits the field, so FastAPI returns HTTP 422 before the handler runs.

Proposed fix
-curl -X POST http://127.0.0.1:8000/chat/capybara -H "Content-Type: application/json" -d '{"cookie": "m-b=xxxx", "formkey": "xxxxx", "message": "What is the meaning of life?"}'
+curl -X POST http://127.0.0.1:8000/chat/capybara -H "Content-Type: application/json" -d '{"bot": "capybara", "cookie": "m-b=xxxx", "formkey": "xxxxx", "message": "What is the meaning of life?"}'
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
curl -X POST http://127.0.0.1:8000/chat/capybara -H "Content-Type: application/json" -d '{"cookie": "m-b=xxxx", "formkey": "xxxxx", "message": "What is the meaning of life?"}'
curl -X POST http://127.0.0.1:8000/chat/capybara -H "Content-Type: application/json" -d '{"bot": "capybara", "cookie": "m-b=xxxx", "formkey": "xxxxx", "message": "What is the meaning of life?"}'
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 55, Update the README curl example to include the required
bot field in its JSON request body, using the expected bot identifier while
preserving the existing cookie, formkey, and message fields.

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.

1 participant