@agent-native/core 0.27.0 → 0.28.0

package/docs/content/frames.md

@@ -33,14 +33,14 @@ component in dev and prod.
 - Reads `application_state.navigation` every turn, so it already knows which
   view you're in and what's selected — you don't have to re-explain "this".
 
-### Dev vs prod tool modes {#tool-modes}
+### App vs Code tool modes {#tool-modes}
 
 The panel runs in one of two tool modes:
 
-- **Production mode** — the agent only has your app's own tools: the actions you
+- **App mode** — the agent only has your app's own tools: the actions you
   defined with `defineAction`, plus navigation and context. No filesystem or
   shell access. This is what end users get.
-- **Development mode** — adds the shared coding tools (`bash`, `read`, `edit`,
+- **Code mode** — adds the shared coding tools (`bash`, `read`, `edit`,
   `write`) and database access on top of the app tools, so the agent can change
   the app's own source. Code requests are gated: when a message requires code
   (`type: "code"`) and no code-capable frame is connected, the panel shows a
@@ -48,9 +48,15 @@ The panel runs in one of two tool modes:
   when a frame is connected, the request is routed to it and a code-agent
   indicator shows while it works (`useSendToAgentChat`).
 
+"Code mode" is the agent-capability toggle — distinct from environment dev mode
+(`NODE_ENV` / Vite). For back-compat the underlying `AGENT_MODE` env var, the
+`/_agent-native/agent-chat/mode` endpoint (whose payload still uses `devMode`),
+and the `agent-chat.mode` settings key are unchanged. The client hook is
+`useCodeMode()` (the older `useDevMode()` remains as a deprecated alias).
+
 In the local dev frame, the settings cog toggles between these modes. Switching
-to prod hides the frame's own sidebar and shows the app's in-app agent sidebar
-inside the iframe instead, so you can preview exactly what end users see.
+off Code mode hides the frame's own sidebar and shows the app's in-app agent
+sidebar inside the iframe instead, so you can preview exactly what end users see.
 
 ## Integrated terminal and CLI switching {#cli-terminal}
 

package/docs/content/workspace.md

@@ -139,7 +139,7 @@ Change how the agent behaves, in 60 seconds.
 
 ## How the Agent Uses Resources {#how-the-agent-uses-resources}
 
-The agent has built-in tools for managing resources: `resource-list`, `resource-read`, `resource-effective`, `resource-write`, and `resource-delete`. These are available in both dev and production modes.
+The agent has built-in tools for managing resources: `resource-list`, `resource-read`, `resource-effective`, `resource-write`, and `resource-delete`. These are available in both Code mode and App mode.
 
 At the start of every conversation, the agent automatically reads:
 
@@ -337,8 +337,8 @@ When the agent encounters a task that matches a skill, it reads the skill file a
 
 There are two ways to add skills:
 
-1. **Via Workspace tab** — Create a new resource with a path like `skills/my-skill/SKILL.md`. This works in both dev and production.
-2. **Via code (dev only)** — Add a Markdown file to `.agents/skills/` in your project. These are available when the app runs in dev mode.
+1. **Via Workspace tab** — Create a new resource with a path like `skills/my-skill/SKILL.md`. This works in both Code mode and App mode.
+2. **Via code (Code mode only)** — Add a Markdown file to `.agents/skills/` in your project. These are available when the app runs in Code mode.
 
 ## Custom Agents {#custom-agents}
 
@@ -435,8 +435,8 @@ When you send a message:
 
 What shows up depends on the mode:
 
-- **Dev mode** — Codebase files, workspace resources, custom agents, and connected agents
-- **Production mode** — Workspace resources, custom agents, and connected agents
+- **Code mode** — Codebase files, workspace resources, custom agents, and connected agents
+- **App mode** — Workspace resources, custom agents, and connected agents
 
 ## / Slash Commands {#slash-commands}
 
@@ -444,16 +444,16 @@ Type `/` at the start of a line to invoke a skill. A dropdown shows available sk
 
 What shows up depends on the mode:
 
-- **Dev mode** — Skills from `.agents/skills/` (codebase) and skills from resources
-- **Production mode** — Skills from resources only
+- **Code mode** — Skills from `.agents/skills/` (codebase) and skills from resources
+- **App mode** — Skills from resources only
 
 If no skills are configured, the dropdown shows a hint with a link to these docs.
 
-## Dev vs Production Mode {#dev-vs-prod}
+## Code vs App Mode {#dev-vs-prod}
 
 The resource system works identically in both modes. The difference is what additional sources are available for `@` tagging and `/` commands:
 
-| Feature            | Dev Mode                                                                | Production                                             |
+| Feature            | Code Mode                                                               | App Mode                                               |
 | ------------------ | ----------------------------------------------------------------------- | ------------------------------------------------------ |
 | @ tagging          | Codebase files + workspace resources + custom agents + connected agents | Workspace resources + custom agents + connected agents |
 | / slash commands   | .agents/skills/ + resource skills                                       | Resource skills only                                   |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.27.0",
+  "version": "0.28.0",
   "type": "module",
   "engines": {
     "node": ">=22"