@agent-native/core 0.165.1 → 0.165.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.165.1",
+  "version": "0.165.2",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {
@@ -427,8 +427,8 @@
     "y-protocols": "^1.0.7",
     "yjs": "^13.6.32",
     "zod": "^4.3.6",
-    "@agent-native/toolkit": "^0.16.8",
-    "@agent-native/recap-cli": "0.5.5"
+    "@agent-native/recap-cli": "0.5.5",
+    "@agent-native/toolkit": "^0.16.8"
   },
   "devDependencies": {
     "@ai-sdk/anthropic": "^3.0.71",

package/src/templates/chat/CHANGELOG.md

@@ -3,8 +3,34 @@
 All notable user-facing changes to Chat are documented here. Open it any
 time from the command menu (Cmd+K → "What's new").
 
-## 2026-06-23
+Older updates live in [the changelog folder](./changelog/) and are included in the in-app "What's new" view.
 
-### Added
+## 2026-08-11
 
-- See what's new right inside Chat — a changelog now lives in the command menu (Cmd+K).
+### Fixed
+
+- Chrome no longer offers to install Chat as a desktop app.
+
+## 2026-08-10
+
+### Improved
+
+- Full-page chat now uses the available width up to 1000px for more comfortable prompts and responses.
+
+## 2026-07-31
+
+### Improved
+
+- Clicking the Agent Native logo now toggles the app sidebar.
+
+## 2026-07-29
+
+### Improved
+
+- Sidebar footers now keep Feedback, Search, and Collapse together without a separate language shortcut.
+
+## 2026-07-25
+
+### Improved
+
+- Settings navigation now keeps Manage agent as a dedicated linked destination at the bottom.

package/corpus/templates/.retired/issues/package.json

@@ -1,7 +0,0 @@
-{
-  "name": "issues",
-  "private": true,
-  "scripts": {
-    "build": "node ../../../scripts/build-retired-netlify-site.ts issues"
-  }
-}

package/corpus/templates/.retired/meeting-notes/package.json

@@ -1,7 +0,0 @@
-{
-  "name": "meeting-notes",
-  "private": true,
-  "scripts": {
-    "build": "node ../../../scripts/build-retired-netlify-site.ts meeting-notes"
-  }
-}

package/corpus/templates/.retired/recruiting/package.json

@@ -1,7 +0,0 @@
-{
-  "name": "recruiting",
-  "private": true,
-  "scripts": {
-    "build": "node ../../../scripts/build-retired-netlify-site.ts recruiting"
-  }
-}

package/corpus/templates/.retired/scheduling/package.json

@@ -1,7 +0,0 @@
-{
-  "name": "scheduling",
-  "private": true,
-  "scripts": {
-    "build": "node ../../../scripts/build-retired-netlify-site.ts scheduling"
-  }
-}

package/corpus/templates/.retired/voice/package.json

@@ -1,7 +0,0 @@
-{
-  "name": "voice",
-  "private": true,
-  "scripts": {
-    "build": "node ../../../scripts/build-retired-netlify-site.ts voice"
-  }
-}

package/corpus/templates/voice/.agents/skills/upgrade-agent-native/SKILL.md

@@ -1,87 +0,0 @@
----
-name: upgrade-agent-native
-description: >-
-  Bring an older Agent Native app or workspace current. Use when updating
-  @agent-native/core, fixing a broken upgrade, or when tempted to patch or
-  override core/dispatch packages to make an old branch run.
-scope: dev
-metadata:
-  internal: true
----
-
-# Upgrade Agent Native
-
-## Rule
-
-When an older Agent Native app/branch needs to run on current packages, use
-`agent-native upgrade`. Never "fix" upgrade breakage with
-`pnpm.overrides`, `patchedDependencies`, `resolutions`, local patches, or
-edits under `node_modules/@agent-native/*` — especially not against
-`@agent-native/core` or `@agent-native/dispatch`.
-
-## Why
-
-Agents often respond to a failed core bump by inventing framework patches and
-dispatch behavior overrides. That hides the real app-level break, drifts from
-upstream, and makes the next upgrade worse. The supported path is bump →
-install → refresh scaffold skills → verify, then fix **app** code only.
-
-## How
-
-1. **Doctor first (optional but recommended)**
-
-   ```bash
-   npx @agent-native/core@latest upgrade check
-   ```
-
-   This reports framework overrides/patches and pending `@agent-native/*`
-   bumps. If overrides/patches are present, remove them before continuing.
-
-2. **Run the upgrade**
-
-   ```bash
-   npx @agent-native/core@latest upgrade
-   ```
-
-   Or from an already-installed CLI: `pnpm exec agent-native upgrade` /
-   `agent-native upgrade`.
-
-   What it does:
-
-   - Blocks (unless `--force`) when `@agent-native/*` overrides/patches exist
-   - Rewrites non-local `@agent-native/*` dependency pins to `latest`
-   - Runs the package manager install
-   - Runs `skills update scaffold --project`
-   - Runs `typecheck` when the project has that script
-
-3. **If upgrade or typecheck fails**
-
-   - Read the concrete error
-   - Fix **app** source, actions, config, or env — not framework packages
-   - Re-run `agent-native upgrade` or `pnpm typecheck`
-   - Stop and ask the user if you cannot fix the app-level error
-
-4. **Dry-run / partial runs**
-
-   ```bash
-   agent-native upgrade --dry-run
-   agent-native upgrade --skip-verify
-   agent-native upgrade --skip-install   # package.json bumps only
-   ```
-
-## Don't
-
-- Don't add `pnpm.overrides`, `overrides`, `resolutions`, or
-  `patchedDependencies` for any `@agent-native/*` package
-- Don't edit `node_modules/@agent-native/core` or
-  `node_modules/@agent-native/dispatch`
-- Don't invent local "dispatch behavior" shims to paper over version skew
-- Don't keep iterating with more framework patches after a failed install
-- Don't skip `skills update scaffold --project` after a core bump (the
-  upgrade command does this for you)
-
-## Related Skills
-
-- **self-modifying-code** — Tier 4: framework packages are off limits
-- **agent-native-docs** — version-matched docs after the bump
-- **portability** — keep app code provider-agnostic across upgrades