@appthen/vibe-workspace

AppThen Workbench runtime and offline extension development toolkit.

For Extension Developers

The recommended starting point is the generated offline workspace:

pnpm dlx @appthen/vibe-workspace init extension-workspace --template full
cd extension-workspace
pnpm install
pnpm doctor
pnpm dev

The workspace supports multiple local extensions and does not require marketplace access during development. Read the generated AGENTS.md before making changes.

Extension Commands

appthen-extension init [dir] [--id app.id] [--template basic|full]
appthen-extension dev [--port 5177]
appthen-extension doctor [--json]
appthen-extension validate
appthen-extension test [extensionId]
appthen-extension build [extensionId]
appthen-extension pack [extensionId]
appthen-extension publish [extensionId] --server <url> --tenant <tenantId>
appthen-extension install <package-file> --server <url> --tenant <tenantId>

开发 Workbench SDK 本身时，不需要发布 npm。先在 SDK 仓库执行 pnpm run build:lib -- --watch，再从扩展工作区指向本地 SDK：

pnpm dev -- --package-root /path/to/vibe-workspace

publish uploads and updates the tenant extension record. It does not mount the extension into a Workbench unless --install-tenant is provided. Workbench mounting and permissions are configured separately.

Stable Extension API

External extensions should use:

• ctx.capabilities.registerSidebarView
• ctx.capabilities.registerEditorView
• ctx.capabilities.registerContribution
• ctx.capabilities.registerFrontendToolHandler
• ctx.views.openEditor
• ctx.links
• ctx.runtime and ctx.auth

External extensions should not depend on extensionRegistry, eventBus, workspaceEditorService, or registerMainView.

Documentation

• Extension development specification
• AGENTS.md is generated in every workspace by appthen-extension init.
• Multi-column workspace rules

Local Development Of This Repository

pnpm install
pnpm typecheck
pnpm run build:lib