@keystrokehq/cli 0.1.49 → 0.1.51

package/dist/skills-bundle/_AGENTS.mcp.md

@@ -17,7 +17,7 @@ The **keystroke platform** is the hosted control plane and the shared web worksp
 | Workflows      | `src/workflows/`            | `@keystrokehq/keystroke/workflow`                                           |
 | Triggers       | `src/triggers/`             | `@keystrokehq/keystroke/trigger`                                            |
 | Apps           | `src/apps/`                 | `@keystrokehq/keystroke/app`                                                |
-| Integrations   | npm packages + catalog      | `@keystrokehq/exa`, `@keystrokehq/slack`, … — discover with `exec_command` + `keystroke app search` |
+| Integrations   | npm packages + catalog      | `@keystrokehq/exa`, `@keystrokehq/slack`, … — discover with `exec_command` + `keystroke apps search` |
 | Skills / files | `src/skills/`, `src/files/` | attached on `defineAgent`                                                   |
 
 Default-export each module — the server discovers files under `src/`.
@@ -66,7 +66,7 @@ Workflows also render as an interactive **canvas** in the platform. Keep durable
 - **Research real APIs before mirroring them** — building actions for custom integrations is very common; web search and fetch the actual reference & explore relevant docs, don't guess endpoints or payload shapes.
 - **Run before you claim you are finished** — deploy with `deploy_project`, run it in the cloud via `exec_command`, and read the real output before activating live triggers or claiming you are finished. Chat with agents and run workflows to confirm they behave correctly.
 - **Cover obvious edge cases** and write simple tests as needed (null field, empty array, a step that throws).
-- **Verify integration prerequisites** — before composing a catalog action into a workflow, run it once with `keystroke app execute` (via `exec_command`) to confirm the IDs and fields exist in the connected account.
+- **Verify integration prerequisites** — before composing a catalog action into a workflow, run it once with `keystroke apps execute` (via `exec_command`) to confirm the IDs and fields exist in the connected account.
 - **Connected apps aren't in `.env`** — deploy never uploads `.env`; use the `connect_app` tool to get a link for the user to connect integrations in the web app (a browser cannot open in this workspace).
 - **Filtered deploys** — determine if you should do a full vs filtered deploy, or use WIP ignore directives (`search_docs "filtered deploy"`).
 - **Dependencies** — use the project's existing package manager (`package.json` `packageManager` field or lockfile); default to npm only on a freshly created project with no lockfile. Deploy uploads only the built `dist/` artifact — a lockfile is not part of what ships to the platform.
@@ -78,22 +78,22 @@ Use `exec_command` with the keystroke CLI — credentials are injected automatic
 
 ```bash
 # Workflows
-keystroke workflow list                                                        # list deployed workflows
-keystroke workflow run <workflow-key> --input '{}'                             # invoke a workflow
-keystroke workflow runs list <workflow-key>                                    # recent runs for a workflow
-keystroke workflow runs get <workflow-key> <run-id> --include steps,trace      # one run in full: input, each step, execution trace
+keystroke workflows list                                                        # list deployed workflows
+keystroke workflows run <workflow-key> --input '{}'                             # invoke a workflow
+keystroke workflows runs list <workflow-key>                                    # recent runs for a workflow
+keystroke workflows runs get <workflow-key> <run-id> --include steps,trace      # one run in full: input, each step, execution trace
 
 # Agents
-keystroke agent list                                                           # list deployed agents
-keystroke agent prompt <agent-key> --message "Hi"                              # send a message (add --session-id to continue a session)
-keystroke agent sessions list <agent-key>                                      # recent sessions for an agent
-keystroke agent sessions get <agent-key> <session-id> --include messages,trace # one session in full: messages, execution trace
+keystroke agents list                                                           # list deployed agents
+keystroke agents prompt <agent-key> --message "Hi"                              # send a message (add --session-id to continue a session)
+keystroke agents sessions list <agent-key>                                      # recent sessions for an agent
+keystroke agents sessions get <agent-key> <session-id> --include messages,trace # one session in full: messages, execution trace
 
 # Triggers (attachment id is <trigger-key>:<workflow-key>)
-keystroke trigger list                                                         # list deployed triggers
-keystroke trigger url <trigger-key>                                            # print a trigger's webhook URL
-keystroke trigger runs list <trigger-key>:<workflow-key>                       # recent runs for a trigger→workflow attachment
-keystroke trigger runs get <trigger-key>:<workflow-key> <run-id> --include workflows,trace  # one run in full: workflows fired, execution trace
+keystroke triggers list                                                         # list deployed triggers
+keystroke triggers url <trigger-key>                                            # print a trigger's webhook URL
+keystroke triggers runs list <trigger-key>:<workflow-key>                       # recent runs for a trigger→workflow attachment
+keystroke triggers runs get <trigger-key>:<workflow-key> <run-id> --include workflows,trace  # one run in full: workflows fired, execution trace
 ```
 
 Read `src/` first — existing agents, workflows, actions, and triggers are your best map of how this project works.
@@ -103,11 +103,11 @@ Read `src/` first — existing agents, workflows, actions, and triggers are your
 To discover apps/integrations and their actions, query the live catalog with the CLI via `exec_command` (the docs integration index is unreliable):
 
 ```bash
-keystroke app list                                  # apps registered/connectable in your org
-keystroke app search <query>                        # find an app and its slug in the full catalog
-keystroke app actions <app> --search <q>            # actions an app exposes
-keystroke app action <app> <tool>                   # schema + how to run/import one action
-keystroke app execute <app> <tool> --input '{...}'  # run a connected catalog action (no server)
+keystroke apps list                                  # apps registered/connectable in your org
+keystroke apps search <query>                        # find an app and its slug in the full catalog
+keystroke apps actions <app> --search <q>            # actions an app exposes
+keystroke apps action <app> <tool>                   # schema + how to run/import one action
+keystroke apps execute <app> <tool> --input '{...}'  # run a connected catalog action (no server)
 keystroke credentials list                          # what's already connected — check before asking the user to connect
 ```
 

package/dist/skills-bundle/_AGENTS.md

@@ -67,20 +67,20 @@ pnpm test                   # same — package.json scripts call the CLI
 Keystroke is deploy-first: build, ship, then run and inspect what's live. Deploy often.
 
 1. **Auth once** — `keystroke auth login` (token is stored and reused).
-2. **Verify prerequisites** — `keystroke app execute <app> <tool> --input '{...}'` runs any connected catalog action against the cloud with no deploy and no server. Before wiring an integration into a workflow, execute it once for real: confirm the IDs, custom fields, and labels you're about to hard-code actually exist in the *connected* account. Schema inspection and hand-rolled dry-run flags prove nothing about the mutating path.
+2. **Verify prerequisites** — `keystroke apps execute <app> <tool> --input '{...}'` runs any connected catalog action against the cloud with no deploy and no server. Before wiring an integration into a workflow, execute it once for real: confirm the IDs, custom fields, and labels you're about to hard-code actually exist in the *connected* account. Schema inspection and hand-rolled dry-run flags prove nothing about the mutating path.
 3. **Edit** primitives under `src/`. Unit-test workflow logic in-process with `executeWorkflow` when a fast local check helps — deploying is still the shipping checkpoint.
 4. **Deploy** — `keystroke deploy` (full) or `keystroke deploy --filter agents/support` (one module). Deploy runs lint and typecheck first — attempt it directly; do not pre-run lint, typecheck, or build.
-5. **Run** — `keystroke workflow run <slug> --input '{...}'` / `keystroke agent prompt <slug> --message "..."`.
+5. **Run** — `keystroke workflows run <slug> --input '{...}'` / `keystroke agents prompt <slug> --message "..."`.
 6. **Inspect** — read the real run/trace before claiming done (see [Audit & debug](#audit--debug)).
 7. Repeat.
 
 ```bash
 keystroke auth status                                     # current user + org
-keystroke project list                                    # your platform projects
+keystroke projects list                                    # your platform projects
 keystroke deploy                                          # lint + typecheck + build + ship dist/ (first deploy must be full)
-keystroke workflow run greeting --input '{"name":"Ada"}'  # run a workflow
-keystroke agent prompt hello --message "Hi"               # prompt an agent
-keystroke app execute github github_get_the_authenticated_user     # run a connected catalog action
+keystroke workflows run greeting --input '{"name":"Ada"}'  # run a workflow
+keystroke agents prompt hello --message "Hi"               # prompt an agent
+keystroke apps execute github github_get_the_authenticated_user     # run a connected catalog action
 ```
 
 New project: `keystroke init my-app --yes`, then deploy. Join an existing cloud project: `keystroke pull --project <slug>`.
@@ -216,7 +216,7 @@ export default defineWebhookSource({
 
 Filters live on the source; `transform` lives on the workflow attachment. Agents use `.attach({ agent, prompt })` (not `transform`). Attachment id: `{sourceSlug}:{targetSlug}`.
 
-**Deploy timing** — webhooks are passive and safe to deploy any time. A poll fires immediately on deploy; a cron waits for its next scheduled slot, then runs unattended. Until the workflow is verified, pause with `keystroke trigger attachment disable` — the disabled state survives redeploys.
+**Deploy timing** — webhooks are passive and safe to deploy any time. A poll fires immediately on deploy; a cron waits for its next scheduled slot, then runs unattended. Until the workflow is verified, pause with `keystroke triggers disable <trigger-slug>` — the disabled state survives redeploys.
 
 ## Integrations & credentials
 
@@ -224,20 +224,20 @@ Keystroke has 1,000+ built-in integrations, and it's easy to build a custom one
 
 Discover apps and actions with the CLI — the docs integration index is **not** reliable for discovery:
 
-One `<app> <tool>` shape flows through discovery → inspect → run. `app action`/`app actions` print the next step (run, import, connect) after their output.
+One `<app> <tool>` shape flows through discovery → inspect → run. `apps actions get` / `apps actions list` print the next step (run, import, connect) after their output.
 
 ```bash
-keystroke app list                          # all registered apps
-keystroke app search <query>                # find an app + slug in the full catalog
-keystroke app actions <app> --search <q>    # actions an app exposes
-keystroke app action <app> <tool>           # schema + how to run/import one action
-keystroke app execute <app> <tool> --input '{...}'   # run a connected catalog action (no server)
+keystroke apps list                          # all registered apps
+keystroke apps search <query>                # find an app + slug in the full catalog
+keystroke apps actions list <app> --search <q>    # actions an app exposes
+keystroke apps actions get <app> <tool>           # schema + how to run/import one action
+keystroke apps execute <app> <tool> --input '{...}'   # run a connected catalog action (no server)
 keystroke credentials list                  # what's already connected — check before asking the user to connect
 keystroke connect <slug>                    # connect an app credential (opens web OAuth/api key flow for the user)
-keystroke credentials set <key> --set apiKey=@env:MY_KEY   # static API key
+keystroke credentials create <key> --set apiKey=@env:MY_KEY   # static API key
 ```
 
-Check `keystroke credentials list` before telling the user to connect anything — the credential often already exists (each row shows the app and scope; `app action` output does *not* show connection status, so the list is the only reliable check).
+Check `keystroke credentials list` before telling the user to connect anything — the credential often already exists (each row shows the app and scope; `apps actions get` output does *not* show connection status, so the list is the only reliable check).
 
 Credentials are for secrets. Non-secret config — spreadsheet IDs, channel names, base URLs — belongs in code as a literal constant or a workflow input. There is no platform variable store and `keystroke deploy` **never uploads `.env`**, so a constant in source is the correct home, not a workaround. Missing a built-in integration? Use `defineCredential` + an action, `defineApp`, or `defineMcp`. See `/learn/credentials/custom-integrations`.
 
@@ -259,16 +259,16 @@ Both materialize into the agent's `/workspace/agent/...` environment before each
 Inspect deployed runs with `--include` to see full traces:
 
 ```bash
-keystroke workflow runs list <workflow-slug>
-keystroke workflow runs get <workflow-slug> <run-id> --include steps,trace
+keystroke workflows runs list <workflow-slug>
+keystroke workflows runs get <workflow-slug> <run-id> --include steps,trace
 
-keystroke agent sessions list <agent-slug>
-keystroke agent sessions get <agent-slug> <session-id> --include messages,trace
+keystroke agents sessions list <agent-slug>
+keystroke agents sessions get <agent-slug> <session-id> --include messages,trace
 
-keystroke trigger list
-keystroke trigger url <trigger-slug>                          # webhook URL (+ ?token= on platform)
-keystroke trigger runs get <trigger-slug>:<workflow-slug> <run-id> --include workflows,trace
-keystroke trigger attachment disable <trigger-slug> <trigger-slug>:<workflow-slug>   # pause without redeploy (takes both the trigger slug and the attachment id)
+keystroke triggers list
+keystroke triggers url <trigger-slug>                          # webhook URL (+ ?token= on platform)
+keystroke triggers runs get <trigger-slug> <run-id> --workflow <workflow-slug> --include workflows,trace
+keystroke triggers disable <trigger-slug>   # pause without redeploy; --workflow/--agent narrows to one attachment
 
 keystroke history list --kind workflow --status failed
 ```
@@ -280,10 +280,10 @@ Invoke/inspect commands print JSON to stdout (exit 0 on success, 1 on failure)
 - [ ] Deployed the change and read the real run output/trace — not just "it should work".
 - [ ] Prompted agents / ran workflows with realistic input and verified behavior.
 - [ ] Researched real APIs before mirroring them in custom integration actions — no guessed endpoints or payloads.
-- [ ] Executed each mutating integration action once via `keystroke app execute` before composing it — a passing dry-run flag doesn't count.
+- [ ] Executed each mutating integration action once via `keystroke apps execute` before composing it — a passing dry-run flag doesn't count.
 - [ ] Covered obvious edge cases (null field, empty array, a step that throws) with a simple test where warranted.
 - [ ] Checked `keystroke credentials list` before connecting; connected any new apps with `keystroke connect` (not `.env`).
-- [ ] Tested manually before deploying attached cron/polling triggers, or used `trigger attachment disable` to pause until ready.
+- [ ] Tested manually before deploying attached cron/polling triggers, or used `triggers disable` to pause until ready.
 
 ## Common gotchas
 

package/dist/templates/hello-world/README.md

@@ -7,7 +7,7 @@ Lint, typecheck, and test configs live in the CLI; this project only adds the pa
 ```bash
 pnpm install
 keystroke auth login                       # once
-keystroke project link --project <slug>    # keystroke project list
+keystroke projects link --project <slug>    # keystroke projects list
 keystroke deploy                           # lint + typecheck + build + ship dist/ (no pre-steps needed)
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@keystrokehq/cli",
-  "version": "0.1.49",
+  "version": "0.1.51",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/keystrokehq/keystroke.git",