@notis_ai/cli 0.2.1 → 0.2.3

package/README.md

@@ -1,21 +1,23 @@
 # @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.
+Use the Notis CLI through NPX. Install and sign into Notis Desktop to keep the local CLI auth profile current; do not rely on an installed `notis` command. Related skills such as `notis-cli` and `notis-apps` are delivered through normal Notis skill sync for the signed-in user.
+
+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 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.
+The desktop app owns sign-in and keeps the CLI profile in sync automatically.
 
 The CLI defaults to `json` output in agent or non-TTY contexts and `table` output in interactive terminals.
 
@@ -29,107 +31,79 @@ The CLI defaults to `json` output in agent or non-TTY contexts and `table` outpu
 - `--timeout-ms <n>` — HTTP timeout in milliseconds
 - `--idempotency-key <key>` — Override the generated idempotency key for mutating commands
 
-## Auth
-
-### `notis auth login`
-
-Store credentials for a named CLI profile.
-
-When to use: Use this before authenticated commands, especially in fresh environments or CI profiles.
-
-Options:
-- `--jwt <token>` — JWT token to store for the profile.
-
-Examples:
-- `notis auth login --jwt <token>`
-- `notis auth login --profile staging --api-base http://localhost:3001`
+## Apps
 
-### `notis auth logout`
+### `npx --package @notis_ai/cli@latest -- notis apps list`
 
-Remove the stored JWT for the active profile.
+List apps the current profile can access.
 
-When to use: Use this to clear local credentials without touching other profiles.
+When to use: Discover existing apps before linking or deploying.
 
 Examples:
-- `notis auth logout`
-- `notis auth logout --profile staging`
+- `npx --package @notis_ai/cli@latest -- notis apps list`
+- `npx --package @notis_ai/cli@latest -- notis apps list --json`
 
-### `notis auth status`
+### `npx --package @notis_ai/cli@latest -- notis apps init <name> [dir]`
 
-Inspect local auth configuration and optionally verify it against the API.
+Scaffold a new Notis app project.
 
-When to use: Use this before automating commands to confirm the active profile and token health.
+When to use: Start a new Notis app. Use --from with a bundled scaffold when one is close to the desired app; otherwise creates the bare Vite + React project.
 
 Options:
-- `--verify` — Perform a live authenticated roundtrip to the API.
-
-Examples:
-- `notis auth status`
-- `notis auth status --verify --json`
-
-
-## Apps
-
-### `notis apps list`
-
-List apps the current profile can access.
-
-When to use: Discover existing apps before linking or deploying.
+- `--from <slug>` — Start from a bundled scaffold listed by `notis apps scaffolds list`.
 
 Examples:
-- `notis apps list`
-- `notis apps list --json`
+- `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 notis-database`
+- `npx --package @notis_ai/cli@latest -- notis apps init "My App" ./my-app`
 
-### `notis apps init <name> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps scaffolds list`
 
-Scaffold a new Notis app project.
+List bundled Notis app scaffolds.
 
-When to use: Start a new Notis app. Creates a Vite + React project with @notis/sdk pre-configured.
+When to use: Discover the fixed scaffold catalog shipped with the CLI before starting a new app.
 
 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 "My App" --from notis-database`
 
-### `notis apps create <name> [dir]`
+### `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.
-
 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 dev [dir]`
 
 Develop Notis apps inside the Electron desktop Portal with automatic local bundle reloads.
 
-When to use: Run this inside a single app or a monorepo root with apps/<name>/notis.config.ts. It discovers every app, starts the local bundle server, registers desktop-local dev sessions, and opens the Electron Portal Development tab.
+When to use: Run this inside a single app or a monorepo root with apps/<name>/notis.config.ts. It discovers every app, starts the local bundle server, registers desktop-local dev sessions, and opens the Electron Portal to the local development app.
 
 Options:
 - `--port <number>` — Local bundle server port (default: 5173).
-- `--no-open` — Do not auto-open the desktop Portal Development tab.
+- `--no-open` — Do not auto-open the desktop Portal local development app.
 
 Examples:
-- `notis apps dev`
-- `notis apps dev ./my-app`
-- `notis apps dev ./workspace --port 5200`
+- `npx --package @notis_ai/cli@latest -- notis apps dev`
+- `npx --package @notis_ai/cli@latest -- notis apps dev ./my-app`
+- `npx --package @notis_ai/cli@latest -- notis apps dev ./workspace --port 5200`
 
-### `notis apps build [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps build [dir]`
 
 Build and package the app into .notis/output/.
 
 When to use: Prepare the app for verification or deployment.
 
 Examples:
-- `notis apps build`
-- `notis apps build ./my-app`
+- `npx --package @notis_ai/cli@latest -- notis apps build`
+- `npx --package @notis_ai/cli@latest -- notis apps build ./my-app`
 
-### `notis apps verify [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps verify [dir]`
 
 Headless render smoke each route in a stub-runtime harness.
 
@@ -144,36 +118,36 @@ Options:
 - `--keep-open` — Leave server + browser session running after report (for manual triage).
 
 Examples:
-- `notis apps verify`
-- `notis apps verify --routes notes`
-- `notis apps verify --mode live`
-- `notis apps verify --no-browser  # start the harness, drive agent-browser yourself`
+- `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 --no-browser  # start the harness, drive agent-browser yourself`
 
-### `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.
 
 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`
 
-### `notis apps pull <app-id> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps pull <app-id> [dir]`
 
 Download a Notis app source snapshot into a local project folder.
 
-When to use: Edit an installed app locally. Pulls the persisted source and links the directory to the app.
+When to use: Edit an installed app locally. Pulls the persisted source, links the directory to the app/version, then continue with npm install, notis apps dev, notis apps build, and notis apps deploy.
 
 Options:
 - `--force` — Overwrite a non-empty target directory.
 - `--version <n>` — Pull a specific app source version (default: latest).
 
 Examples:
-- `notis apps pull abc123`
-- `notis apps pull abc123 ./my-app --force`
+- `npx --package @notis_ai/cli@latest -- notis apps pull abc123`
+- `npx --package @notis_ai/cli@latest -- notis apps pull abc123 ./my-app --force`
 
-### `notis apps deploy [dir]`
+### `npx --package @notis_ai/cli@latest -- notis apps deploy [dir]`
 
 Build and upload the app to the linked Notis app.
 
@@ -185,109 +159,58 @@ Options:
 - `--direct` — Upload directly to Supabase storage, bypassing the backend server. Auto-fallback on network errors.
 
 Examples:
-- `notis apps deploy`
-- `notis apps deploy --skip-build`
-- `notis apps deploy --app-id abc123`
-- `notis apps deploy --direct`
+- `npx --package @notis_ai/cli@latest -- notis apps deploy`
+- `npx --package @notis_ai/cli@latest -- notis apps deploy --skip-build`
+- `npx --package @notis_ai/cli@latest -- notis apps deploy --app-id abc123`
+- `npx --package @notis_ai/cli@latest -- notis apps deploy --direct`
 
-### `notis apps doctor [dir]`
+### `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`
-
-
-## Databases
-
-### `notis db list`
-
-List native Notis databases.
-
-When to use: Use this to find database ids and slugs before querying or updating schemas.
-
-Examples:
-- `notis db list`
-- `notis db list --json`
-
-### `notis db upsert`
-
-Create or update a native database schema.
-
-When to use: Use this when you need to provision a new database or adjust an existing schema.
-
-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.
-
-Examples:
-- `notis db upsert --operation create --title "Tasks"`
-- `notis db upsert --operation update --database-id db_123 --title "Tasks V2"`
-
-### `notis db query <database-slug>`
-
-Run a structured query against a native Notis database.
-
-When to use: Use this when the database slug is known and you need direct filters, sorts, or pagination.
-
-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.
-
-Examples:
-- `notis db query tasks --page-size 50`
-- `notis db query tasks --filter '{"property":"Status"}'`
+- `npx --package @notis_ai/cli@latest -- notis apps doctor`
+- `npx --package @notis_ai/cli@latest -- notis apps doctor ./my-app`
 
 
 ## 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.
 
@@ -295,66 +218,79 @@ 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.
+- `--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.
-- `--toolkits <csv-or-json>` — Optional toolkit namespace(s) to use when resolving the tool.
 
 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 - < 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.
 
 When to use: Use this when a tool requires authentication with an external service.
 
 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 gmail --json`
 
 
 ## 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

package/config/notis_app_boundary_rules.json

@@ -0,0 +1,50 @@
+{
+  "javascript": [
+    {
+      "pattern": "window\\.__NOTIS_RUNTIME__",
+      "message": "window.__NOTIS_RUNTIME__ is forbidden; rely on the portal-injected NotisProvider runtime."
+    },
+    {
+      "pattern": "document\\.(?:body|head|documentElement)\\b",
+      "message": "document.body, document.head, and document.documentElement are forbidden; apps must stay inside the app surface."
+    },
+    {
+      "pattern": "document\\.(?:querySelector|querySelectorAll|getElementById|getElementsByClassName|getElementsByTagName)\\s*\\(\\s*(['\"`])[^\\n]*\\[data-notis-",
+      "message": "querying portal-owned [data-notis-*] hooks is forbidden."
+    },
+    {
+      "pattern": "createPortal\\s*\\(",
+      "message": "React portals are unsupported in Notis apps until a shadow-safe overlay contract exists."
+    },
+    {
+      "pattern": "@radix-ui/react-portal",
+      "message": "@radix-ui/react-portal is unsupported in Notis apps until a shadow-safe overlay contract exists."
+    },
+    {
+      "pattern": "PortalPrimitive",
+      "message": "Radix portal primitives are unsupported in Notis apps until a shadow-safe overlay contract exists."
+    }
+  ],
+  "css": [
+    {
+      "pattern": ":root\\b",
+      "message": ":root selectors are forbidden; styles must stay inside the app surface."
+    },
+    {
+      "pattern": "(^|[\\s,>+~])html(?=[\\s.#[:{>+~,]|$)",
+      "message": "html selectors are forbidden; styles must stay inside the app surface."
+    },
+    {
+      "pattern": "(^|[\\s,>+~])body(?=[\\s.#[:{>+~,]|$)",
+      "message": "body selectors are forbidden; styles must stay inside the app surface."
+    },
+    {
+      "pattern": "\\[data-notis-(?!app-root\\b)[^\\]]*\\]",
+      "message": "portal-owned [data-notis-*] selectors are forbidden. Use [data-notis-app-root] only for the app surface itself."
+    },
+    {
+      "pattern": "\\[data-sidebar(?:=[^\\]]+)?\\]",
+      "message": "portal sidebar selectors are forbidden."
+    }
+  ]
+}

package/dist/scaffolds/notis-database/app/globals.css

@@ -0,0 +1,44 @@
+@tailwind base;
+@tailwind components;
+@tailwind utilities;
+
+/*
+ * The portal mounts the app inside [data-notis-app-root] (display: block,
+ * min-height: 100% from @notis/sdk/styles.css). Width 100% ensures the
+ * two-pane layout can stretch to the full content area; height stays on
+ * the SDK's min-height: 100% default so the page can grow with content.
+ * The page itself uses `h-screen` to guarantee a fixed viewport height
+ * for the two-pane divider and centered empty states.
+ */
+[data-notis-app-root] {
+  width: 100%;
+}
+
+/*
+ * Dev-preview fallback tokens. Active only when the dev entrypoint sets the
+ * data-dev-preview attribute. Production bundle runs inside the portal
+ * shadow root where the host injects real theme tokens, so this rule is
+ * scoped narrowly enough to never collide with portal-provided values.
+ */
+[data-dev-preview] {
+  --background: 0 0% 100%;
+  --foreground: 0 0% 4%;
+  --card: 0 0% 100%;
+  --card-foreground: 0 0% 4%;
+  --popover: 0 0% 100%;
+  --popover-foreground: 0 0% 4%;
+  --primary: 0 0% 9%;
+  --primary-foreground: 0 0% 98%;
+  --secondary: 240 5% 96%;
+  --secondary-foreground: 0 0% 9%;
+  --muted: 240 5% 96%;
+  --muted-foreground: 240 4% 46%;
+  --accent: 240 5% 96%;
+  --accent-foreground: 0 0% 9%;
+  --destructive: 0 84% 60%;
+  --destructive-foreground: 0 0% 98%;
+  --border: 240 6% 90%;
+  --input: 240 6% 90%;
+  --ring: 0 0% 4%;
+  --radius: 0.5rem;
+}

package/dist/scaffolds/notis-database/app/layout.tsx

@@ -0,0 +1,6 @@
+import '@notis/sdk/styles.css';
+import './globals.css';
+
+export default function AppShell({ children }: { children: React.ReactNode }) {
+  return children;
+}