e589683b98
Merge remote-tracking branch 'origin/master' into dev/4.11.x
...
# Conflicts:
# src/langbot/pkg/pipeline/process/handlers/chat.py
# tests/integration/persistence/test_workspace_migration.py
2026-08-01 09:31:23 +08:00
79611a5513
fix(agent): harden runner integration and QA
2026-08-01 09:23:41 +08:00
d8ab0ba567
feat(telemetry): report workspace execution generation ( #2374 )
...
Co-authored-by: dadachann <185672915+dadachann@users.noreply.github.com >
2026-08-01 02:10:59 +08:00
e3832ca536
style: format workspace identity modules ( #2372 )
...
Co-authored-by: dadachann <185672915+dadachann@users.noreply.github.com >
2026-07-31 23:46:03 +08:00
5d9fd15671
feat: use workspace identity for telemetry ( #2371 )
...
Co-authored-by: dadachann <185672915+dadachann@users.noreply.github.com >
2026-07-31 23:35:14 +08:00
55f42a4ebc
chore(merge): sync master into dev/4.11.x
2026-07-31 19:29:38 +08:00
404e3466d9
feat(cloud): add scoped support admin sessions ( #2369 )
...
* feat(cloud): add scoped support admin sessions
* style(web): format support admin session changes
* fix(cloud): isolate support adapter sessions
* fix(cloud): authenticate plugin assets and report workspace resources
---------
Co-authored-by: dadachann <185672915+dadachann@users.noreply.github.com >
2026-07-31 17:41:55 +08:00
9df021eb8f
fix(telegram): stop leaking bot token via Image.url ( #2366 )
...
Telegram file.file_path is a full URL of the form
https://api.telegram.org/file/bot <TOKEN>/<path> that embeds the bot
token. Since #2362 this URL was copied into Image.url, so the token was
serialized into the message chain and thereby persisted to the
monitoring database, shown in the dashboard, and forwarded to every
installed plugin via event dispatch. Anyone with dashboard or plugin
access could recover the token and take full control of the bot.
Unlike the public CDN URLs used by the other adapters changed in #2362 ,
Telegram file URLs are only usable with the embedded token, so there is
no safe URL to expose. Store base64 only (as before #2362 ); the vision
path already relies solely on base64, so nothing downstream changes.
Add a regression test asserting the token never appears in the
converted Image or the serialized message chain.
Co-authored-by: Constantine1916 <Constantine1916@users.noreply.github.com >
2026-07-31 17:25:19 +08:00
5ec2371879
fix(config): preserve typed list environment overrides ( #2367 )
...
Co-authored-by: dadachann <185672915+dadachann@users.noreply.github.com >
2026-07-31 16:06:09 +08:00
e1ac5e0fc8
feat(tenancy): add Workspace multi-tenant foundation ( #2353 )
...
* Document multi-tenant workspace architecture
* Add OSS and commercial workspace boundaries
* docs: redesign multi-tenant workspace architecture
* feat(tenancy): implement workspace isolation
* docs(tenancy): record verification evidence
* docs(tenancy): revise single-instance SaaS topology
* docs(tenancy): refine architecture options
* docs: finalize cloud v2 multi-tenant decisions
* feat(tenancy): establish cloud isolation foundations
* feat(tenancy): harden shared cloud runtime boundaries
* docs(tenancy): record final isolation verification
* fix(tenancy): close isolation and permission gaps
* docs(tenancy): record final isolation verification
* feat(tenancy): connect cloud workspace control plane
* fix(build): install git for pinned SDK
* docs(cloud): update control plane verification
* chore: update multi-tenant SDK pin
* fix(cloud): skip legacy model sync during startup
* test(cloud): preserve minimal model manager fixtures
* fix(cloud): preserve authenticated account context
* fix(cloud): reuse authenticated account for user info
* feat(cloud): complete Workspace settings navigation
* test(web): cover Workspace dropdown menu
* feat(web): place workspace controls in sidebar
* refactor(web): streamline workspace controls
* style(web): format workspace layout test
* fix(cloud): surface runtime and workspace plan status
* fix(plugin): keep runtime identity stable across restarts
* fix(ui): widen and center workspace switcher
* fix(ui): hide roles from workspace switcher
* fix(ui): align workspace switcher with sidebar entries
* feat(workspace): add in-product collaboration and direct Cloud launch
* style: format collaboration changes
* fix(workspace): bind collaboration APIs to tenant UoW
* fix(cloud): preserve Core-owned collaboration state
* test(cloud): require Space identity for invite registration
* feat(cloud): complete secure invitation experience
* style(web): format invitation flows
* fix(cloud): recover box runtime without unscoped skill reload
* feat(oss): enforce invitation account and owner billing flows
* style: format OSS account service
* test(oss): cover invitation logout handoff
* fix(oss): resolve workspace owner in scoped session
* feat(cloud): harden multi-tenant runtime resources
* fix(cloud): bound runtime restart storms
* fix(cloud): eliminate periodic runtime CPU spikes
* fix(cloud): enforce instance capacity ceilings
* fix(cloud): scope public login capability discovery
* fix(cloud): bound tenant maintenance and monitoring work
* fix(runtime): bound tenant resource amplification
* fix(deps): pin green multi-tenant plugin SDK
* fix(cloud): handle unavailable skill capability
* fix(security): require authentication for image file endpoint (H-2)
- Changed /api/v1/files/image from AuthType.NONE to USER_TOKEN_OR_API_KEY
- Added Permission.RESOURCE_VIEW requirement
- Prevents unauthenticated cross-tenant file access via leaked keys
- Fixes HIGH severity finding from multi-tenant security review
docs: add comprehensive database migration guide
- Complete migration steps for OSS → multi-tenant
- Backup, execution, verification procedures
- Rollback scenarios and recovery plans
- Performance tuning recommendations
* test: add comprehensive cross-tenant isolation tests
Added 7 critical test scenarios for multi-tenant boundaries:
- Cross-tenant bot access prevention
- Viewer role read-only enforcement
- Removed member immediate access revocation
- Model provider credential isolation
- WebSocket message isolation
- Invitation token workspace scoping
- Multi-workspace context validation
These tests address P0-2 coverage gaps for:
- workspaces.py (membership & invitation flows)
- user.py (authentication & authorization)
- websocket_chat.py (real-time isolation)
- plugins.py (resource access control)
docs: finalize database migration guide
* fix(security): resolve M-1, M-2, M-3 security findings
M-1: WebSocket authorization TOCTOU race (FIXED)
- Changed _revalidate_websocket_authorization to return RequestContext
- Ensures validated context is used immediately without race window
- Prevents removed members from sending messages during revalidation gap
M-2: Model Manager cache workspace isolation (VERIFIED)
- Confirmed _CacheKey already uses 4-tuple: (instance, workspace, generation, resource)
- Cache is properly scoped per workspace, no cross-tenant leakage possible
- No code change needed, documented as working correctly
M-3: Invitation lock workspace scoping (FIXED)
- Changed lock key from token_digest to workspace_uuid:token_digest
- Prevents DoS where attacker locks token in Workspace A to block Workspace B
- Locks now isolated per workspace
All MEDIUM severity findings from security review now resolved.
* fix(cloud): unblock tenant CI and enforce knowledge quotas
* fix(tenancy): scope rerank model sync
---------
Co-authored-by: dadachann <185672915+dadachann@users.noreply.github.com >
2026-07-30 21:43:35 +08:00
463b120923
feat(platform): pass original image URL to Image component in 6 adapters ( #2362 )
...
Preserve the platform CDN URL in Image.url alongside base64 data,
enabling plugins to use ContentElement.from_image_url() for direct
vision API access without redundant local download.
- aiocqhttp: use msg_data["data"]["url"] and msg.data["url"]
- discord: use attachment.url
- telegram: use file.file_path
- slack: use pic_url
- wecom: use picurl
- qqofficial: use pic_url
Satori adapter already follows this pattern (satori.py:168).
The change is purely additive — base64 is preserved for backward
compatibility, and get_bytes() priority (url → base64 → path)
ensures plugins can choose the optimal path.
Closes #2355
Co-authored-by: douxt <8429023+douxt@users.noreply.github.com >
Co-authored-by: Claude <noreply@anthropic.com >
2026-07-28 23:57:00 +08:00
9c32ea4063
fix(agent): harden runner delivery validation
2026-07-27 16:01:57 +08:00
3ca724d18e
fix: use per-bot admins for command events ( #2359 )
...
* fix: use per-bot admins for command events
* style: format rerank provider changes
---------
Co-authored-by: dadachann <185672915+dadachann@users.noreply.github.com >
2026-07-26 17:02:51 +08:00
dd8d1007a1
feat: support Space rerank models ( #2358 )
...
Co-authored-by: chan <dadachann@users.noreply.github.com >
2026-07-26 16:37:34 +08:00
e32210301a
fix(agent): migrate official runner ids
2026-07-24 20:50:25 +08:00
283c6949f4
fix(mcp): validate tool call timeout config
2026-07-23 18:26:41 +08:00
0dfae76e39
fix(mcp): make tool call timeout configurable
2026-07-23 18:26:37 +08:00
7677d1a288
fix(mcp): add 30s timeout to prevent MCP tool calls from hanging indefinitely
...
Previously, MCP tool calls via call_tool() had no timeout, so a hung MCP
server would block the entire session indefinitely (exacerbated by
concurrency.session=1). This wraps the call in asyncio.timeout(30) and
raises an Exception on expiry, letting the LLM recover gracefully.
Closes #2339
2026-07-23 18:26:18 +08:00
73e47ea2d4
fix(mcp): keep waiting for box recovery
2026-07-23 17:41:27 +08:00
06e03af994
fix(runtime): complete reconnect recovery paths
2026-07-23 17:28:31 +08:00
8511178666
fix(runtime): harden connector lifecycle
2026-07-23 16:03:26 +08:00
6b13c37c3b
feat(agent): integrate structured runner interactions
2026-07-22 11:32:17 +08:00
998b76d53a
fix(runtime): make plugin and box connectors resilient
2026-07-21 18:43:24 +08:00
1765c43262
Revert "fix(runtime): make plugin and box connectors resilient"
...
This reverts commit 0b461e5830
2026-07-21 18:43:01 +08:00
0b461e5830
fix(runtime): make plugin and box connectors resilient
2026-07-21 18:41:22 +08:00
7615c40f73
fix(plugin): extend knowledge retrieval timeout
2026-07-20 17:12:55 +08:00
76c5003c21
fix(localagent): stop re-seeding stream accumulator with previous round content ( #2329 )
...
When the LLM (e.g. MiniMax-M3) returns multiple rounds after tool calls, the _StreamAccumulator was initialized with initial_content=first_content, causing every subsequent round to repeat the entire first message. Remove the re-seeding so each round starts with a clean accumulator.
Add regression test verifying multi-round tool call content is not duplicated.
2026-07-20 16:38:11 +08:00
e4d4860446
fix(platform): resolve post-rebase compatibility
2026-07-19 23:03:54 +08:00
8afab5fa49
fix(mcp): recover box stdio sessions after disconnect
2026-07-19 22:47:09 +08:00
3359951837
test(workspace): add top-down release gates
2026-07-19 22:46:01 +08:00
cfa7c7b336
fix(tools): support skill mount root discovery
2026-07-19 22:46:01 +08:00
9f28d6949a
fix(agent-runner): unify streamed completion delivery
2026-07-19 22:46:01 +08:00
8a7c3fcefe
fix(agent-runner): aggregate non-streaming replies
2026-07-19 22:46:01 +08:00
54c872b74f
fix(agent-runner): close sandbox skill authoring flow
2026-07-19 22:46:01 +08:00
c55be79f9f
fix(agent-runner): prepare local runner functional tests
2026-07-19 22:46:01 +08:00
1af106aa92
fix(agent-runner): validate clean marketplace onboarding
2026-07-19 22:46:01 +08:00
d88d05e27c
feat(agent-runner): enforce 4.x host-owned execution
2026-07-19 22:46:01 +08:00
9aa71d54e3
feat(agent-runner): finalize 4.x processor integration
2026-07-19 22:45:15 +08:00
0c0f5d8061
feat(wizard): start bot setup from scenarios
2026-07-19 22:44:08 +08:00
00fb6f8236
feat(agent-platform): productize bot event route testing
2026-07-19 22:44:08 +08:00
4cbb9415bf
feat(agent-platform): show bot route runtime status
2026-07-19 22:44:08 +08:00
ee11e97e86
feat(agent-platform): add bot route dry-run
2026-07-19 22:44:08 +08:00
7fb393b85b
refactor: consolidate bot event routing
2026-07-19 22:44:07 +08:00
662627142e
test(agent-runner): strengthen local agent e2e gate
2026-07-19 22:42:40 +08:00
1eef5d2344
fix: remove internal adapter terminology from UI
2026-07-19 22:42:40 +08:00
427e8b2873
fix: stabilize 4.11 branch runtime state
2026-07-19 22:42:40 +08:00
84b3485e7e
fix(platform): align eba event declarations
2026-07-19 22:41:31 +08:00
b29ff78d7b
fix(debug-chat): preserve websocket pipeline routing
2026-07-19 22:41:31 +08:00
517986bd10
feat(agent-runner): support scoped token counting
2026-07-19 22:41:31 +08:00
68d43834bd
fix(adapters): add categories to telegram EBA manifest
...
The Telegram (EBA) manifest was missing spec.categories, so it fell
into the uncategorized/protocol bucket. Restore popular + global to
match the legacy telegram adapter.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com >
2026-07-19 22:41:30 +08:00
huanghuoguoguo