Let the coordinator create workspaces and write findings in tasks
create_workspace gives the coordinator a way to start a workspace with its shared context, and the tool list is shared, so a new id can be used by create_bot or add_bot_to_workspace in the same reply. A coordinator's tasks now get create_workspace and update_workspace too: the research task that had the material could only report it, never write it into the workspace, so the coordinator promised an update it had no turn to make. A workspace created from chat is pushed as server:workspace-created, from the tool and from the live relay, so the rail shows it without a reload.
This commit is contained in:
@@ -167,6 +167,14 @@ export type BotCreatedData = {
|
||||
in_own_chat: boolean;
|
||||
};
|
||||
|
||||
/**
|
||||
* `server:workspace-created` data: a workspace the user can now see, as
|
||||
* their rail lists it.
|
||||
*/
|
||||
export type WorkspaceCreatedData = {
|
||||
workspace: WorkspaceWithActivity;
|
||||
};
|
||||
|
||||
/**
|
||||
* `server:bot-removed` data: the bot that was deleted.
|
||||
*/
|
||||
@@ -617,6 +625,11 @@ export const WebSocketEvents = [
|
||||
* A bot's face or status line changed (`data`: `BotUpdatedData`)
|
||||
*/
|
||||
"server:bot-updated",
|
||||
/**
|
||||
* A workspace the user can see was created (`data`:
|
||||
* `WorkspaceCreatedData`)
|
||||
*/
|
||||
"server:workspace-created",
|
||||
/**
|
||||
* A running job took a step (`data`: `BotJobUpdateData`)
|
||||
*/
|
||||
|
||||
Reference in New Issue
Block a user