@tangle-network/create-agent-app 0.45.13 → 0.45.14

package/README.md

@@ -7,3 +7,7 @@ npm create @tangle-network/agent-app@latest my-agent
 ```
 
 Then `cd my-agent && pnpm install && pnpm typecheck && pnpm test`, and follow the generated `CUSTOMIZE.md` / `AGENTS.md`.
+
+For a chat-first web surface, the generated customization trail points to the
+shared workspace composition in
+[`examples/default-workspace.md`](../examples/default-workspace.md).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tangle-network/create-agent-app",
-  "version": "0.45.13",
+  "version": "0.45.14",
   "description": "Create a tested Tangle agent application with either a tool loop or a complete chat interface.",
   "keywords": [
     "tangle",

package/template-chat/CUSTOMIZE.md

@@ -28,6 +28,11 @@ Discovery: **Which model answers by default, at what effort, on which harness?**
 - [ ] Set `model.default` to a model your Tangle Router key can reach.
 - [ ] Pick `harness` (`opencode` default; vendor-locked harnesses like
       `claude-code` must pair with their own provider's models).
+- [ ] Define the selectable profile catalog for the UI and map each selected
+      profile id to the real runtime `AgentProfile` before session creation.
+      Keep that browser catalog to stable display metadata and capability labels;
+      resolve prompts, tools, permissions, connections, resources, and backend
+      policy server-side. Put profile authoring in settings, not the composer.
 - [ ] Leave per-turn overrides alone — the client can send `model`/`effort`
       per request and `MODEL_NAME` overrides without a redeploy.
 
@@ -63,6 +68,18 @@ Discovery: **What does the real surface look like?**
       `streamChatTurn` (start + resume against `/api/chat/replay/:turnId`),
       `useChatInteractions` + `InteractionQuestionCard`/`InteractionPlanCard`
       for the ask channel this server already exposes.
+- [ ] For a chat-first product, use `AgentWorkspaceLayout` from
+      `@tangle-network/agent-app/workspace-react` for the outer layout and
+      session rail, `EntryComposer` from
+      `@tangle-network/agent-app/chat-react` for the new-session route, and
+      `SessionHistoryPanel` from `@tangle-network/agent-app/web-react` for the
+      full history route.
+      Pass `agent.profile`, `agent.harness`, `agent.model`, and `agent.effort`
+      from real product state so the shared control row does not disappear.
+      Pass `planMode`, `uploadUrl`, and `mentions` only when the corresponding
+      backend behavior, upload route, and file index are real.
+      Keep navigation taxonomy, session URLs, domain context, and transcript
+      cards in the product.
 - [ ] Keep the wire contract: `chatTurnRequestInit` from web-react serializes
       exactly what `createChatTurnRoutes` parses.