@agent-native/core 0.209.1 → 0.209.2-nightly-20261015213030

package/docs/content/template-clips-developers.mdx

@@ -138,14 +138,15 @@ Every operation is a TypeScript file in `templates/clips/actions/`, auto-mounted
 
 The Chrome extension attaches console and network diagnostics to a recording, and `save-browser-diagnostics` stores them. Every console and network entry carries a `tabId`.
 
-| Topic         | Behavior                                                                                                                                                              |
-| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Tabs          | Up to five per recording: the start tab, then tabs active in the last 10 minutes, most recent first. A tab the user switches to during the recording is attached too. |
-| Over five     | The least recently active tab other than the focused one is detached. Its entries so far stay in the recording.                                                       |
-| Lookback      | Up to 30 seconds before the recording started, limited by the page's own console history and resource timing list. These entries have negative `elapsedMs`.           |
-| `tabId`       | Set on every console and network entry.                                                                                                                               |
-| `method`      | `"UNKNOWN"` on lookback network entries, which come from resource timing and have no HTTP method. Live requests report the method.                                    |
-| Not collected | Request and response bodies and headers. Console and network entries are redacted before upload.                                                                      |
+| Topic         | Behavior                                                                                                                                                                                                                                         |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Tabs          | Up to five per recording: the start tab, then tabs active in the last 10 minutes, most recent first. A tab the user switches to during the recording is attached too.                                                                            |
+| Over five     | The least recently active tab other than the focused one is detached. Its entries so far stay in the recording.                                                                                                                                  |
+| Lookback      | Up to 30 seconds before the recording started, limited by the page's own console history and resource timing list. These entries have negative `elapsedMs`.                                                                                      |
+| `tabId`       | Set on every console and network entry.                                                                                                                                                                                                          |
+| `method`      | `"UNKNOWN"` on lookback network entries, which come from resource timing and have no HTTP method. Live requests report the method.                                                                                                               |
+| App activity  | On Agent-Native apps, the [recorder](/docs/recorder) events from the recorded tab. `save-recording-app-activity` stores them as a private file with a summary on the diagnostics row, and `get-recording-app-activity` reads them by time range. |
+| Not collected | Request and response bodies and headers. Console and network entries are redacted before upload.                                                                                                                                                 |
 
 ## Data model
 

package/docs/content/template-clips-features.mdx

@@ -169,13 +169,14 @@ Earlier screen time attaches up to five minutes of local screen history from bef
 
 Install the Clips Chrome extension for a recording plus the browser logs and network activity from the tab you're debugging, useful for reporting product bugs and browser-only repros.
 
-| Topic       | Behavior                                                                                                                                                                                                       |
-| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Tabs        | Up to five: the tab you started the recording from, then tabs you used in the last 10 minutes, most recent first.                                                                                              |
-| Switching   | A tab you switch to during the recording is captured too. If more than five tabs are attached, the least recently used tab other than the one in focus is detached, and its logs so far stay in the recording. |
-| Lookback    | Up to 30 seconds before the recording started, as far as the page still keeps its console history and resource timing. These entries have negative time offsets.                                               |
-| Saved       | Console messages, and fetch/XHR request info: method, a redacted URL, status, duration, and whether it failed. Each entry records the tab it came from.                                                        |
-| Never saved | Request or response bodies, headers, or cookies.                                                                                                                                                               |
+| Topic        | Behavior                                                                                                                                                                                                       |
+| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Tabs         | Up to five: the tab you started the recording from, then tabs you used in the last 10 minutes, most recent first.                                                                                              |
+| Switching    | A tab you switch to during the recording is captured too. If more than five tabs are attached, the least recently used tab other than the one in focus is detached, and its logs so far stay in the recording. |
+| Lookback     | Up to 30 seconds before the recording started, as far as the page still keeps its console history and resource timing. These entries have negative time offsets.                                               |
+| Saved        | Console messages, and fetch/XHR request info: method, a redacted URL, status, duration, and whether it failed. Each entry records the tab it came from.                                                        |
+| App activity | On Agent-Native apps, the recorded tab's own actions, state changes, navigation, and errors from the [recorder](/docs/recorder), including the 30 seconds before the recording started.                        |
+| Never saved  | Request or response bodies, headers, or cookies.                                                                                                                                                               |
 
 Lookback network entries have no HTTP method, so their method is recorded as `UNKNOWN`. Requests made during the recording include the method. Tabs are tracked while the extension is running, so for the first 10 minutes after it starts, fewer than five tabs may qualify.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.209.1",
+  "version": "0.209.2-nightly-20261015213030",
   "description": "The agentic application framework for building autonomous agents with intuitive UIs",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {
@@ -216,6 +216,7 @@
     "./client/sign-in-landing": "./dist/client/sign-in-landing.js",
     "./client/oauth-popup": "./dist/client/oauth-popup.js",
     "./client/route-state": "./dist/client/route-state.js",
+    "./client/recorder": "./dist/client/recorder.js",
     "./observability/actions/list-observability-reviews": "./dist/observability/actions/list-observability-reviews.js",
     "./observability/actions/get-observability-review-app": "./dist/observability/actions/get-observability-review-app.js",
     "./observability/actions/get-observability-review-detail": "./dist/observability/actions/get-observability-review-detail.js",
@@ -469,6 +470,7 @@
     "./client/notifications": "./dist/client/notifications/index.js",
     "./progress": "./dist/progress/index.js",
     "./client/progress": "./dist/client/progress/index.js",
+    "./client/problem-report": "./dist/client/problem-report.js",
     "./triggers": "./dist/triggers/index.js",
     "./terminal": "./dist/client/terminal/index.js",
     "./terminal/server": "./dist/terminal/index.js",
@@ -704,7 +706,7 @@
     "yaml": "^2.9.0",
     "yjs": "^13.6.33",
     "zod": "^4.3.6",
-    "@agent-native/agentkit": "^0.209.1",
+    "@agent-native/agentkit": "^0.209.2-nightly-20261015213030",
     "@agent-native/recap-cli": "^0.5.73"
   },
   "devDependencies": {
@@ -775,7 +777,7 @@
     "xlsx": "^0.18.5"
   },
   "peerDependencies": {
-    "@agent-native/core-corpus": ">=0.196.0",
+    "@agent-native/core-corpus": "0.209.2-nightly-20261015213030",
     "@ai-sdk/anthropic": ">=3",
     "@ai-sdk/cohere": ">=3",
     "@ai-sdk/google": ">=3",

package/src/templates/chat/app/components/layout/Sidebar.tsx

@@ -5,6 +5,7 @@ import {
   useChatThreads,
   type ChatThreadSummary,
 } from "@agent-native/toolkit/app/chat/agentkit-chat/rail";
+import { ReportProblemButton } from "@agent-native/toolkit/app/feedback";
 import { OrgSwitcher } from "@agent-native/toolkit/app/org";
 import { openCommandMenu } from "@agent-native/toolkit/app/shared";
 import { AgentNativeIcon } from "@agent-native/toolkit/app/shared/AgentNativeIcon";
@@ -567,7 +568,16 @@ export function Sidebar({
         <ChatThreadsSection collapsed={collapsed} />
       </nav>
 
-      <div className="mt-auto shrink-0 border-t border-sidebar-border p-2">
+      <div
+        className={cn(
+          "mt-auto shrink-0 px-2 pb-1",
+          collapsed && "flex justify-center",
+        )}
+      >
+        <ReportProblemButton variant={collapsed ? "icon" : "sidebar"} />
+      </div>
+
+      <div className="shrink-0 border-t border-sidebar-border p-2">
         <div
           className={cn(
             collapsed

package/src/templates/factory/.agents/skills/review-latest-feedback/SKILL.md

@@ -126,8 +126,8 @@ record source, target, owner, exact action, and verification. Don't reopen
 closed fixes.
 **Clustered** closes one row but retains it.
 
-Enumerate channel parents newest backward through `next_cursor` until older
-than 5 days. Check reactions first; skip marked messages.
+Enumerate channel parents newest-first for five days. For a permalink plus
+newer scope, follow the [checked inventory procedure](references/channel-inventory.md).
 
 **`slack_search` can rank and truncate.** Use channel reads to enumerate parents
 and put their count in the recap. Sort targeted searches oldest-first and follow

package/src/templates/factory/.agents/skills/review-latest-feedback/references/channel-inventory.md

@@ -0,0 +1,31 @@
+# Channel parent inventory
+
+Use this procedure before investigating, claiming, or using a CI rollup in
+place of Slack source messages.
+
+- Read each scoped channel newest-first, following `next_cursor` until the
+  five-day boundary, the inclusive permalink cutoff, or Slack exhaustion.
+- For “this permalink and newer,” use the parent message's `ts` as the inclusive
+  `cutoffTs` and `permalinkTs`. Slack's `oldest` parameter is exclusive, so
+  query from at least one second earlier and filter locally by `ts >= cutoff`.
+- Record every top-level parent returned in every fetched page before filtering
+  or triage. This includes duplicates, owned items, bots, and boundary overlap.
+  Reactions and ownership determine what to investigate, not what to inventory.
+- Save `.tmp/feedback-inventory.json` with `cutoffTs`, optional `permalinkTs`,
+  and `channels`. Set `permalinkTs` when a supplied message anchors the scan. A channel
+  has `channelId`, `oldestQuery`, and `pages`. A page has its requested `cursor`,
+  returned `nextCursor`, `exhausted`, the full Slack `parentCount`, the complete
+  `sourceTimestamps` list copied from that response, and `parents`. Each parent
+  records `ts`, `reactionChecked: true`, `reactionSummary` (`none` if empty),
+  and `disposition`.
+- Keep the source manifest separate from disposition rows. Copy every timestamp
+  and the count from the full Slack response before filtering; the checker
+  compares both lists, catches missing parents and requires the requested
+  permalink timestamp to appear. Continue until a fetched page contains a
+  parent older than cutoff or Slack reports exhaustion.
+- Run `pnpm feedback:inventory-check -- .tmp/feedback-inventory.json`. It checks
+  boundary overlap, page/cursor order, count parity, timestamps, reaction state,
+  and dispositions. Include each channel's parent and page counts in the recap.
+
+A grouped CI report or attachment is a discovery index, never a replacement for
+the channel-parent inventory.