You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Pass explicit workspace IDs through agent data-plane calls #3
Propagate the task's immutable workspace_id to every Lake data-plane call, delegated task, app/build create, and workspace REST/MCP request made by this agent.
Refs oramasearch/lake#311. Coordinate with oramasearch/agent-runtime#6, the client cutover prerequisite. Lake no longer publishes or reads global bus events: agent-events lives in the workspace Zetta named by the task's persisted services.id. Only content-free agent-tasks.<agent> dispatch remains on the shared bus.
Acceptance
Read workspace identity from the claimed task, never from a default-customer lookup. Required IDs remain explicit even when the customer has only one workspace.
Forward it through tool schemas, prompts/tool adapters and every delegated create; unknown or missing IDs surface invalid_input without fallback.
Test two customers and multiple workspaces per customer, including event publication and delegated calls using task-bound credentials.
Adopt the updated runtime client, remove old global-event consumers, document the coordinated cutover, and redeploy this agent.
Back off on empty dispatch reads so the idle receive rate is at most once per minute per agent; coordinate the longer upstream poll with the runtime follow-up.
For offline corpus/generator tooling, propagate the explicit target workspace through its input/configuration and generated requests rather than introducing bus polling.
Activity