@amaster.ai/pi-teamwork

Pi extension for team collaboration and project management. Provides LLM-callable tools to interact with issue trackers and project management systems.

Supported Providers

• Multica — CLI-based adapter via multica

Configuration

Auto-Install

Runtime auto-installation is disabled because mutable package-manager taps and download scripts cannot provide the pinned artifact verification required in a credential-bearing agent process. Install a pinned Multica release separately and put the verified binary on $PATH, or configure multica.binary.

The deprecated autoInstall: true setting no longer executes an installer. It only reports a clear error when the binary is missing.

Configuration may live in user/agent settings or in a trusted project's .pi/settings.json. Project settings are ignored when trust is declined and do not expand ${ENV_VAR}; keep environment-backed credentials in user or agent settings.

Mode 1 — Self-hosted server

For teams running their own Multica server. The extension runs multica setup self-host with the provided URLs, then authenticates with the token:

{
  "pi-teamwork": {
    "enabled": true,
    "provider": "multica",
    "multica": {
      "serverUrl": "https://api.your-server.com",
      "appUrl": "https://your-server.com",
      "token": "<token-from-multica-server>"
    }
  }
}

Mode 2 — Pre-configured environment

Run multica setup once on the machine and finish login through multica's normal flow. The extension will reuse that state:

{
  "pi-teamwork": {
    "enabled": true,
    "provider": "multica",
    "multica": {
      "workspace": ""
    }
  }
}

Mode 3 — Headless token (Multica Cloud)

For CI or non-interactive environments where you can't run multica setup. The extension will run multica login --token <token> on every session_start:

{
  "pi-teamwork": {
    "enabled": true,
    "provider": "multica",
    "multica": {
      "token": "<token-from-multica-server>"
    }
  }
}

⚠️ token is a credential. Keep it out of version control — put it in a local-only settings file or inject via env-substituted config.

| Field | Description | |-------|-------------| | enabled | Enable/disable the extension | | provider | Provider name (multica) | | multica.binary | Path to multica binary (default: multica) | | multica.workspace | Workspace ID override; leave empty to use multica's default | | multica.token | Headless-login token. Omit when multica is already logged in on the machine | | multica.serverUrl | Self-hosted server API URL. Triggers multica setup self-host --server-url on start | | multica.appUrl | Self-hosted server frontend URL. Required when serverUrl is a remote address | | multica.autoInstall | Deprecated compatibility flag; no installer is executed (default: false) |

Tools

| Tool | Description | |------|-------------| | issue_list | List issues with optional filters (status, assignee, project, limit) | | issue_get | Get detailed info about a specific issue | | issue_create | Create a new issue | | issue_update | Update an existing issue (title, description, status, priority, assignee) | | issue_comment | Add a comment to an issue | | project_list | List all projects in the workspace | | teamwork_status | Check provider/daemon status |

Commands

• /teamwork-status — Show current provider status

Architecture

src/
├── index.ts              # Generic tool layer (provider-agnostic)
├── types.ts              # TeamworkProvider interface + shared types
└── adapters/
    └── multica.ts        # Multica CLI adapter + initialization

The extension uses a provider pattern — index.ts registers tools that delegate to a TeamworkProvider interface. Adding a new provider (Linear, Jira, etc.) only requires implementing the interface and adding a factory branch in session_start.