@notis_ai/cli 0.2.0-beta.16.1 → 0.2.0-beta.161.1

package/README.md

@@ -1,21 +1,56 @@
 # @notis_ai/cli
 
-Agent-first Notis CLI for apps, databases, and generic tool execution.
+Agent-first Notis CLI for apps and generic tool execution.
 
 ## Install
 
-The Notis CLI is bundled automatically with the Notis desktop app.
+Requires Node.js 22.12.0 or newer (Node 24 LTS recommended). Update Node.js before installing or running the CLI; the CLI never upgrades your host runtime.
+
+Use the Notis CLI through NPX; do not rely on an installed `notis` command. Run `notis login` once to authorize a scoped, revocable OAuth credential in the browser — that is how the CLI signs in everywhere, including on a machine that also runs Notis Desktop.
+
+After local login, the CLI idempotently adds static Notis guidance to detected Codex and Claude Code user instruction files without changing their hooks. Run `notis agents install` when you explicitly want memory hooks that load the user's profile at session start, recall only new relevant memories before prompts, and save completed turns as automatic cross-session context. Codex then asks you to review and trust those hooks once in `/hooks`.
+
+For CI, hosted agents, or internal scripts, pass a non-persisted token with `NOTIS_JWT=<token>`.
 
 ## Quick Start
 
 ```bash
-notis --help
-notis auth status
-notis apps list
-notis db list
+npx --package @notis_ai/cli@latest -- notis --help
+npx --package @notis_ai/cli@latest -- notis login
+npx --package @notis_ai/cli@latest -- notis doctor
+npx --package @notis_ai/cli@latest -- notis apps list
+npx --package @notis_ai/cli@latest -- notis tools search "list Notis databases"
 ```
 
-If you're using the desktop app, login and logout keep the CLI profile in sync automatically.
+Use `notis login --paste-code` for the HTTPS copy-paste fallback on a remote machine.
+
+## Release channels
+
+`@latest` is the only tag worth documenting, for beta accounts too.
+
+The npm tag has to be chosen before the CLI starts, and the CLI only learns which Notis it talks to once it reads the profile — so no single install command can be right for both environments on its own. Instead the deployment answers the question: `/.well-known/oauth-protected-resource/cli` reports its channel, `notis login` pins it on the profile, and any later run that finds itself on the wrong build hands the whole invocation to the right one before it does anything else.
+
+- `notis doctor` reports `release_channel`, `cli_version`, and a `channel` check.
+- `--api-base <url>` decides the build for that one run, so a one-off call against another environment uses the matching CLI.
+- `./dev.sh` profiles and source checkouts are never re-executed: whatever you started stays in control.
+- `NOTIS_CLI_AUTO_CHANNEL=0` disables the hand-off; `doctor` then reports the mismatch instead of correcting it.
+
+## Profiles
+
+A profile is one account paired with one API endpoint. Every profile keeps its own credential, so switching between them never signs any of them out.
+
+```bash
+npx --package @notis_ai/cli@latest -- notis login --profile work
+npx --package @notis_ai/cli@latest -- notis profile list
+npx --package @notis_ai/cli@latest -- notis profile use work
+npx --package @notis_ai/cli@latest -- notis --profile default tools search "..."
+```
+
+`notis logout` revokes and removes the OAuth grant for one profile; `--all-profiles` clears every one.
+
+Credential precedence within the selected profile is: an active `./dev.sh` worktree credential, then `NOTIS_JWT`, then the profile's OAuth grant.
+
+`./dev.sh` exposes its test account as a lease-backed `dev-<workspace>-<hash>` profile bound to its loopback backend. The credential stays in the worktree rather than the shared account config. That synthetic profile is the default only inside its active worktree; naming any stored profile with `--profile` runs against that real account instead.
 
 The CLI defaults to `json` output in agent or non-TTY contexts and `table` output in interactive terminals.
 
@@ -24,244 +59,443 @@ The CLI defaults to `json` output in agent or non-TTY contexts and `table` outpu
 - `--json` — Shortcut for `--output json`
 - `--output <table|json|yaml|ndjson>` — Output mode override
 - `--non-interactive` — Disable prompts
-- `--profile <name>` — Select a stored profile
+- `--profile <name>` — Run as a stored profile instead of the active one
 - `--api-base <url>` — Override the API base for one invocation
 - `--timeout-ms <n>` — HTTP timeout in milliseconds
 - `--idempotency-key <key>` — Override the generated idempotency key for mutating commands
 
-## Auth
+## Authentication
+
+### `npx --package @notis_ai/cli@latest -- notis login`
+
+Authorize a CLI profile in a browser with scoped OAuth access.
 
-### `notis auth login`
+When to use: Run this once per account you want the CLI to reach. Pass --profile to add a second account without signing the first one out.
 
-Store credentials for a named CLI profile.
+Options:
+- `--no-browser` — Print the authorization URL without opening a browser.
+- `--print-url` — Print the authorization URL even when opening a browser.
+- `--mode <mode>` — auto (default) hands the browser callback to a background listener when this command cannot wait; browser waits in-process; code shows a one-time code to copy.
+- `--paste-code` — Alias for --mode code.
+- `--timeout-seconds <n>` — Authorization lifetime in seconds (default 300 while waiting in a terminal; 1800 for detached or code hand-offs).
+- `--scope <scope>` — OAuth permission to request (repeatable).
+- `--code <code>` — Redeem the code shown in the browser after a non-interactive login.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis login`
+- `npx --package @notis_ai/cli@latest -- notis login --profile work`
+- `npx --package @notis_ai/cli@latest -- notis login --profile beta --api-base https://api-beta.notis.ai`
+- `npx --package @notis_ai/cli@latest -- notis login --no-browser --print-url`
+- `npx --package @notis_ai/cli@latest -- notis login --mode browser`
+- `npx --package @notis_ai/cli@latest -- notis login --mode code`
+- `npx --package @notis_ai/cli@latest -- notis login --code 4f3c2b1a`
+
+### `npx --package @notis_ai/cli@latest -- notis logout`
+
+Revoke and remove the OAuth credential for one CLI profile.
 
-When to use: Use this before authenticated commands, especially in fresh environments or CI profiles.
+When to use: Use this to disconnect a single account. Other profiles keep their credentials unless you pass --all-profiles.
 
 Options:
-- `--jwt <token>` — JWT token to store for the profile.
+- `--all-profiles` — Clear OAuth credentials and pending authorizations from every CLI profile.
 
 Examples:
-- `notis auth login --jwt <token>`
-- `notis auth login --profile staging --api-base http://localhost:3001`
+- `npx --package @notis_ai/cli@latest -- notis logout`
+- `npx --package @notis_ai/cli@latest -- notis logout --profile work`
+- `npx --package @notis_ai/cli@latest -- notis logout --all-profiles`
 
-### `notis auth logout`
 
-Remove the stored JWT for the active profile.
+## Coding-agent context
 
-When to use: Use this to clear local credentials without touching other profiles.
+### `npx --package @notis_ai/cli@latest -- notis agents install`
+
+Install Notis instructions and recall/capture hooks for local Codex and Claude Code.
+
+When to use: Run after login to give local coding agents durable Notis CLI guidance, session-start profile context, deduplicated relevant recall, and automatic completed-turn capture. Hosted Notis sandboxes already receive prompt context and are skipped.
+
+Options:
+- `--codex-only` — Configure only Codex.
+- `--claude-only` — Configure only Claude Code.
+- `--no-memory-hooks` — Install static instructions and remove Notis recall/capture hooks.
 
 Examples:
-- `notis auth logout`
-- `notis auth logout --profile staging`
+- `npx --package @notis_ai/cli@latest -- notis agents install`
+- `npx --package @notis_ai/cli@latest -- notis agents install --codex-only`
+- `npx --package @notis_ai/cli@latest -- notis agents install --claude-only`
+- `npx --package @notis_ai/cli@latest -- notis agents install --no-memory-hooks`
 
-### `notis auth status`
 
-Inspect local auth configuration and optionally verify it against the API.
+## Skills
 
-When to use: Use this before automating commands to confirm the active profile and token health.
+### `npx --package @notis_ai/cli@latest -- notis skills sync`
+
+Synchronize account skills and keep the three Notis base skills current.
+
+When to use: Run manually whenever local agent skills should be reconciled. Manual runs ignore the Desktop automatic-sync preference.
 
 Options:
-- `--verify` — Perform a live authenticated roundtrip to the API.
+- `--electron-repeat` — Honor the automatic Desktop sync preference (used by Notis Desktop).
 
 Examples:
-- `notis auth status`
-- `notis auth status --verify --json`
+- `npx --package @notis_ai/cli@latest -- notis skills sync`
+- `npx --package @notis_ai/cli@latest -- notis skills sync --json`
 
 
 ## Apps
 
-### `notis apps list`
+### `npx --package @notis_ai/cli@latest -- notis apps list`
 
 List apps the current profile can access.
 
 When to use: Discover existing apps before linking or deploying.
 
 Examples:
-- `notis apps list`
-- `notis apps list --json`
+- `npx --package @notis_ai/cli@latest -- notis apps list`
+- `npx --package @notis_ai/cli@latest -- notis apps list --json`
 
-### `notis apps init <name> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps init <name> [dir]`
 
 Scaffold a new Notis app project.
 
-When to use: Start a new Notis app. Creates a Vite + React project with @notis/sdk pre-configured.
+When to use: Start a new Notis app. Use --from with a published Store app when one is close to the desired app; otherwise creates the bare Vite + React project.
+
+Options:
+- `--from <slug>` — Start from a published Store app listed by `notis apps scaffolds list`. Downloads its source from the public app registry.
 
 Examples:
-- `notis apps init "Mind the Flo"`
-- `notis apps init "My App" ./my-app`
+- `npx --package @notis_ai/cli@latest -- notis apps scaffolds list`
+- `npx --package @notis_ai/cli@latest -- notis apps init "Mind the Flo"`
+- `npx --package @notis_ai/cli@latest -- notis apps init "My CRM" --from databases`
+- `npx --package @notis_ai/cli@latest -- notis apps init "My App" ~/code/my-app`
 
-### `notis apps create <name> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps scaffolds list`
+
+List published Store apps available as scaffolds.
+
+When to use: Discover published Store apps to start from before creating a new app. Every app published to the public Store is automatically a scaffold; use --search to narrow the catalog.
+
+Options:
+- `--search <term>` — Filter scaffolds by name, tagline, description, or category.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis apps scaffolds list`
+- `npx --package @notis_ai/cli@latest -- notis apps scaffolds list --search journal`
+- `npx --package @notis_ai/cli@latest -- notis apps init "My App" --from databases`
+
+### `npx --package @notis_ai/cli@latest -- notis apps create <name> [dir]`
 
 Create a new remote Notis app and optionally link a local project to it.
 
 When to use: Provision a fresh remote app before the first deploy. Pass a project directory to link it immediately.
 
 Options:
-- `--description <text>` — Optional app description.
-- `--icon <lucide:icon>` — Optional Lucide icon, for example lucide:dices.
+- `--team-id <id>` — Create or reuse the exact team-scoped app (default: personal).
 
 Examples:
-- `notis apps create "My App"`
-- `notis apps create "My App" . --description "Internal tool" --icon lucide:layout-dashboard`
+- `npx --package @notis_ai/cli@latest -- notis apps create "My App"`
+- `npx --package @notis_ai/cli@latest -- notis apps create "My App" .`
 
-### `notis apps dev [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps build [dir]`
 
-Run the Vite dev server for local development.
+Build and package the app into .notis/output/.
 
-When to use: Iterate on app UI with hot reload. SDK hooks return mock data.
+When to use: Prepare the app for verification or deployment.
 
 Examples:
-- `notis apps dev`
-- `notis apps dev ./my-app`
+- `npx --package @notis_ai/cli@latest -- notis apps build`
+- `npx --package @notis_ai/cli@latest -- notis apps build ./my-app`
 
-### `notis apps build [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps verify [dir]`
 
-Build and package the app into .notis/output/.
+Validate that every route renders and reports Store listing readiness.
 
-When to use: Prepare the app for preview or deployment.
+When to use: Any time after notis apps build, and before deploy. Catches render-time crashes and missing runtime calls. Incomplete listing media is reported as a warning; pass --listing to fail on it instead.
+
+Options:
+- `--routes <slugs>` — Comma-separated route slugs. Default: every route in manifest.
+- `--port <n>` — Loopback port. Default: auto-pick.
+- `--skip-build` — Skip notis apps build; reuse existing .notis/output/.
+- `--mode <mode>` — stub | live. Default stub. Live posts to /portal_views/runtime_query with the CLI JWT and fails routes whose runtime calls all errored.
+- `--listing` — Fail instead of warn when the Store listing (tagline, categories, screenshots, changelog) is incomplete.
+- `--no-browser` — Start the harness server and print URLs; do not drive agent-browser.
+- `--keep-open` — Leave server + browser session running after report (for manual triage).
 
 Examples:
-- `notis apps build`
-- `notis apps build ./my-app`
+- `npx --package @notis_ai/cli@latest -- notis apps verify`
+- `npx --package @notis_ai/cli@latest -- notis apps verify --routes notes`
+- `npx --package @notis_ai/cli@latest -- notis apps verify --mode live`
+- `npx --package @notis_ai/cli@latest -- notis apps verify --listing  # gate on Store listing readiness before publish`
+- `npx --package @notis_ai/cli@latest -- notis apps verify --no-browser  # start the harness, drive agent-browser yourself`
 
-### `notis apps preview [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps screenshot [dir]`
 
-Serve the built bundle locally for testing.
+Capture configured listing route/scenario states via the headless harness.
 
-When to use: Smoke-test the exact bundle that will be deployed. Databases use seed data.
+When to use: Generate the 3–6 declared metadata/screenshot-N.png files for the App Store listing. Apps are icon-led (like Raycast) — there is no cover image, only these screenshots. Each screenshot may set a focus selector to remove empty canvas and a light or dark theme that also controls its Store frame. Run before notis apps verify / deploy / publish.
 
 Options:
-- `--port <number>` — Server port (default: 8787).
+- `--routes <slugs>` — Comma-separated route slugs. Default: every configured screenshot state.
+- `--port <n>` — Loopback port. Default: auto-pick.
+- `--width <px>` — Viewport width. Default: 2000.
+- `--height <px>` — Viewport height. Default: 1250 (16:10).
+- `--output-dir <dir>` — Where to write screenshot-N.png. Default: metadata/.
+- `--mode <mode>` — stub | live. Default stub. Live renders against real data via the CLI JWT (requires a linked app), so screenshots show actual content instead of empty states.
+- `--raw` — Write the unframed harness capture instead of the default Store presentation.
+- `--skip-build` — Skip notis apps build; reuse existing .notis/output/.
 
 Examples:
-- `notis apps preview`
-- `notis apps preview --port 3000`
+- `npx --package @notis_ai/cli@latest -- notis apps screenshot  # honors notis.config.ts screenshot scenarios`
+- `npx --package @notis_ai/cli@latest -- notis apps screenshot --routes home,history`
+- `npx --package @notis_ai/cli@latest -- notis apps screenshot --mode live  # populated screenshots from real data`
+- `npx --package @notis_ai/cli@latest -- notis apps screenshot --raw  # diagnostic capture without Store framing`
 
-### `notis apps link <app-id> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps link <app-id> [dir]`
 
 Link a local project to a remote Notis app.
 
 When to use: Connect a local project to an existing app for deployment.
 
+Options:
+- `--expected-version <version>` — Link only if the remote deployment version still matches this non-negative integer.
+
 Examples:
-- `notis apps link abc123`
-- `notis apps link abc123 ./my-app`
+- `npx --package @notis_ai/cli@latest -- notis apps link abc123`
+- `npx --package @notis_ai/cli@latest -- notis apps link abc123 ./my-app`
+- `npx --package @notis_ai/cli@latest -- notis apps link abc123 ./recovered-app --expected-version 0`
 
-### `notis apps deploy [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps pull <app-id> [dir]`
 
-Build and upload the app to the linked Notis app.
+Download a Notis app source snapshot into a local project folder.
 
-When to use: Ship the installed app to production for the linked user/team app. Requires a linked app (notis apps link). This command does not publish to the app store.
+When to use: Edit an installed app. Preserve local edits, pull and link its persisted source, then build, verify and deploy.
+
+Options:
+- `--force` — Overwrite a non-empty target directory.
+- `--source-version <n>` — Pull a specific app source version (default: latest).
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis apps pull abc123`
+- `npx --package @notis_ai/cli@latest -- notis apps pull abc123 ./my-app --force --source-version 3`
+
+### `npx --package @notis_ai/cli@latest -- notis apps deploy [dir]`
+
+Build, verify and release the linked Workspace app.
+
+When to use: Build, verify and release the linked personal or team Workspace app. This command does not publish to the Store.
 
 Options:
 - `--app-id <id>` — Override linked app ID.
-- `--skip-build` — Skip the build step (use existing .notis/output/).
-- `--direct` — Upload directly to Supabase storage, bypassing the backend server. Auto-fallback on network errors.
+- `--skip-build` — Reuse unchanged build output; automated verification still runs.
 
 Examples:
-- `notis apps deploy`
-- `notis apps deploy --skip-build`
-- `notis apps deploy --app-id abc123`
-- `notis apps deploy --direct`
 
-### `notis apps doctor [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps publish [dir]`
+
+Submit the deployed app for Store review.
+
+When to use: After the user explicitly confirms the App Details page and Store listing are ready. Requires the current local project to match the latest deployed version.
+
+Options:
+- `--app-id <id>` — Override linked app ID.
+- `--confirm-ready` — Confirm the user approved the current App Details page for Store submission.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis apps publish --confirm-ready`
+- `npx --package @notis_ai/cli@latest -- notis apps publish ./my-app --confirm-ready`
+
+### `npx --package @notis_ai/cli@latest -- notis apps duplicate [dir]`
+
+Duplicate an app into an independent copy with its own databases.
+
+When to use: When the same app should run for a second purpose - a notes app for blog drafts alongside one for bookmarks. The copy shares no data with the source.
+
+Options:
+- `--app-id <id>` — App to duplicate. Defaults to the app this project is linked to.
+- `--name <name>` — Name for the duplicate (default: the source name followed by "copy").
+- `--copy-documents <mode>` — Which rows to copy: 'declared' (default, the starter content a fresh install would have), 'all', or 'none'.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis apps duplicate --name "Blog"`
+- `npx --package @notis_ai/cli@latest -- notis apps duplicate --app-id abc123 --name "Bookmarks" --copy-documents none`
+
+### `npx --package @notis_ai/cli@latest -- notis apps doctor [dir]`
 
 Check project health and readiness.
 
 When to use: Diagnose issues with a Notis app project.
 
 Examples:
-- `notis apps doctor`
-- `notis apps doctor ./my-app`
+- `npx --package @notis_ai/cli@latest -- notis apps doctor`
+- `npx --package @notis_ai/cli@latest -- notis apps doctor ./my-app`
+
+
+## Reports
+
+Reports save independent SDK documents into app-owned database records. They do not deploy an app or change shared app routes.
+
+Choose the owning database first and author exactly one SDK route. Keep readable content in a separate context file. Build, verify, inspect the preview, then save. Save rebuilds and stub-verifies a frozen artifact before persistence; local verification does not prove that live data loaded in the saved report.
+
+To revise, read the current document and recover its source from the short-lived `report_source_url`. Pass `--document-id` and the freshly read `--expected-revision`; add `--attach` only to replace the body of an existing non-view record. Read back the saved record and inspect its native URL. See the product `notis-reports` skill for the full authoring contract.
+
+### `npx --package @notis_ai/cli@latest -- notis reports init <name> [dir]`
+
+Init a record-owned SDK report locally.
+
+When to use: Author an independent report without deploying its owning app.
+
+Options:
+- `--from <slug>` — Start from a published Store app listed by `notis apps scaffolds list`. Downloads its source from the public app registry.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis apps scaffolds list`
+- `npx --package @notis_ai/cli@latest -- notis reports init "Mind the Flo"`
+- `npx --package @notis_ai/cli@latest -- notis reports init "My CRM" --from databases`
+- `npx --package @notis_ai/cli@latest -- notis reports init "My App" ~/code/my-app`
+
+### `npx --package @notis_ai/cli@latest -- notis reports build [dir]`
+
+Build a record-owned SDK report locally.
+
+When to use: Author an independent report without deploying its owning app.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis reports build`
+- `npx --package @notis_ai/cli@latest -- notis reports build ./my-app`
+
+### `npx --package @notis_ai/cli@latest -- notis reports verify [dir]`
+
+Verify a record-owned SDK report locally.
+
+When to use: Author an independent report without deploying its owning app.
+
+Options:
+- `--routes <slugs>` — Comma-separated route slugs. Default: every route in manifest.
+- `--port <n>` — Loopback port. Default: auto-pick.
+- `--skip-build` — Skip notis apps build; reuse existing .notis/output/.
+- `--mode <mode>` — stub | live. Default stub. Live posts to /portal_views/runtime_query with the CLI JWT and fails routes whose runtime calls all errored.
+- `--listing` — Ignored for reports; saving a report does not publish a Store listing.
+- `--no-browser` — Start the harness server and print URLs; do not drive agent-browser.
+- `--keep-open` — Leave server + browser session running after report (for manual triage).
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis reports verify`
+- `npx --package @notis_ai/cli@latest -- notis reports verify --routes notes`
+- `npx --package @notis_ai/cli@latest -- notis reports verify --mode live`
+- `npx --package @notis_ai/cli@latest -- notis reports verify --no-browser  # start the harness, drive agent-browser yourself`
 
+### `npx --package @notis_ai/cli@latest -- notis reports preview [dir]`
 
-## Databases
+Preview a record-owned SDK report locally. Keeps the preview server and browser session open.
 
-### `notis db list`
+When to use: Author an independent report without deploying its owning app.
+
+Options:
+- `--routes <slugs>` — Comma-separated route slugs. Default: every route in manifest.
+- `--port <n>` — Loopback port. Default: auto-pick.
+- `--skip-build` — Skip notis apps build; reuse existing .notis/output/.
+- `--mode <mode>` — stub | live. Default stub. Live posts to /portal_views/runtime_query with the CLI JWT and fails routes whose runtime calls all errored.
+- `--listing` — Ignored for reports; saving a report does not publish a Store listing.
+- `--no-browser` — Start the harness server and print URLs; do not drive agent-browser.
+- `--keep-open` — Leave server + browser session running after report (for manual triage).
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis reports preview`
+- `npx --package @notis_ai/cli@latest -- notis reports preview --routes notes`
+- `npx --package @notis_ai/cli@latest -- notis reports preview --mode live`
+- `npx --package @notis_ai/cli@latest -- notis reports preview --no-browser  # start the harness, drive agent-browser yourself`
 
-List native Notis databases.
+### `npx --package @notis_ai/cli@latest -- notis reports save [dir]`
 
-When to use: Use this to find database ids and slugs before querying or updating schemas.
+Build, verify and save a report into an app-owned database record.
+
+When to use: Persist an independently authored report, not an app release.
+
+Options:
+- `--database-id <id>` — Required. Owning app database.
+- `--document-id <id>` — Existing record to update or attach to.
+- `--attach` — Attach to an existing non-view record.
+- `--expected-revision <revision>` — Fresh view revision (0 for a record without a view).
+- `--title <title>` — Required, including updates. Record title.
+- `--context-file <file>` — Required. UTF-8 readable report content and structure.
+- `--properties-file <file>` — JSON database property values keyed by name.
 
 Examples:
-- `notis db list`
-- `notis db list --json`
+- `npx --package @notis_ai/cli@latest -- notis reports save ./weekly-report --database-id <id> --title "Weekly review" --context-file ./context.md`
+
 
-### `notis db upsert`
+## Hand-over
 
-Create or update a native database schema.
+Give the branch you are on to a Notis agent, which continues the work in a git worktree on the Notis cloud computer. `--route` picks the agent: the hosted Notis agent, or the user's own Codex/Claude Code in the cloud sandbox or on their Mac. `--branch-mode same` makes the agent commit onto your branch; the default cuts a new branch from it.
 
-When to use: Use this when you need to provision a new database or adjust an existing schema.
+### `npx --package @notis_ai/cli@latest -- notis handover start <task>`
+
+Hand the current branch to a Notis agent and keep working.
+
+When to use: Use this when you want Notis to continue work on the branch you are on -- long refactors, test fixing, or anything that should keep running after you close the laptop. Pick the agent with --route.
 
 Options:
-- `--operation <create|update>` — Create a new database or update an existing one.
-- `--database-id <id>` — Database id for update operations.
-- `--title <text>` — Database title.
-- `--description <text>` — Database description.
-- `--icon <lucide-icon-name>` — Database icon (Lucide icon name, e.g. database).
-- `--properties <json>` — JSON array of property definitions.
+- `--branch-mode <mode>` — same = the agent commits onto your branch. new = the agent cuts a new branch from it (default).
+- `--route <target>` — Which agent runs it: notis (hosted, default), codex_cloud, claude_cloud, codex_local, claude_local, or auto.
+- `--repo <slug>` — Configured repository slug on the cloud computer, when you know it.
+- `--no-wip` — Refuse on a dirty tree instead of committing the changes first.
 
 Examples:
-- `notis db upsert --operation create --title "Tasks"`
-- `notis db upsert --operation update --database-id db_123 --title "Tasks V2"`
+- `npx --package @notis_ai/cli@latest -- notis handover start "fix the failing auth tests"`
+- `npx --package @notis_ai/cli@latest -- notis handover start "finish the migration" --branch-mode same --route codex_cloud`
+- `npx --package @notis_ai/cli@latest -- notis handover start "add integration tests" --route claude_cloud`
+- `npx --package @notis_ai/cli@latest -- notis handover start "review and clean up this branch" --route claude_local`
 
-### `notis db query <database-slug>`
+### `npx --package @notis_ai/cli@latest -- notis handover status`
 
-Run a structured query against a native Notis database.
+Show the coding-agent threads Notis is running for you.
 
-When to use: Use this when the database slug is known and you need direct filters, sorts, or pagination.
+When to use: Use this after a hand-over to see whether the agent is still working.
 
 Options:
-- `--filter <json>` — Structured query filter JSON.
-- `--sort <json>` — Sort JSON object or array.
-- `--page-size <n>` — Page size between 1 and 100.
-- `--offset <n>` — Zero-based offset.
-- `--cursor <value>` — Pagination cursor alias for next_offset.
+- `--provider <provider>` — Filter to codex or claude_code.
+- `--refresh` — Force a live refresh instead of cached state.
 
 Examples:
-- `notis db query tasks --page-size 50`
-- `notis db query tasks --filter '{"property":"Status"}'`
+- `npx --package @notis_ai/cli@latest -- notis handover status`
+- `npx --package @notis_ai/cli@latest -- notis handover status --provider codex --refresh`
 
 
 ## Generic Tools
 
-### `notis tools toolkits`
+### `npx --package @notis_ai/cli@latest -- notis tools toolkits`
 
-List toolkit namespaces available to the active user.
+List toolkit namespaces and connection statuses available to the active user.
 
-When to use: Use this before searching or executing generic tools.
+When to use: Use this to inspect connection state before searching or executing generic tools.
 
 Examples:
-- `notis tools toolkits`
-- `notis tools toolkits --json`
+- `npx --package @notis_ai/cli@latest -- notis tools toolkits`
+- `npx --package @notis_ai/cli@latest -- notis tools toolkits --json`
 
-### `notis tools search <query>`
+### `npx --package @notis_ai/cli@latest -- notis tools search <query>`
 
 Search across toolkit namespaces using natural language.
 
 When to use: Use this when you need a generic capability that does not have a first-class CLI command.
 
 Options:
-- `--toolkits <csv-or-json>` — Optional subset of toolkit ids to search.
+- `--known-fields <text>` — Optional known field hints, such as channel_name:general or user_email:a@example.com.
 
 Examples:
-- `notis tools search "send an email"`
-- `notis tools search "update framer page" --toolkits mcp-framer`
+- `npx --package @notis_ai/cli@latest -- notis tools search "send an email"`
+- `npx --package @notis_ai/cli@latest -- notis tools search "post on LinkedIn" --known-fields "platform:linkedin"`
 
-### `notis tools describe <tool-name>`
+### `npx --package @notis_ai/cli@latest -- notis tools describe <tool-name>`
 
 Describe a generic tool by name.
 
 When to use: Use this when you know the tool name and want its parameter schema before execution.
 
-Options:
-- `--toolkits <csv-or-json>` — Optional subset of toolkit ids to search.
-
 Examples:
-- `notis tools describe composio-gmail-default-send_email`
-- `notis tools describe notis-default-query --toolkits notis-default`
+- `npx --package @notis_ai/cli@latest -- notis tools describe composio-gmail-send_email`
+- `npx --package @notis_ai/cli@latest -- notis tools describe LOCAL_NOTIS_DATABASE_QUERY`
 
-### `notis tools exec <tool-name>`
+### `npx --package @notis_ai/cli@latest -- notis tools exec <tool-name>`
 
 Execute a generic tool by canonical tool name.
 
@@ -269,65 +503,133 @@ When to use: Use this as the escape hatch for integrations or Notis tools withou
 
 Options:
 - `--arguments <json>` — JSON object, @file path, or - for stdin.
+- `--arguments-file <path>` — Read the JSON arguments object from a file.
+- `--file <argument-path=local-path>` — Upload a local file into a file-uploadable tool argument. Repeatable.
 - `--get-schema` — Display the tool parameter schema without executing.
 - `--dry-run` — Validate arguments against the tool schema without executing.
-- `--watch <seconds>` — Re-execute on an interval and stream results.
 
 Examples:
-- `notis tools exec notis-default-query --arguments '{"database_slug":"tasks","query":{}}'`
-- `notis tools exec notis-default-query --get-schema`
-- `notis tools exec notis-default-query --dry-run --arguments '{"database_slug":"tasks","query":{}}'`
-- `notis tools exec notis-default-query --arguments @query.json`
-- `notis tools exec notis-default-query --arguments - < query.json`
-- `notis tools exec notis-default-query --watch 10 --arguments '{"database_slug":"tasks","query":{}}'`
+- `npx --package @notis_ai/cli@latest -- notis tools exec LOCAL_NOTIS_DATABASE_QUERY --arguments '{"database_slug":"tasks","query":{}}'`
+- `npx --package @notis_ai/cli@latest -- notis tools exec LOCAL_NOTIS_DATABASE_GET_DATABASE --arguments '{"database_slug":"tasks"}'`
+- `npx --package @notis_ai/cli@latest -- notis tools exec LOCAL_NOTIS_DATABASE_QUERY --get-schema`
+- `npx --package @notis_ai/cli@latest -- notis tools exec LOCAL_NOTIS_DATABASE_QUERY --dry-run --arguments '{"database_slug":"tasks","query":{}}'`
+- `npx --package @notis_ai/cli@latest -- notis tools exec LOCAL_NOTIS_DATABASE_QUERY --arguments @query.json`
+- `npx --package @notis_ai/cli@latest -- notis tools exec LOCAL_NOTIS_DATABASE_QUERY --arguments-file query.json`
+- `npx --package @notis_ai/cli@latest -- notis tools exec LOCAL_NOTIS_DATABASE_QUERY --arguments - < query.json`
+- `npx --package @notis_ai/cli@latest -- notis tools exec composio-dropbox-upload_file --arguments '{"path":"/target/in/dropbox.pdf"}' --file content=./Invoice.pdf`
 
-### `notis tools exec-parallel <calls>`
+### `npx --package @notis_ai/cli@latest -- notis tools exec-parallel <calls>`
 
 Execute multiple tools concurrently.
 
 When to use: Use this when you need to run independent tool calls simultaneously for speed.
 
+Options:
+- `--file <argument-path=local-path>` — Unsupported for exec-parallel; use tools exec for file uploads.
+
 Examples:
-- `notis tools exec-parallel '[{"tool_name":"notis-default-query","arguments":{"database_slug":"tasks","query":{}}},{"tool_name":"notis-default-list_databases","arguments":{}}]'`
+- `npx --package @notis_ai/cli@latest -- notis tools exec-parallel '[{"tool_name":"LOCAL_NOTIS_DATABASE_QUERY","arguments":{"database_slug":"tasks","query":{}}},{"tool_name":"LOCAL_NOTIS_DATABASE_LIST_DATABASES","arguments":{}}]'`
 
-### `notis tools link <toolkit>`
+### `npx --package @notis_ai/cli@latest -- notis tools link <toolkit>`
 
-Get the URL to connect an integration toolkit.
+Connect or reconnect an integration toolkit.
 
-When to use: Use this when a tool requires authentication with an external service.
+When to use: Use this when a tool requires authentication or an active connection must be replaced.
+
+Options:
+- `--reconnect` — Replace the existing account instead of adding another connection.
+- `--connection-id <id>` — Exact connection id to replace when multiple accounts exist.
+- `--label <label>` — Account label for a new or replacement connection.
+- `--credentials <json>` — Credential JSON object, @file path, or - for stdin. Prefer stdin so secrets do not enter shell history.
 
 Examples:
-- `notis tools link github`
-- `notis tools link gmail --json`
+- `npx --package @notis_ai/cli@latest -- notis tools link github`
+- `npx --package @notis_ai/cli@latest -- notis tools link dataforseo --reconnect --credentials - < credentials.json`
+
+
+## Profile Commands
+
+### `npx --package @notis_ai/cli@latest -- notis profile list`
+
+List every CLI profile with its account, API endpoint, and credential state.
+
+When to use: Use this to see which accounts and environments this machine can reach before choosing one.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis profile list`
+- `npx --package @notis_ai/cli@latest -- notis profile list --json`
+
+### `npx --package @notis_ai/cli@latest -- notis profile use <name>`
+
+Switch the default profile without signing any profile out.
+
+When to use: Use this to change which account and API subsequent commands target. Every other profile keeps its credential.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis profile use work`
+- `npx --package @notis_ai/cli@latest -- notis profile use default`
+
+### `npx --package @notis_ai/cli@latest -- notis profile show [name]`
+
+Show one profile in detail, including scopes and credential expiry.
+
+When to use: Use this to inspect exactly which account and endpoint a profile resolves to.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis profile show`
+- `npx --package @notis_ai/cli@latest -- notis profile show work --json`
+
+### `npx --package @notis_ai/cli@latest -- notis profile remove <name>`
+
+Delete a CLI profile from this machine.
+
+When to use: Use this after logging a profile out. Removing a still-authorized profile requires --force and leaves the grant live server-side.
+
+Options:
+- `--force` — Discard a profile that still holds a credential.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis profile remove old-work`
+- `npx --package @notis_ai/cli@latest -- notis profile remove old-work --force`
 
 
 ## Meta Commands
 
-### `notis doctor`
+### `npx --package @notis_ai/cli@latest -- notis doctor`
 
 Run a quick CLI health check for config, auth, and API reachability.
 
 When to use: Use this before relying on the CLI in automation or after changing environments.
 
 Examples:
-- `notis doctor`
-- `notis doctor --json`
+- `npx --package @notis_ai/cli@latest -- notis doctor`
+- `npx --package @notis_ai/cli@latest -- notis doctor --json`
+
+### `npx --package @notis_ai/cli@latest -- notis whoami`
+
+Display the active profile, user, and available toolkit connection statuses.
+
+When to use: Use this to quickly confirm which account and environment a command will target.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis whoami`
+- `npx --package @notis_ai/cli@latest -- notis whoami --json`
 
-### `notis describe <command...>`
+### `npx --package @notis_ai/cli@latest -- notis describe <command...>`
 
 Describe a first-class CLI command in detail.
 
 When to use: Use this when an agent or human needs the exact shape, examples, and semantics of a command.
 
 Examples:
-- `notis describe apps push`
-- `notis describe db query`
+- `npx --package @notis_ai/cli@latest -- notis describe apps deploy`
+- `npx --package @notis_ai/cli@latest -- notis describe tools exec`
 
 
 ## Local Development
 
 ```bash
-cd cli/npm
+cd packages/cli
 npm install
 node ./bin/notis.js --help
 npm run docs:generate