agentui open, files filters and bulk delete (0.3.0)

CHANGELOG.md

@@ -8,6 +8,15 @@
 - `agentui update` updates a Windows install; npm installs still update with npm.
 - Login: the email-code relay is spelled out as the assistant's job — ask for the
   email, run step 1, ask the user to paste the code, run step 2.
+- `agentui open <target> [value]`: a link to the right place in the web app for this
+  project (a table, a setting, a panel, a missing secret, an integration's connect
+  screen), checked by the platform. `agentui open` alone lists targets and what the
+  project is waiting on. Replaces "go to the dashboard" and hand-built `/dl` links.
+- `agentui project link` is described as what it is: a preview login token.
+- `agentui files delete` takes many ids and reports `deleted` / `notFound` / `failed`;
+  it exits 1 if anything was not deleted.
+- `agentui files list` filters: `--category`, `--since`, `--before`, `--min-size`,
+  `--max-size`, `--visibility`, `--sort`, `--order`.
 
 ## 0.2.0
 

skills/agentui-app-data/SKILL.md

@@ -70,6 +70,9 @@ agentui data security suggest Invoice \
   --reason "Financial records"
 ```
 
+`agentui open security <Table>` with the same flags prints the same link, and
+`agentui open` alone lists the tables that have no rules yet.
+
 A proposal that would match no records — a field or user property that does not exist —
 is refused before the link is minted, because accepting one locks every user out of
 their own data with no error.

skills/agentui-app-files/SKILL.md

@@ -16,10 +16,11 @@ agentui files upload ./report.pdf                 # private by default → retur
 agentui files upload ./logo.png --public          # permanent URL anyone with the link can read
 agentui files upload ./data.csv --name q3.csv --type text/csv
 agentui files list --search invoice --mine
+agentui files list --category image --since 2026-09-01 --sort size --order desc
 agentui files download <fileId> --out ./here/
 agentui files url <fileId>                        # temporary share link (prints expiry + scope)
 agentui files publish <fileId> --yes              # make an existing private file public
-agentui files delete <fileId> --yes
+agentui files delete <fileId> [fileId...] --yes  # permanent; many ids at once
 ```
 
 ## Rules that matter
@@ -40,4 +41,16 @@ agentui files delete <fileId> --yes
   and flags the result as truncated — continue from the offset it reports rather than
   assuming you saw the whole workspace.
 
+- `files list` filters: `--category` (image, video, audio, pdf, spreadsheet,
+  document, archive, other), `--since` / `--before` (dates), `--min-size` /
+  `--max-size` (bytes), `--visibility public|private`, `--sort createdAt|name|size`,
+  `--order asc|desc`. The platform checks each one: a bad value is refused with the
+  allowed values listed.
+- `files delete` removes the file from storage and the database, and it cannot be
+  undone. Confirm with the user, list exactly which files, and only then pass `--yes`.
+  It accepts many ids and sends them in batches of 100. If any id is not found or
+  storage refuses it, the command exits 1 with `deleted`, `notFound` and `failed` in
+  the payload. Report those counts; do not say "deleted" when only some were.
+  `failed` files are still stored, and the error message includes the retry command.
+
 Use `--json` and read back the `id` — that is what every other files command takes.

skills/agentui-integrations/SKILL.md

@@ -23,8 +23,9 @@ agentui integrations alerts                      # auth expired, rate limits, re
 ```
 
 Config, tokens and auth state are **never returned** — only the type and whether it is
-connected. If something the app needs is not authenticated, say so and let the user
-connect it in the dashboard; you cannot do it from here.
+connected. If something the app needs is not authenticated, say so and hand the user
+`agentui open integration <provider>` — a link to the connect screen for that
+provider. You cannot connect it from here.
 
 Before writing HTTP calls by hand, check `agentui guide external-api` and
 `agentui integrations docs <platform>`. The platform handles credentials, encryption,

skills/agentui-platform/SKILL.md

@@ -103,7 +103,14 @@ alternative you were about to propose is a weekend of scaffolding.
 4. **Ask before shipping to production.** `push` refuses production without `--yes`,
    and so should you. Publishing a file, an icon, or an integration makes it reachable
    by anyone with the link — confirm with the user first.
-5. **Report walls.** When a command is wrong, missing or misleading, run
+5. **Send the user to the right place with `agentui open`.** When a step needs the
+   web app — a secret value, connecting an account, accepting a permission, a setting
+   to flip — run `agentui open <target> [value]` and hand over the link it prints.
+   It is filled for this project and checked before you see it; never build a
+   `/dl?…` URL by hand. `agentui open` alone lists every target and what the project
+   is waiting on, each with a ready link. `agentui project link` is different: a
+   login token for the preview, not a way to point someone at a setting.
+6. **Report walls.** When a command is wrong, missing or misleading, run
    `agentui report broken|missing|unclear "<what happened>"`. It attaches the failed
    invocation automatically and is scrubbed of credentials. A workaround you keep to
    yourself leaves the wall up for everyone.

skills/agentui-ship-app/SKILL.md

@@ -210,7 +210,9 @@ this one workflow** — a sibling automation in the same app does not inherit th
 ```bash
 agentui project open                      # the editor, in the browser
 agentui project open --preview --print    # the PRODUCTION app URL (see the warning below)
-agentui project link                      # pre-authed deep link, 7 days
+agentui open                              # what the project needs from a person, with links
+agentui open setting ssoEnabled           # a link to one place in the web app (see below)
+agentui project link                      # pre-authed LOGIN link to the preview, 7 days
 agentui project link --scope iframe       # 1 hour, for embedding
 agentui project icon logo.png --yes       # app icon → all PWA sizes + rebuild
 ```
@@ -220,8 +222,12 @@ consult `agentui env current`. **After building a non-production environment, do
 hand the user that URL**: take `previewUrl` from the `--build` output, or the
 environment's own URL from `agentui env status`.
 
-A `project link` lets anyone holding it act as the user in that workflow until it
-expires — hand it over only on a channel the user chose.
+`agentui open <target> [value]` is how you point the user at a place in the web app —
+a table, a setting, a panel, the box for a missing secret. Run `agentui open` alone for
+the targets; an unknown table or setting is refused with the valid values.
+
+A `project link` is a login token, not a pointer: anyone holding it acts as the user in
+that workflow until it expires — hand it over only on a channel the user chose.
 
 ## Blueprints