Problem
OpenBot has persistent coworkers, per-Agent computers, governed tool use, and auditability, but it lacks a simple way to share and reuse complete Agent configurations across users and deployments.
For teams running multiple OpenBot instances or collaborating on agent setups, every Agent must be recreated manually by copying YAML by hand. This makes it hard to standardize on proven Agent roles, share best practices, or onboard new users quickly.
Feature request
Add Agent templates - a shareable, importable format for complete Agent configurations. This should be a configuration-level feature, not a new data model.
Proposed behaviour
Allow exporting an Agent's full configuration (role, tools, grants, skills, instructions) as a single shareable file.
Allow importing an Agent template file to create a new Agent with the same configuration.
Support optional metadata in templates (author, description, tags) for discovery and versioning.
Let users import templates from local files or URLs.
Validate templates on import and show clear errors for missing or incompatible fields.
Preserve all governance settings (grants, policies) on import, scoped to the importing user's permissions.
##Required controls
Disabled by default; enabled per deployment.
Template scope: personal, team-shared, or public URL.
Immutable audit log showing when a template was exported, imported, or modified.
Review, edit, and delete controls for imported templates.
Clear separation between template configuration and runtime state (no runtime data is exported).
Never automatically grant additional tools or permissions on import — grants must be explicitly re-applied.
Configurable allowlist for template sources (local only, trusted domains, or any URL).
Why this matters
This would make OpenBot more competitive for team deployments and community sharing while preserving its core advantages: per-Agent isolation, gateway policy enforcement, and action-level auditability. It would be particularly useful for a self-hosted team that wants to standardize on proven Agent roles (e.g., "Newsletter Orchestrator", "Site Monitor") across multiple instances without manual recreation.
Acceptance criteria
An administrator can export an Agent's configuration as a template file.
An administrator can import a template file to create a new Agent.
Template imports preserve all configuration fields (role, tools, grants, skills, instructions).
Template imports do not carry over runtime state (transcripts, memory, active sessions).
All template exports/imports appear in the existing audit trail.
Invalid templates are rejected with clear error messages.
Imported Agents respect the importing user's existing grant boundaries.
Suggested name
Agent Templates or Shareable Agent Configurations
Problem
OpenBot has persistent coworkers, per-Agent computers, governed tool use, and auditability, but it lacks a simple way to share and reuse complete Agent configurations across users and deployments.
For teams running multiple OpenBot instances or collaborating on agent setups, every Agent must be recreated manually by copying YAML by hand. This makes it hard to standardize on proven Agent roles, share best practices, or onboard new users quickly.
Feature request
Add Agent templates - a shareable, importable format for complete Agent configurations. This should be a configuration-level feature, not a new data model.
Proposed behaviour
Allow exporting an Agent's full configuration (role, tools, grants, skills, instructions) as a single shareable file.
Allow importing an Agent template file to create a new Agent with the same configuration.
Support optional metadata in templates (author, description, tags) for discovery and versioning.
Let users import templates from local files or URLs.
Validate templates on import and show clear errors for missing or incompatible fields.
Preserve all governance settings (grants, policies) on import, scoped to the importing user's permissions.
##Required controls
Disabled by default; enabled per deployment.
Template scope: personal, team-shared, or public URL.
Immutable audit log showing when a template was exported, imported, or modified.
Review, edit, and delete controls for imported templates.
Clear separation between template configuration and runtime state (no runtime data is exported).
Never automatically grant additional tools or permissions on import — grants must be explicitly re-applied.
Configurable allowlist for template sources (local only, trusted domains, or any URL).
Why this matters
This would make OpenBot more competitive for team deployments and community sharing while preserving its core advantages: per-Agent isolation, gateway policy enforcement, and action-level auditability. It would be particularly useful for a self-hosted team that wants to standardize on proven Agent roles (e.g., "Newsletter Orchestrator", "Site Monitor") across multiple instances without manual recreation.
Acceptance criteria
An administrator can export an Agent's configuration as a template file.
An administrator can import a template file to create a new Agent.
Template imports preserve all configuration fields (role, tools, grants, skills, instructions).
Template imports do not carry over runtime state (transcripts, memory, active sessions).
All template exports/imports appear in the existing audit trail.
Invalid templates are rejected with clear error messages.
Imported Agents respect the importing user's existing grant boundaries.
Suggested name
Agent Templates or Shareable Agent Configurations