Workspaces and Tasks

The /task route is the task workspace hub. It gives users one place to chat with the default agent, create reusable workspaces, schedule recurring tasks, manage agent defaults, and return to previous task runs.

A workspace is a persistent execution environment for an agent. It has a chat session, workspace files, enabled connections, enabled skills, and optional scheduled-task settings. When a workspace starts, BotDojo starts or resumes the workspace container, loads the workspace's files and skills, and gives the agent the selected tools and context.

Left navigation

The left navigation on /task is split into fixed top-level pages and collapsible workspace history sections.

New Chat

Use New Chat for a one-off task with the default agent. The composer can reference enabled connections with @ and skills with /.

When the chat creates a workspace-backed run, BotDojo records it in the left navigation so the user can reopen the conversation later. These ad hoc task runs appear under Chats when there is chat history.

Search

The Search entry opens task memory search. Use it to find prior task conversations, workspace context, and saved task history without manually opening each workspace.

Personalization

Personalization controls the defaults used when creating new task workspaces. These defaults are copied into new workspaces at creation time. Existing workspaces keep their own saved settings unless edited directly.

Personalization has three sections:

• Agent - Configure the default task agent. The current subsections are Name & Model, AGENT.md, and MEMORY.md.
• Connections - Choose the default connection access for new task workspaces.
• Skills - Choose which skill collections are available to new task workspaces and how those collections are loaded.

Use Personalization when the user wants future tasks to start with a different model, different instructions, different memory, different tools, or different skill availability.

Agents

Agents is the place to view and manage task agents available in the project. Agents define the identity, instructions, memory, model defaults, permissions, and skill ownership used by task workspaces.

The default task agent is the agent used by New Chat, new workspaces, and schedules unless a workspace or template overrides it.

Artifacts

Artifacts appears when task workspaces have produced saved artifacts. It lets users browse generated documents or files across workspaces and jump back to the workspace where an artifact was created.

Scheduled Tasks

Scheduled Tasks lists workspaces with recurring scheduled runs. Each scheduled task is backed by a workspace plus a scheduled trigger.

From the scheduled task menu, users can:

• Run now - Queue the scheduled task immediately.
• Enable or Disable - Toggle the linked schedule without deleting the workspace.
• Edit - Change the prompt, schedule, model override, notification recipients, resources, skills, or connection access.

Scheduled tasks reuse the workspace's saved configuration. This means the task keeps the same enabled connections, skill settings, workspace files, and optional session reuse settings across runs.

Workspaces

Workspaces lists project workspaces. These are persistent work areas intended for reusable or longer-lived work. A project workspace can hold files, open chat sessions, skill edits, and workspace-specific settings.

Use a project workspace when the work should be revisited, shared in project context, or used as the basis for a recurring task.

Chats

Chats lists previous ad hoc task workspaces created from New Chat. These are task-history entries rather than named project workspaces. Reopen a chat when the user wants to continue or inspect a prior task run.

Workspace view

Opening a workspace from the left navigation switches the main area into the workspace view. In /task, workspaces default to a chat-first mode, but they still have workspace files and settings behind the scenes.

The workspace view includes:

• Chat - The active conversation with the workspace agent.
• Files - Workspace files that can be opened, referenced, edited, and attached to prompts.
• Settings - Workspace-level settings for runtime size, access, skills, and schedules.
• Open file panels - Files selected from the workspace can open alongside chat so the user and agent can inspect or edit them.

The workspace container owns the runtime file system. Workspace files are exposed to the agent through workspace file resources such as workspace://files/..., and the UI maps those resources back to visible files.

Workspace directory and files

Workspace files are the files available inside the workspace container. The UI file explorer shows the workspace directory, and files selected from the explorer can be opened in the workspace view or attached to a chat message.

Important behavior:

• Files selected in chat are attached as workspace file resources.
• Open files stay associated with the workspace session.
• The agent can read and write workspace files when the workspace has the relevant file tools enabled.
• Files outside the user-facing workspace area, such as internal /home/agent/... paths, are generally hidden from the file picker unless surfaced through a specific skill or management flow.

Skills in workspaces

Skills are reusable instructions and tool workflows that the agent can discover or load while solving a task. Skills are managed from Personalization > Skills, workspace settings, or the composer skill menu.

Skill collections can be configured in three modes for new workspaces:

• Primary - Cloned into /home/agent/skills when the workspace starts. Use this for the agent's own editable my-skills collection or skills that should be immediately available as local files.
• Discoverable - Searchable by the workspace and available for the agent to load when needed. This keeps startup lighter while still making the skill available.
• Hidden - Excluded from new task workspaces created with the current settings.

In a workspace, the Manage skills flow can add or update skills through BotDojo chat, upload a zip, or import from GitHub when the collection allows contributions. Skills can also be opened and edited from the workspace skill manager.

Connections in workspaces

Connections are model context resources and integrations available to the workspace agent. Examples include external apps, project resources, BotDojo resources, and integration-backed tool suites.

Connection access is workspace-scoped. A workspace can allow, require approval for, or deny a connection. Tool-level permissions can also allow direct invocation, require approval, or block individual tools.

Default connection access comes from Personalization or the workspace template. A new task can adjust connection access before submission, and an existing workspace can adjust access in workspace settings.

Scheduling tasks

A scheduled task is a workspace with scheduled-task metadata and a linked scheduled trigger. The schedule stores the prompt, schedule config, selected flow, optional model override, notification recipients, prompt resources, and session reuse behavior.

Use scheduled tasks for recurring work such as periodic reports, inbox checks, data refreshes, follow-up prompts, or recurring research tasks.

Scheduled tasks are different from simple chat reminders because they run against a workspace. They can reuse files, skills, connections, and context saved on that workspace.

Personal Workspace vs Project Workspaces

BotDojo distinguishes between personal workspace behavior and project workspace behavior.

Area	Personal Workspace	Project Workspaces
Scope	User-centered task environment	Project-centered shared work area
Connections label	My Connections	Project-specific connections, usually shown as the project name or Project Connections
Default project access	Project resources default toward denied access unless enabled	Project resources can default toward approval-required access
Best for	Personal task defaults, private agent preferences, personal integrations	Team or project work, reusable workspaces, shared artifacts, recurring project tasks
Navigation	Focused on the user's task hub	Includes project workspace history and project navigation back to the project

Use a personal workspace for work that should follow the user's own connections and agent defaults. Use a project workspace when the task belongs to a project, needs project connections, should be revisited by project context, or should become a scheduled task.

Common workflow

1. Open /task.
2. Use Personalization to set the default agent, connections, and skills.
3. Start with New Chat for a quick task, or create a named item under Workspaces for longer-lived work.
4. Open files or attach workspace files as needed.
5. Add skills through the composer or workspace skill manager when the agent needs reusable instructions.
6. Convert recurring work into a Scheduled Task so it runs on a schedule with the same workspace context.