@agent-native/core 0.145.4 → 0.145.6

package/corpus/templates/clips/app/components/recorder/recorder-engine.ts

@@ -10,6 +10,7 @@ import {
 } from "@shared/media-device-selection";
 import {
   SCREEN_CAPTURE_FRAME_RATE,
+  screenCaptureDisplayOptions,
   screenCaptureVideoConstraints,
 } from "@shared/recording-capture";
 import {
@@ -888,16 +889,8 @@ export class RecorderEngine {
       const displaySurface = normalizeDisplaySurfaceForRuntime(
         this.opts.displaySurface ?? "window",
       );
-      const displayOptions: ExtendedDisplayMediaOptions = {
-        video: screenCaptureVideoConstraints(displaySurface),
-        audio: wantsMic,
-        // Let "Browser tab" open the tab picker. preferCurrentTab turns it
-        // into a current-tab shortcut, which makes choosing another tab harder.
-        selfBrowserSurface:
-          displaySurface === "browser" ? "include" : "exclude",
-        surfaceSwitching: "include",
-        systemAudio: wantsMic ? "include" : "exclude",
-      };
+      const displayOptions: ExtendedDisplayMediaOptions =
+        screenCaptureDisplayOptions(displaySurface);
 
       if (wantsMic || wantsDisplay) {
         this.audioMixCtx?.close().catch(() => {});

package/corpus/templates/clips/app/global.css

@@ -36,6 +36,8 @@
   --sidebar-accent-foreground: 0 0% 15%;
   --sidebar-border: 0 0% 90%;
   --sidebar-ring: 0 0% 40%;
+  --highlight: 197 100% 50%;
+  --highlight-foreground: 0 0% 10%;
 }
 
 .dark {
@@ -67,6 +69,13 @@
   --sidebar-accent-foreground: 0 0% 90%;
   --sidebar-border: 0 0% 20%;
   --sidebar-ring: 0 0% 60%;
+  --highlight: 197 100% 50%;
+  --highlight-foreground: 0 0% 10%;
+}
+
+@theme inline {
+  --color-highlight: hsl(var(--highlight));
+  --color-highlight-foreground: hsl(var(--highlight-foreground));
 }
 
 @layer base {

package/corpus/templates/clips/app/routes/r.$recordingId.tsx

@@ -1473,6 +1473,7 @@ export default function RecordingPage() {
                     >
                       <span>{t(item.labelKey)}</span>
                       {item.tooltipKey ? (
+                        // guard:allow-large-help-icon - menu item tooltip icon
                         <IconHelpCircle
                           aria-hidden="true"
                           className="h-3.5 w-3.5 shrink-0 text-muted-foreground/70"

package/corpus/templates/clips/changelog/2026-08-07-screen-recordings-now-capture-tab-and-system-audio-even-when.md

@@ -0,0 +1,6 @@
+---
+type: fixed
+date: 2026-08-07
+---
+
+Screen recordings now capture tab and system audio even when the microphone is off, so transcripts are generated instead of failing with a misleading no-speech message.

package/corpus/templates/clips/changelog/2026-08-07-transcription-now-retries-transient-cloud-failures-automatic.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-08-07
+---
+
+Transcription now retries transient cloud failures automatically, and failure messages say what actually went wrong instead of blaming the recording.

package/corpus/templates/clips/desktop/src-tauri/src/silence_detector.rs

@@ -392,7 +392,6 @@ fn install_call_ended_watcher(app: &AppHandle, threshold_ms: u64) {
             let mut ever_seen_front = false;
             let mut last_front_at: Option<Instant> = None;
             let mut fired = false;
-            let mut last_front_was_generic_browser = false;
             let mut call_app_used_microphone = false;
             let mut microphone_released_at: Option<Instant> = None;
             let mut generation: Option<u64> = None;
@@ -408,7 +407,6 @@ fn install_call_ended_watcher(app: &AppHandle, threshold_ms: u64) {
                     ever_seen_front = false;
                     last_front_at = None;
                     fired = false;
-                    last_front_was_generic_browser = false;
                     call_app_used_microphone = false;
                     microphone_released_at = None;
                     continue;
@@ -417,7 +415,6 @@ fn install_call_ended_watcher(app: &AppHandle, threshold_ms: u64) {
                     ever_seen_front = false;
                     last_front_at = None;
                     fired = false;
-                    last_front_was_generic_browser = false;
                     call_app_used_microphone = false;
                     microphone_released_at = None;
                     generation = Some(active_generation);
@@ -450,7 +447,6 @@ fn install_call_ended_watcher(app: &AppHandle, threshold_ms: u64) {
                 if is_strong_vc || is_generic_browser {
                     ever_seen_front = true;
                     last_front_at = Some(Instant::now());
-                    last_front_was_generic_browser = is_generic_browser;
                 }
                 if fired {
                     continue;
@@ -474,10 +470,18 @@ fn install_call_ended_watcher(app: &AppHandle, threshold_ms: u64) {
                     _ => {}
                 }
 
+                // Require audio corroboration for every trigger in this
+                // watcher: backgrounding the call app, or its process
+                // dropping its mic input, does not by itself prove the call
+                // ended — a browser tab can report either transition while
+                // the meeting is still playing through system audio. Only
+                // quiet mic+system audio alongside the signal does.
+                let audio_quiet = audio_recently_silent(&state, threshold_ms);
+
                 let microphone_released = microphone_release_stop_ready(
                     call_app_used_microphone,
                     microphone_released_at.map(|at| Instant::now().duration_since(at)),
-                );
+                ) && audio_quiet;
 
                 let frontmost_call_ended = ever_seen_front
                     && last_front_at
@@ -485,12 +489,7 @@ fn install_call_ended_watcher(app: &AppHandle, threshold_ms: u64) {
                             Instant::now().duration_since(t).as_millis() as u64 >= threshold_ms
                         })
                         .unwrap_or(false)
-                    // Require audio corroboration for browser-hosted calls:
-                    // backgrounding Chrome/Arc alone does not prove that the
-                    // Meet tab ended. Use the last known conference app, not
-                    // the unrelated app now in front.
-                    && (!last_front_was_generic_browser
-                        || audio_recently_silent(&state, threshold_ms));
+                    && audio_quiet;
 
                 if microphone_released || frontmost_call_ended {
                     let _ = app.emit("meetings:call-ended", ());

package/corpus/templates/clips/server/db/schema.ts

@@ -246,6 +246,13 @@ export const recordingTranscripts = table("recording_transcripts", {
     .notNull()
     .default("pending"),
   failureReason: text("failure_reason"),
+  // The MACHINE-READABLE reason, and the one that decides retryability — see
+  // shared/transcript-failure.ts. `failureReason` above is prose rendered from
+  // this and is for humans only; production accumulated 39 distinct strings
+  // for what turned out to be a handful of conditions, and retryability was
+  // being re-derived by regex over that prose. Nullable for rows written
+  // before this column existed.
+  failureCode: text("failure_code"),
   // Count of automatic retries already attempted after a transient failure
   // (ffmpeg timeout, transient provider/network error). Bounds the
   // fire-and-forget auto-retry pass in request-transcript.ts so a repeatedly

package/corpus/templates/clips/server/plugins/db.ts

@@ -1146,6 +1146,14 @@ const migrations = runMigrations(
         expires_at INTEGER NOT NULL
       )`,
     },
+    {
+      version: 64,
+      name: "recording-transcripts-failure-code",
+      // Additive. Existing rows keep failure_code NULL and their prose; new
+      // failures record a code that owns retryability instead of having it
+      // re-derived by regex over the message.
+      sql: `ALTER TABLE recording_transcripts ADD COLUMN failure_code TEXT`,
+    },
   ],
   { table: "clips_migrations" },
 );

package/corpus/templates/clips/shared/recording-capture.ts

@@ -35,3 +35,41 @@ export function screenCaptureVideoConstraints(
     displaySurface,
   };
 }
+
+export type ScreenCaptureDisplayOptions = {
+  video: ScreenCaptureVideoConstraints;
+  audio: boolean;
+  selfBrowserSurface: "include" | "exclude";
+  surfaceSwitching: "include" | "exclude";
+  systemAudio: "include" | "exclude";
+};
+
+/**
+ * The `getDisplayMedia` options for a screen recording.
+ *
+ * Screen/tab audio is requested ALWAYS, and deliberately does not depend on
+ * whether the microphone is on. They are two different sources, and one toggle
+ * used to govern both: with the mic off, Chrome was never even offered the
+ * "share tab audio" checkbox, so a screen recording of a call or a demo
+ * captured zero audio tracks. Measured in production, 345 recordings landed
+ * with `has_audio = false` — 95 over a minute, 17 over five — and each was told
+ * "No speech was detected because this recording was saved without audio",
+ * blaming the recording for a capture setting. That was 64% of recent
+ * transcript failures. The Chrome extension always requested display audio and
+ * never had the problem.
+ *
+ * Declining the checkbox is still respected; the user simply gets the choice.
+ */
+export function screenCaptureDisplayOptions(
+  displaySurface: ScreenCaptureSurface,
+): ScreenCaptureDisplayOptions {
+  return {
+    video: screenCaptureVideoConstraints(displaySurface),
+    audio: true,
+    // Let "Browser tab" open the tab picker. preferCurrentTab turns it into a
+    // current-tab shortcut, which makes choosing another tab harder.
+    selfBrowserSurface: displaySurface === "browser" ? "include" : "exclude",
+    surfaceSwitching: "include",
+    systemAudio: "include",
+  };
+}

package/corpus/templates/clips/shared/transcript-failure.ts

@@ -0,0 +1,89 @@
+/**
+ * One vocabulary for why a transcript did not happen.
+ *
+ * Production accumulated **39 distinct `failure_reason` strings** across 1100
+ * failed rows, introduced on five separate dates across four files and three
+ * capture surfaces. No commit ever owned the terminal-failure vocabulary, so
+ * every fix added its own sentence. Two of those strings were the same
+ * condition renamed ("backup transcription" → "Builder transcription"), which
+ * silently forked every downstream count.
+ *
+ * Worse, a typed code already existed (`AudioOnlyExtractionErrorCode`), was
+ * thrown, and was discarded at the persistence boundary — after which
+ * retryability was re-derived by running regexes over the English prose. A
+ * message reworded for clarity could therefore change whether a transcript
+ * retried.
+ *
+ * So: the CODE is the record, prose is rendered from it, and retryability is a
+ * property of the code. Adding a failure mode means adding one entry here, not
+ * a new sentence at a call site.
+ */
+
+/** Why a transcript ended in `failed`. Persisted; do not renumber or reword. */
+export type TranscriptFailureCode =
+  // --- audio extraction (mirrors AudioOnlyExtractionErrorCode) ---
+  | "NO_AUDIO_TRACK"
+  | "NO_SPEECH_DETECTED"
+  | "FFMPEG_UNAVAILABLE"
+  | "EXTRACTION_FAILED"
+  | "TIMEOUT"
+  // --- transcript level ---
+  /** The recording itself was saved with no audio stream at all. */
+  | "NO_AUDIO_SAVED"
+  /** Cloud transcription was attempted and threw. */
+  | "CLOUD_FAILED"
+  /** No cloud provider is connected for this owner. */
+  | "CLOUD_UNCONFIGURED"
+  /** Anything not yet classified. Prose is preserved; never retried blindly. */
+  | "UNKNOWN";
+
+/**
+ * Codes worth retrying automatically.
+ *
+ * Retrying anything else wastes a media fetch and an ffmpeg run to reach the
+ * same answer — `NO_AUDIO_SAVED` in particular is a measurement of the stored
+ * file, so no number of retries will find audio that was never captured.
+ */
+const RETRYABLE: ReadonlySet<TranscriptFailureCode> = new Set([
+  "TIMEOUT",
+  "EXTRACTION_FAILED",
+  "CLOUD_FAILED",
+]);
+
+export function isRetryableTranscriptFailure(
+  code: TranscriptFailureCode | null | undefined,
+): boolean {
+  return code != null && RETRYABLE.has(code);
+}
+
+/**
+ * The sentence shown to a person, derived from the code.
+ *
+ * Each says what happened and what the reader can do about it. None of them
+ * blames the recording for a capture setting — "no speech was detected" on a
+ * recording saved without audio was the single most common transcript failure
+ * in production, and it sent people looking for a microphone problem when the
+ * screen-share simply never included audio.
+ */
+export function transcriptFailureMessage(code: TranscriptFailureCode): string {
+  switch (code) {
+    case "NO_AUDIO_SAVED":
+      return "This recording has no audio track, so there was nothing to transcribe. Screen recordings only capture audio when you share tab or system audio, or record with a microphone.";
+    case "NO_AUDIO_TRACK":
+      return "The saved media has no audio stream, so there was nothing to transcribe.";
+    case "NO_SPEECH_DETECTED":
+      return "Audio was captured but no speech was found in it.";
+    case "FFMPEG_UNAVAILABLE":
+      return "Audio could not be prepared for transcription because ffmpeg is unavailable on the server.";
+    case "EXTRACTION_FAILED":
+      return "Audio could not be prepared for transcription. Retrying usually works.";
+    case "TIMEOUT":
+      return "Transcription timed out before it finished. Retrying usually works.";
+    case "CLOUD_FAILED":
+      return "No transcript was captured locally, and cloud transcription could not finish. Retrying usually works; if it persists, check the recording's audio and the Builder connection.";
+    case "CLOUD_UNCONFIGURED":
+      return "No transcript was captured locally, and no cloud transcription provider is connected. Connect Builder in Settings to transcribe automatically.";
+    case "UNKNOWN":
+      return "Transcription did not finish.";
+  }
+}

package/corpus/templates/content/.agents/skills/actions/SKILL.md

@@ -20,6 +20,24 @@ Before creating any custom REST/API route for app data, inspect `actions/` and t
 
 **Stop trigger:** the moment you are about to create a file under `server/routes/api/` — or add server middleware to guard one — stop and check it against the exception list in *When You Still Need Custom `/api/` Routes* below. If it is not on that list, write a `defineAction` instead. This applies even when you already started the route; abandoning a half-written action to hand-roll routes is the exact failure this rule exists to prevent.
 
+## Keep actions deterministic and composable
+
+An action may call a provider API, validate or normalize data, and persist
+records without being an AI feature. Keep those operations deterministic,
+focused, and independently useful to the agent. Do not put LLM calls or a
+second model runtime in ordinary actions. The only narrow exception is the
+`completeText()` text-in/text-out escape hatch described in
+`delegate-to-agent`; it must not own tools, chat history, run state, side
+effects, or user steering.
+
+When a workflow is framed as research, analysis, generation, recommendation,
+or synthesis, or spans several provider calls and writes, route the user into
+the AgentSidebar and let the agent orchestrate focused actions. Do not hide an
+AI-shaped workflow behind one opaque `generate-*` or `create-*` action just
+because its implementation is deterministic. A visible user-initiated run
+should use `sendToAgentChat({ openSidebar: true })`, and its follow-ups should
+continue in the same thread rather than a separate freeform input.
+
 ## Why
 
 Actions give the agent callable tools with structured input/output, AND they give the frontend a typed client contract through hooks. One implementation serves both the agent and the UI. They keep the agent's chat context clean, they're reusable, and they can be tested independently.

package/corpus/templates/content/.agents/skills/agent-native-toolkit/SKILL.md

@@ -56,6 +56,11 @@ The repeated app shell has two distinct navigation surfaces:
   labeled as local, preview, or analyze. For original/generated review, stack
   the source above the result by default and use side-by-side only for short,
   highly scannable content.
+- Deterministic implementation does not make an AI-shaped experience
+  deterministic. If the user expects research, analysis, generation,
+  recommendation, synthesis, visible progress, or steering, route the button
+  to the AgentSidebar and let the agent call focused actions. Keep revisions in
+  the same thread instead of adding a second freeform prompt box.
 - Standalone apps with `AgentSidebar` must resolve one assistant-ui runtime
   context. Match direct assistant-ui pins to the installed core/toolkit peer
   graph, use Vite dedupe/aliases when linked dependencies can split contexts,

package/corpus/templates/content/.agents/skills/delegate-to-agent/SKILL.md

@@ -14,11 +14,21 @@ metadata:
 
 ## Rule
 
-The UI never calls an LLM directly. Product workflows are delegated to the
-agent through the chat bridge so users can see, steer, and audit the work.
-Server-side one-shot model calls are an explicit escape hatch for narrow text
-transforms only; use `completeText()` from `@agent-native/core/server` when the
-work intentionally does not need tools, chat history, or run state.
+The app's default AI surface is the agent chat. Any user-facing work that asks
+the model to research, analyze, generate, recommend, synthesize, or reason over
+multiple steps must start or continue in the AgentSidebar so users can see,
+steer, and audit the work. UI buttons use `sendToAgentChat()` with
+`openSidebar: true`, and follow-up or revision text belongs in that same thread
+instead of a second app-local textbox.
+
+Actions are tools, not alternate AI runtimes. Keep them deterministic and
+focused: provider reads, validation, deterministic transforms, CRUD, and
+persistence are good action work. Let the agent orchestrate several such tools
+when the workflow is AI-shaped or user-steerable. Server-side one-shot model
+calls are a rare escape hatch for narrow text transforms only; use
+`completeText()` from `@agent-native/core/server` only when the work
+intentionally does not need tools, chat history, run state, side effects, or
+user steering.
 
 ## Why
 
@@ -35,6 +45,7 @@ sendToAgentChat({
   message: "Generate a summary of this document",
   context: documentContent, // optional hidden context (not shown in chat UI)
   submit: true, // auto-submit to the agent
+  openSidebar: true,
 });
 ```
 
@@ -56,6 +67,10 @@ sendToAgentChat({
 This is still a full agent run: tools, actions, thread state, and run tracking
 all remain active. It simply does not focus or open the sidebar.
 
+Use this silent form only for explicitly background or system-initiated work.
+It is not the default for a user clicking an AI-labeled button; visible work
+should open the sidebar so the user can follow and redirect the run.
+
 **From scripts (Node):**
 
 ```ts
@@ -77,8 +92,9 @@ const result = await completeText({
 });
 ```
 
-Wrap user-facing uses in actions so the UI and agent share the same operation.
-Do not call provider SDKs directly.
+If the narrow exception is exposed to the UI, wrap it in an action so the UI
+and agent share the same operation. Keep it clearly non-conversational and do
+not call provider SDKs directly.
 
 **From the UI, detecting when agent is done:**
 
@@ -97,9 +113,9 @@ The `submit` option controls whether the message is sent automatically or placed
 
 | `submit` value | Behavior                                | Use when                                                                            |
 | -------------- | --------------------------------------- | ----------------------------------------------------------------------------------- |
-| `true`         | Auto-submits to the agent immediately   | Routine operations the user has already approved                                    |
-| `false`        | Prefills the chat input for user review | High-stakes operations (deleting data, modifying code, API calls with side effects) |
-| omitted        | Uses the project's default setting      | General-purpose delegation                                                          |
+| `true`         | Auto-submits to the agent immediately   | Routine operations with clear intent; keep `openSidebar: true` for visible work |
+| `false`        | Prefills the AgentSidebar composer      | Review, edit, or add detail before the run; use the existing sidebar thread   |
+| omitted        | Uses the project's default setting      | General-purpose delegation                                                       |
 
 ```ts
 // Auto-submit: routine operation
@@ -109,61 +125,43 @@ sendToAgentChat({ message: "Update the project summary", submit: true });
 sendToAgentChat({
   message: "Delete all projects older than 30 days",
   submit: false,
+  openSidebar: true,
 });
 ```
 
-## Capture user input first when generating from a prompt
-
-Buttons that produce new content ("New Design", "Create Dashboard", "Make Deck", "Generate Form") need the user's prompt as input. **Never hardcode a generic message** — the result will be a generic generation the user didn't actually ask for.
+## Capture user input in the sidebar
 
-**Bad** — auto-submits a placeholder message; the user never said what they wanted:
+The AgentSidebar composer is the default prompt surface. When a button needs
+the user to describe what to create, prefill that same composer and let the
+user edit or complete it:
 
 ```tsx
 <Button
   onClick={() =>
-    sendToAgentChat({ message: "make a design", submit: true })
+    sendToAgentChat({
+      message: "Help me create a research report from this brief:",
+      context: researchBrief,
+      submit: false,
+      openSidebar: true,
+    })
   }
 >
-  New Design
+  Start in agent
 </Button>
 ```
 
-**Good** — Popover anchored to the button captures the prompt, then submits it:
-
-```tsx
-<Popover open={open} onOpenChange={setOpen}>
-  <PopoverTrigger asChild>
-    <Button>New Design</Button>
-  </PopoverTrigger>
-  <PopoverContent className="w-96">
-    <Textarea
-      autoFocus
-      value={prompt}
-      onChange={(e) => setPrompt(e.target.value)}
-      placeholder="What do you want to design?"
-    />
-    <Button
-      onClick={() => {
-        sendToAgentChat({ message: prompt, submit: true });
-        setOpen(false);
-        setPrompt("");
-      }}
-    >
-      Create
-    </Button>
-  </PopoverContent>
-</Popover>
-```
-
-**Always ask for input first when** the output depends on a prompt the user must provide — "design what?", "deck about what?", "dashboard for which metric?", "form for which use case?".
-
-**Auto-submit without input is fine when intent is unambiguous:**
+Never auto-submit a generic creative prompt when the user has not said what
+they want. Auto-submit without additional input is fine when intent is
+unambiguous:
 
 - "Try to fix" on a tool error — submits the error details with a clear fix instruction
 - "Retry the last operation" after a transient failure
 - Single-purpose buttons where there is nothing meaningful for the user to add
 
-If you find yourself writing `submit: true` with a hardcoded creative verb (`"design a..."`, `"write a..."`, `"build a..."`), stop and add a Popover.
+Use a Popover only for compact, structured parameters the UI must validate,
+such as a date range, target, or approval choice. Do not add a second freeform
+prompt or follow-up textbox for an AI workflow; keep the conversation and
+revisions in the AgentSidebar thread.
 
 ## Delegating to a Sub-Agent (Agent Teams)
 

package/corpus/templates/content/.agents/skills/frontend-design/SKILL.md

@@ -130,6 +130,7 @@ passed this requirement yet.
 - Do not build custom dropdowns, menus, popovers, modals, or confirmations with manual absolute positioning and click-outside effects.
 - Never use browser dialogs (`window.alert`, `window.confirm`, `window.prompt`). Use `AlertDialog`, `Dialog`, or app-specific confirmation UI.
 - Use Tabler icons for all first-party UI icons. Do not add Lucide, Heroicons, inline SVG icon sets, or emoji icons.
+- Keep inline help/info glyphs next to labels at `size-3` (12px) or smaller than the adjacent text. Preserve a larger hit area on the trigger, not the glyph. Use `guard:allow-large-help-icon` only for deliberate heading documentation or menu action exceptions.
 - Use `useActionQuery` and `useActionMutation` from `@agent-native/core/client` for action-backed UI. Standard CRUD should go through actions, not custom `/api/` routes.
 - Keep UI optimistic where possible: update cache and navigation immediately, then reconcile or roll back on mutation result.
 - Custom styles belong in Tailwind classes, component CSS, or the existing global CSS theme file; avoid inline styles.

package/corpus/templates/content/.agents/skills/turn-into-app/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: turn-into-app
 description: >-
-  Turn a proven thread, skill, or workflow into a runnable Agent-Native app
-  with simple buttons, visible agent steps, preview, and deployment handoff.
-  Use when a user invokes `/turn-into-app` or asks to make a workflow into an
-  app.
+  Turn visible project context, a proven thread, skill, or workflow into a
+  runnable Agent-Native app with simple buttons, visible agent steps, preview,
+  and deployment handoff. Use when a user invokes `/turn-into-app` or asks to
+  make a workflow into an app.
 user-invocable: true
 scope: both
 metadata:
@@ -17,34 +17,72 @@ metadata:
 
 This is an end-to-end build skill, not a request for an app proposal.
 
-- With no argument, use the current thread as the source. This is the normal
-  invocation at the end of a successful workflow.
+- With no argument, choose the source in this order: visible project context,
+  then the current thread. A fresh Claude or ChatGPT Project is a valid source
+  on its first turn. Treat its visible project instructions, knowledge files,
+  and supplied past runs as the source; a completed thread is not required.
+  Treat the current turn as a request or configuration unless it contains a
+  concrete repeatable workflow.
 - With a named skill or local workflow, read that source and package it
   immediately, even at the beginning of a thread. For example,
   `/turn-into-app /some-skill` means “turn `/some-skill` into an app.”
 - With an attachment or path, read the supplied artifact as the source.
 - Do not ask the user to restate context that is already in the thread.
-- When invoked from an Agent-Native app, keep the current thread as the source
-  and use the available workspace/coding-agent handoff when the current runtime
-  cannot edit files. Do not claim the app exists without an actual path and
-  verification result.
+- When invoked from an Agent-Native app, use its visible project context first,
+  then the current thread, and use the available workspace/coding-agent
+  handoff when the current runtime cannot edit files. Do not claim the app
+  exists without an actual path and verification result.
 
 ## Source support
 
-Supported source paths today are the current Codex thread, a named skill, or a
-local workflow/transcript supplied as a path or attachment. An exported
-ChatGPT or Claude transcript can use the same local-file path today.
+Supported source paths today are visible Claude or ChatGPT Project context, the
+current Codex or host thread, a named skill, or a local workflow/transcript
+supplied as a path or attachment. An exported ChatGPT or Claude transcript can
+use the same local-file path today.
 
-ChatGPT shared-conversation import and Claude web conversation/project import
-are **coming soon**. Do not claim private web access, invent an importer, add
-fake OAuth, or scrape a logged-in page without an explicit supported adapter.
-If a user gives one of those URLs before an adapter exists, ask for an export or
-transcript instead and treat it as imported source material.
+Claude and ChatGPT Project context is supported only when the host supplies it
+to the model in the current context. The MCP connector does not read hidden
+project chats, private URLs, account settings, or credentials. Do not claim
+private web access, invent an importer, add fake OAuth, or scrape a logged-in
+page. If the needed context is not visible, ask for an export, transcript, or
+attachment and treat that artifact as imported source material.
 
 Deliver a fresh app in a new directory, implement the repeatable workflow with
 buttons and agent handoffs, start its dev server, verify the main path, and
 continue through build/deployment handoff. Do not stop at a plan.
 
+## Fresh project context mode
+
+When the source is a fresh Claude or ChatGPT Project, build a short source brief
+before creating the app. Read the host-provided context in this order:
+
+1. Project instructions and configuration: goal, audience, constraints, output
+   standards, approved tools, and integration expectations. Treat these as
+   product configuration, not as a transcript.
+2. Knowledge files and attachments: read the relevant files fully, preserve
+   their provenance, and reduce them to bounded references, IDs, URLs, or
+   summaries for the new app. Do not copy secrets or large raw payloads into
+   prompts or SQL.
+3. Past runs or examples that are actually visible in the context: select at
+   most 1-3 successful, representative runs. Extract repeatable decisions and
+   review criteria. Treat one-off answers and private data as examples, not as
+   product behavior. If no runs are supplied, proceed from the instructions
+   and knowledge files and say that examples were not available.
+4. The current turn: use it for the requested app boundary, target workspace,
+   naming, and any explicit corrections.
+
+Record the brief with these headings before handoff: source and provenance,
+project goal, configuration and constraints, knowledge sources, repeatable
+workflow, inputs and outputs, judgment and review points, representative runs,
+integrations and permissions, and unknowns. This is the compact contract for
+the app. It keeps the new app useful without pretending that hidden Project
+history was imported. See [the fresh Project reference](references/fresh-project.md)
+for the host setup and brief template.
+
+If the visible Project context has no concrete repeatable job, ask for one
+focused clarification or a representative artifact. Do not fall back to a
+generic “what app do you want to make?” builder.
+
 ## Source selection guard
 
 The generated app must implement the concrete workflow found in the source. It
@@ -151,6 +189,14 @@ pnpm exec agent-native add-app <slug> --template=chat
 Do not use `create` for an existing workspace; it scaffolds a new standalone
 workspace rather than adding an app to the current one.
 
+When the source came from a fresh external Project and the target is a Builder
+workspace, prefer the available Dispatch MCP workspace handoff after writing
+the source brief. Call `start-workspace-app-creation` with a concise prompt,
+the inferred app id, and the brief's repeatable workflow. Pass selected
+workspace resource IDs when they are available, rather than pasting entire
+knowledge files. Continue from the returned workspace path or Builder handoff
+and report the actual verification result.
+
 Use a first-party template only when it materially fits the workflow. Keep the
 new app independent from the source thread's working tree unless the user
 explicitly asks to extend an existing app.
@@ -167,13 +213,20 @@ should make the repeated path obvious without hiding the agent's judgment:
 - Give each important repeated moment a clear button, such as “Analyze,”
   “Suggest options,” “Draft,” “Review,” or “Publish.” Use the source's actual
   vocabulary when it is clear.
-- Put deterministic reads, writes, approvals, and publishing in `actions/`
-  with `defineAction`. The UI and agent must call the same action surface.
+- Put deterministic reads, writes, approvals, provider fetches, and publishing
+  in focused `actions/` with `defineAction`. The UI and agent must call the
+  same action surface.
+- If a workflow is framed as research, analysis, generation, recommendation,
+  or synthesis, start it in the AgentSidebar and let the agent orchestrate
+  those actions. Do not hide an AI-shaped multi-step workflow behind one
+  opaque action just because the implementation is deterministic.
 - Use application state for the current screen, selected item, and focused
   object so the agent can see where the user is.
-- Use `sendToAgentChat({ message, context, submit: true })` for intentional
-  button-triggered agent work. Use `submit: false` when the user should review
-  or edit the proposed prompt first.
+- Use `sendToAgentChat({ message, context, submit: true, openSidebar: true })`
+  for intentional button-triggered agent work. Use `submit: false` when the
+  user should review or edit the proposed prompt in the AgentSidebar first.
+  Keep follow-up and revision prompts in that same thread; do not add a second
+  freeform textbox beside the result.
 - Pass IDs, URLs, and bounded summaries in context. Do not paste large provider
   dumps into prompts, call an LLM directly from the browser, or invent fake
   progress.