@mindstudio-ai/remy 0.1.337 → 0.1.339

package/dist/prompt/compiled/interfaces.md

@@ -43,12 +43,23 @@ All fields are nested under the `"web"` key.
 | `devPort` | `number` | `5173` | Port for the dev server |
 | `devCommand` | `string` | `"npm run dev"` | Command to start the dev server |
 | `defaultPreviewMode` | `"desktop"` \| `"mobile"` | `"desktop"` | Default preview viewport in the editor. Set to `"mobile"` for mobile-first apps. |
+| `previewLinks` | `array` | — | A few places worth opening directly, as chips under the editor's preview address bar. See "Preview links" below. |
 | `prerender` | `object` | — | Opt into prerendering the listed routes/patterns for crawlers/unfurlers. See "Prerendering" below. |
 | `mounts` | `array` | — | Serve other same-workspace apps under path prefixes of this app's hosts. See "Mounting other apps" below. |
 | `redirects` | `array` | — | Path-level redirects. See "Redirects" below. |
 | `rewrites` | `array` | — | Serve different content at the same URL. See "Rewrites" below. |
 | `trailingSlash` | `"strip"` \| `"append"` | — | Enforce a canonical trailing-slash form with a 308. Off by default. |
 
+### Preview links
+
+`{ "web": { "previewLinks": [{ "label": "Admin console", "path": "/console" }] } }` — each entry a short human `label` and a `/`-prefixed `path` on this app. The editor shows them as chips under the preview's address bar so the user can reach a place in one click. Order is preserved; a chip for an agent interface's `webInterfacePath` is appended automatically unless an entry already points there.
+
+Curate these with the same judgement as scenarios — a few places worth visiting, not a chip per route. Four good ones beat fifteen. Highest value first: surfaces nothing links to (an admin console behind its own sign-in), pages needing a token or id in the URL (point them at a record the scenarios seed, using its known id/slug, so the link lands on real content), and role-gated routes where hitting the sign-in screen is itself worth seeing. Then two or three ordinary pages carrying the most of the app's character — a populated list, a detail view with real data, the screen where the main workflow happens.
+
+Leave the root out. The address bar directly above these chips already has back, forward, refresh and home buttons.
+
+Write them after the scenarios, when you know which ids and slugs exist. Paths aren't validated — revisit the list when you rename a route, or the chip 404s.
+
 ### Frontend SDK
 
 ```typescript

package/dist/prompt/static/coding.md

@@ -82,8 +82,8 @@ You have access to the `mindstudio` CLI, which exposes every SDK action as a com
 ### Production App Management
 You have access to `remy-admin`, a CLI for managing the user's production app. Use it via your bash tool. All output is JSON. Run `remy-admin --help` or `remy-admin <command> --help` to discover usage and available options.
 
-Available commands: `requests` (server logs, errors, latency), `crashes` (frontend browser errors), `analytics` (traffic queries — lifetime metrics, sources, live counters), `releases`, `diagnostics` (Lighthouse audit), `domains`, `users` (list, set roles), `db` (query production sql), `data` (live db operations like lift-from-dev), `methods` (list, invoke), `secrets`, `files` (CDN files), `datasources` (document corpora: add, search, `inspect` a bucket or store, bulk `jobs` with a plan, S3 `connect`/`sync`, mappers via `map test`/`remap`, `eval`), `infra` (dedicated retrieval capacity for large corpora), `prerender` (crawler snapshots), `voice` (phone numbers, call logs, voice policy), `issues` (externally-reported bugs), `settings` (app settings: signup restrictions, app-store-reviewer test accounts, embedding origins, toggles).
+Available commands: `requests` (server logs, errors, latency), `crashes` (frontend browser errors), `analytics` (traffic queries — lifetime metrics, sources, live counters), `releases`, `diagnostics` (Lighthouse audit), `domains`, `users` (list, set roles), `db` (query production sql), `data` (live db operations like lift-from-dev), `methods` (list, invoke), `secrets`, `files` (CDN files), `datasources` (document corpora: add, search, `inspect` a bucket or store, bulk `jobs` with a plan, S3 `connect`/`sync`, mappers via `map test`/`remap`, `eval`), `infra` (dedicated retrieval capacity for large corpora), `prerender` (crawler snapshots), `voice` (phone numbers, call logs, voice policy), `issues` (the app's issue tracker: bugs its own users reported, and requests other apps in the workspace filed; `--app` reads or files into another app's tracker), `settings` (app settings: signup restrictions, app-store-reviewer test accounts, embedding origins, toggles).
 
-Two rules: buying a `voice` phone number bills $1/month — never buy without the user's explicit confirmation. `issues` is for externally-reported bugs only — read from it and resolve items when the user asks; never use it to track work you are doing with the user.
+Two rules: buying a `voice` phone number bills $1/month — never buy without the user's explicit confirmation. `issues` is inbound from other people, not your scratchpad: never file your own work-in-progress there, and never use it to track what you and the user are part-way through. Do act on what arrives — a bug an end-user reported, or a request another app filed — and reply on the thread rather than only in chat, because the app that filed it reads your comments and has no other way to hear back.
 
 Use when the user asks about production behavior (server errors via `requests`, browser crashes via `crashes`, traffic/engagement via `analytics`), wants to manage their live app (domains, users, roles), needs to seed or query production data, or wants to check release status.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindstudio-ai/remy",
-  "version": "0.1.337",
+  "version": "0.1.339",
   "description": "Remy coding agent",
   "repository": {
     "type": "git",