Skip to content

Fix indentation in README code example #4

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix indentation in README code example #4

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
250a370
Fix indentation in README code example
nightscape Nov 18, 2025
fe5767a
Fix indentation in README example code
nightscape Nov 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ Result: constant overhead. Whether you manage 10 or 1000 tools, the system promp

matches = await runtime.search_tool_docs("calendar events", limit=5)
for hit in matches:
print(hit["server"], hit["tool"], hit.get("description", ""))
print(hit["server"], hit["tool"], hit.get("description", ""))
Copy link

@gemini-code-assist gemini-code-assist bot Nov 18, 2025

Choose a reason for hiding this comment

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

medium

Thanks for fixing the indentation. While this makes the code syntactically correct, the relative indentation is 3 spaces, which is unconventional. For better readability and consistency with other Python examples in this file and the PEP 8 style guide, I suggest using a 4-space indent here.

Suggested change
print(hit["server"], hit["tool"], hit.get("description", ""))
print(hit["server"], hit["tool"], hit.get("description", ""))

```

3. **Zero-copy proxying** – every tool call stays within the sandbox, mirrored over stdio with strict timeouts.
Expand Down