-
Notifications
You must be signed in to change notification settings - Fork 15
feat/nanobot-integration #6
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
Merged
+14,575
โ139
Merged
Changes from 17 commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
3119c96
feat/nanobot-integration
LarFii 985b142
fix lint
LarFii 01754d7
fix: resolve react-hooks/exhaustive-deps warnings breaking CI build
LarFii 6d4b29d
fix: remove invalid @typescript-eslint/no-explicit-any eslint-disableโฆ
LarFii 541502c
fix: replace Chinese text in SKILL.md example with English
LarFii f038f57
feat: nanobot integration with litewrite tools and API endpoints
893375e
added deepresearch feature, and enabled telegram bot connection
zzhtx258 7158cd1
fix lint
LarFii 2be6057
Merge pull request #7 from HKUDS/feat/nanobot-deep-research
LarFii 36bfa9c
fix: security hardening for nanobot integration
LarFii 2ca39fc
fix lint
LarFii 0edf7f8
feat: nanobot bingxi local changes - tools, session, media, import, aโฆ
536d2c3
feat: complete Telegram channel support with message splitting and fiโฆ
LarFii 662aaee
Update telegram.py
LarFii 7c7c714
Merge origin/feat/nanobot-integration into feat/nanobot-bingxi
ee15111
Merge pull request #8 from HKUDS/feat/nanobot-bingxi
LarFii 88805b5
fix
08443a5
fix: resolve race conditions between initializingDocs and HTTP handlers
LarFii 62b10ed
fix: skip project validation when list API fails (missing ownerId)
LarFii 0346ab4
fix: guard GET /doc init await & wire directApply through /api/chat/run
LarFii 92d2916
fix: restrict directApply to authenticated internal callers
LarFii 184e7fb
fix: forward X-Internal-Secret when proxying to ai-server /run-sync
LarFii File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
The new
directApplyflag is documented as the switch to bypass shadow documents, but it is never read or forwarded intoChatService.run/ToolContextfor the streaming/api/chat/runendpoint. As a result, API consumers that setdirectApply: truewill still get shadow-document edits instead of direct writes, which contradicts the fieldโs contract and breaks the intended integration flow. This should be wired through toChatService.run(or removed if unsupported) so the flag actually affects edit behavior.Useful? React with ๐ย / ๐.