​

Extensions

​

What Extensions Add

​

How Extensions Work

1. Manifest — A pawz-skill.toml with [view] and/or [storage] sections
2. Sidebar view — The extension registers a tab in the sidebar with its own icon and label
3. Persistent data — The extension declares storage tables; agents use skill_store_* tools to persist structured data across sessions
4. Data-bound rendering — The custom view reads from the extension’s storage and renders live data (tables, charts, pipelines, feeds)
5. Widget — An optional dashboard card shows a summary on the Today page

​

Extension Manifest

[skill]
id = "simple-crm"
name = "Simple CRM"
version = "1.0.0"
author = "community"
category = "productivity"
icon = "contacts"
description = "A lightweight CRM with contacts, deals, and activity tracking"

[[credentials]]
key = "CRM_WEBHOOK"
label = "Import Webhook (optional)"
description = "Incoming webhook URL for importing contacts from external systems"
required = false
placeholder = "https://..."

[instructions]
text = """
You have a CRM system with persistent storage. Use the storage tools to manage data:

## Contacts
- skill_store_set: Add or update a contact (name, email, company, stage)
- skill_store_query: Search contacts by name, company, or stage
- skill_store_get: Get a specific contact by ID

## Deals
- skill_store_set: Create or update deals (name, value, stage, contact_id)
- skill_store_query: Filter deals by stage (new, qualified, proposal, closed)

## Activity
- skill_store_set: Log activities (type: call/email/meeting, notes, contact_id)
- skill_store_query: Get activity feed for a contact or date range

When the user asks about their pipeline, contacts, or deals, query storage first.
"""

[widget]
type = "table"
title = "Active Deals"
refresh = "5m"

[[widget.fields]]
key = "name"
label = "Deal"
type = "text"

[[widget.fields]]
key = "value"
label = "Amount"
type = "currency"

[[widget.fields]]
key = "stage"
label = "Stage"
type = "badge"

[view]
id = "crm-pipeline"
label = "CRM"
icon = "contacts"

[storage]
namespace = "crm"
tables = ["contacts", "deals", "activities"]

​

[view] Section

​

[storage] Section

​

Storage Tools

​

Example: Agent interaction

{
  "namespace": "crm",
  "table": "contacts",
  "id": "john-smith",
  "data": {
    "name": "John Smith",
    "email": "john@acme.com",
    "company": "Acme Corp",
    "stage": "new",
    "created": "2025-01-21T10:30:00Z"
  }
}

{
  "namespace": "crm",
  "table": "contacts",
  "filter": { "company": "Acme Corp" }
}

​

Example Extensions

​

CRM Pipeline

​

Smart Home Dashboard

​

Portfolio Tracker

​

Content Calendar

​

Modular Workspace Integration

• Extension views appear in the Custom workspace profile toggle grid
• Users can show/hide extension views like any built-in view
• Extension views respect the active workspace profile
• Hidden extension views preserve their data — nothing is lost

​

Per-Agent Scoping

1. Open the Agents tab → select an agent → go to their Skills sub-tab
2. Enable or disable the extension for that agent
3. Only assigned agents receive the extension’s instructions and credentials in their prompt
4. All agents can read from the extension’s storage (for dashboard rendering)
5. Only assigned agents can write to the extension’s storage
6. The extension’s sidebar view is always visible (it shows data, not agent context)

​

Creating Extensions

1. Start with the In-App Wizard or a template
2. Add your credentials and instructions (same as an integration)
3. Add a [view] section to declare a sidebar tab
4. Add a [storage] section to declare persistent tables
5. Test with a live agent — use chat to populate storage, verify the view renders
6. Publish to PawzHub

​

Upgrade Path

​

Security

• Execute arbitrary Rust code
• Render arbitrary HTML/JavaScript (views use the app’s renderer)
• Access other extensions’ storage namespaces
• Write to storage from unassigned agents
• Bypass domain or shell policies

​

Tier Badges