# Adding Workspace Apps

How to add an app to an Agent-Native workspace: classifying an "agent" request...

- Repository: https://github.com/BuilderIO/agent-native (7579 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add BuilderIO/agent-native --skill adding-workspace-apps -g -a claude-code -y`
Codex: `npx skills add BuilderIO/agent-native --skill adding-workspace-apps -g -a codex -y`
Cursor: `npx skills add BuilderIO/agent-native --skill adding-workspace-apps -g -a cursor -y`
Gemini CLI: `npx skills add BuilderIO/agent-native --skill adding-workspace-apps -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add BuilderIO/agent-native`

## Description

How to add an app to an Agent-Native workspace: classifying an "agent" request, scaffolding `apps/<app-name>`, app discovery and descriptions, mounting and base paths, action-first data, and finishing a chat-template app. Use when asked to create, build, scaffold, or generate a new agent or app in a workspace.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Adding Workspace Apps

## Classify The Ask First

When a user asks from Dispatch chat or through `@agent-native` in Slack or
Telegram to create, build, make, scaffold, or generate an "agent", classify
the ask first.
Simple Dispatch-native behavior such as a reminder, digest, monitor, routing
rule, saved instruction, or recurring workflow can stay in Dispatch as a
recurring job/resource/destination. Robust unique products or teammates that
need their own UI, data model, actions, integrations, or domain workflow should
become a separate workspace app under `apps/<app-name>`, mounted at
`/<app-name>`.

## Where The App Lives

Do not implement a new app by adding a route, page, component, or file to
`apps/chat` or another existing app unless the user explicitly asks to modify
that existing app.

## Vault Access

Dispatch vault access is workspace-wide by default: every saved vault key is
available to every workspace app. Only create or request per-app vault grants
when Dispatch's vault access setting is switched to manual mode.

When an app needs a provider credential, use the app's scoped secret or
workspace-connection resolver so Dispatch remains the source of truth. Do not
ask a non-admin builder to add a key to local project settings or `.env`; use
Dispatch's vault request workflow for a missing key and keep the value out of
app code.

## Discovery, Links, And The UI Stack

The rest: https://github.com/BuilderIO/agent-native/blob/HEAD/.agents/skills/adding-workspace-apps/SKILL.md