@genspark/cli 1.11.2 → 1.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (40) hide show
  1. package/README.md +89 -25
  2. package/dist/client.d.ts +4 -0
  3. package/dist/client.d.ts.map +1 -1
  4. package/dist/client.js +7 -0
  5. package/dist/client.js.map +1 -1
  6. package/dist/commands/chat-events.d.ts +1 -1
  7. package/dist/commands/chat-events.js +1 -1
  8. package/dist/commands/pi-config.d.ts +30 -0
  9. package/dist/commands/pi-config.d.ts.map +1 -0
  10. package/dist/commands/pi-config.js +72 -0
  11. package/dist/commands/pi-config.js.map +1 -0
  12. package/dist/config.d.ts +1 -1
  13. package/dist/config.d.ts.map +1 -1
  14. package/dist/config.js +12 -1
  15. package/dist/config.js.map +1 -1
  16. package/dist/confirm.d.ts +59 -3
  17. package/dist/confirm.d.ts.map +1 -1
  18. package/dist/confirm.js +91 -11
  19. package/dist/confirm.js.map +1 -1
  20. package/dist/index.d.ts.map +1 -1
  21. package/dist/index.js +195 -14
  22. package/dist/index.js.map +1 -1
  23. package/dist/types.d.ts +7 -0
  24. package/dist/types.d.ts.map +1 -1
  25. package/docs/confirmation.md +113 -6
  26. package/docs/skills.md +3 -2
  27. package/package.json +1 -1
  28. package/skills/gsk-aidrive/SKILL.md +19 -3
  29. package/skills/gsk-genteam/SKILL.md +7 -8
  30. package/skills/gsk-gmail/SKILL.md +7 -7
  31. package/skills/gsk-google-calendar/SKILL.md +2 -4
  32. package/skills/gsk-google-chat/SKILL.md +2 -4
  33. package/skills/gsk-google-drive/SKILL.md +4 -2
  34. package/skills/gsk-microsoft-teams/SKILL.md +3 -7
  35. package/skills/gsk-onedrive/SKILL.md +4 -2
  36. package/skills/gsk-outlook-calendar/SKILL.md +2 -4
  37. package/skills/gsk-outlook-email/SKILL.md +7 -7
  38. package/skills/gsk-sb-brain/SKILL.md +130 -0
  39. package/skills/gsk-shared/SKILL.md +2 -0
  40. package/skills/gsk-slack/SKILL.md +4 -4
package/docs/skills.md CHANGED
@@ -2,9 +2,9 @@
2
2
 
3
3
  > Auto-generated by `python -m backend.genspark_tool_cli.generate_skills`. Do not edit manually.
4
4
 
5
- **Total skills:** 56
5
+ **Total skills:** 57
6
6
 
7
- ## Service Skills (56)
7
+ ## Service Skills (57)
8
8
 
9
9
  | Skill | Description |
10
10
  |-------|-------------|
@@ -44,6 +44,7 @@
44
44
  | [gsk-outlook-email](../skills/gsk-outlook-email/SKILL.md) | Outlook Email operations. Actions: search, read, list_folders, create_folder, list_emails, list_email_changes, list_r... |
45
45
  | [gsk-phone-call](../skills/gsk-phone-call/SKILL.md) | Make a real AI phone call on the user's behalf. Validates prerequisites (membership, phone setup, credits), resolves ... |
46
46
  | [gsk-salesforce](../skills/gsk-salesforce/SKILL.md) | Salesforce DX CLI (`sf`) operations in a pre-authenticated sandbox. Actions: run (forwards any `sf` subcommand). |
47
+ | [gsk-sb-brain](../skills/gsk-sb-brain/SKILL.md) | Unified read-only access to the user's Second Brain — notes, emails, meetings, and connected knowledge sources. Ident... |
47
48
  | [gsk-scholar-search](../skills/gsk-scholar-search/SKILL.md) | Search scholarly articles and academic papers. Returns matching papers with titles, authors, venues, and citation cou... |
48
49
  | [gsk-sharepoint](../skills/gsk-sharepoint/SKILL.md) | SharePoint site, list, and file operations. Actions: list, list_items, search, read_content, read_file, upload. |
49
50
  | [gsk-sharepoint-upload](../skills/gsk-sharepoint-upload/SKILL.md) | Upload a file to a SharePoint document library. |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@genspark/cli",
3
- "version": "1.11.2",
3
+ "version": "1.12.0",
4
4
  "description": "CLI tool for Genspark Tool API - search, crawl, analyze images, generate media",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -36,15 +36,31 @@ gsk drive [options]
36
36
 
37
37
  **Aliases:** `drive`
38
38
 
39
+ ## GenTeam drive layout and permissions
40
+
41
+ GenTeam channel and DM drives are flat native containers. `mkdir`, directory
42
+ upload, and moving/restoring native entries into subfolders are rejected with
43
+ `GENTEAM_DRIVE_FLAT_LAYOUT`, including calls using an ID or browser URL. Admin
44
+ access does not override this layout. Channel members with content-edit access
45
+ can upload files at the root; moving, renaming, or deleting native files requires
46
+ conversation administrator access. Removing a shared alias uses its existing
47
+ sharing authorization and never removes its source.
48
+
49
+ Share a file or folder from an allowed source drive to the GenTeam drive root
50
+ with `link`. Use that link's `link_workspace_id` to access the source folder: its
51
+ own hierarchy and ACL remain intact. Existing native legacy folders may be read
52
+ and removed for recovery, but cannot receive new files or be restored.
53
+
39
54
  ## Flags
40
55
 
41
56
  | Flag | Required | Description |
42
57
  |------|----------|-------------|
43
58
  | `<action>` (positional) | Yes | Action to perform (string, one of: ls, find, mkdir, rm, move, get_readable_url, download, download_video, download_audio, download_file, compress, decompress, share, unshare, access, link, unlink, upload, list_trash, restore) |
44
- | `--workspace` | No | AI Drive location. my_drive owns your bytes and quota; shared_drive selects managed org, GenTeam, Hub, or authorized knowledge drives; shared_with_me is an ACL-filtered view across both kinds of container and owns no bytes or quota. (string, one of: my_drive, shared_with_me, shared_drive, default: `my_drive`) |
59
+ | `--workspace` | No | AI Drive location. my_drive owns your bytes and quota; shared_drive selects managed org, GenTeam, Hub, or authorized knowledge drives; shared_with_me is an ACL-filtered view across both kinds of container and owns no bytes or quota. GenTeam drives are flat: upload files or share source folders at the root; no native mkdir. Moving, renaming, and deleting native files requires an admin. (string, one of: my_drive, shared_with_me, shared_drive, default: `my_drive`) |
45
60
  | `--source` | No | Stable source_id returned by ls in shared_with_me or shared_drive. It identifies the storage-owning drive and entry; names are accepted only when unique. (string) |
46
61
  | `--share` | No | Deprecated alias for source, retained for older gsk scripts. (string) |
47
- | `--to` | No | Who to share with, for share/unshare: an email address; My Drive also accepts 'org' / 'group:<uid>'. Managed Drive sources use email or general_access. (string) |
62
+ | `--to` | No | Who to share with, for share/unshare: an email address; My Drive also accepts 'org' / 'group:<uid>' and 'channel:<server_id>:<channel_id>' (a GenTeam channel you belong to — the file is opened to its members and, unless post_card is false, posted there as a card). Managed Drive sources use email or general_access; a Team Drive source (workspace=shared_drive, source=<source_id>) also takes 'channel:…' — for its root, or for one entry inside it named by path (relative to the source) or id — when you manage sharing there. (string) |
63
+ | `--post_card` | No | For share to a channel: also post the document card into the channel (default true). false opens the file to the channel's members without a message. (boolean, default: `True`) |
48
64
  | `--permission` | No | What the recipient or delegated mount may do: view or edit (share/link). The public link audience can only ever view. (string, one of: view, edit, default: `view`) |
49
65
  | `--link_name` | No | Optional destination alias for link. The source entry's current name is used when omitted. (string) |
50
66
  | `--general_access` | No | Who else can open it, for share without a recipient: restricted, org, or link. (string, one of: restricted, org, link) |
@@ -65,7 +81,7 @@ gsk drive [options]
65
81
  | `--file_url` | No | External file URL to save into Drive with download_file (string) |
66
82
  | `--file_name` | No | Filename for download_file (for example annual_report.pdf); inferred when omitted (string) |
67
83
  | `--file_content` | No | Content to upload to AI Drive. Can be plain text or base64-encoded binary data. For text files (txt, md, json, csv, etc.), provide plain text content. For binary files, provide base64-encoded content with 'base64:' prefix. Size limit: 1MB without confirmation, 5MB absolute maximum. (string) |
68
- | `--upload_path` | No | Target path for upload action (must start with '/' and include filename). To upload a new version of an existing file, reuse the same path with overwrite=true instead of creating v2/_final name variants; give genuinely new artifacts (e.g. each run of a recurring workflow) their own path. Create parent directories with mkdir first if they don't exist. (string) |
84
+ | `--upload_path` | No | Target path for upload action (must start with '/' and include filename). To upload a new version of an existing file, reuse the same path with overwrite=true instead of creating v2/_final name variants; give genuinely new artifacts (e.g. each run of a recurring workflow) their own path. In GenTeam drives, upload at the root. Elsewhere, create missing parent directories with mkdir first. (string) |
69
85
  | `--overwrite` | No | Set to true to overwrite the existing file at upload_path (upload action only; default false fails if the path exists). (boolean) |
70
86
  | `--content_type` | No | MIME type of the content. If not provided, will be auto-detected from filename. Common types: text/plain, text/markdown, application/json, text/csv (string) |
71
87
  | `--confirmed` | No | Set to true to confirm upload when: (1) file size > 1MB, or (2) content contains potentially sensitive patterns. If confirmation is required but not provided, upload will fail with a warning. (boolean) |
@@ -4,7 +4,8 @@ version: 1.0.0
4
4
  description: 'GenTeam (Genspark team workspace) operations as the calling user. Actions:
5
5
  join, channels, agents, read, threads, download, search, send, react, delete, update,
6
6
  create_channel, update_channel, invite_link, members, tasks, mark_read, forward,
7
- pins, dm.'
7
+ pins, dm, archive_channel, unarchive_channel, delete_channel, leave_channel (the
8
+ last four: internal dogfood, employee accounts only).'
8
9
  metadata:
9
10
  category: general
10
11
  requires:
@@ -17,7 +18,7 @@ metadata:
17
18
 
18
19
  **PREREQUISITE:** Read `../gsk-shared/SKILL.md` for auth, global flags, and security rules.
19
20
 
20
- GenTeam (Genspark team workspace) operations as the calling user. Actions: join, channels, agents, read, threads, download, search, send, react, delete, update, create_channel, update_channel, invite_link, members, tasks, mark_read, forward, pins, dm.
21
+ GenTeam (Genspark team workspace) operations as the calling user. Actions: join, channels, agents, read, threads, download, search, send, react, delete, update, create_channel, update_channel, invite_link, members, tasks, mark_read, forward, pins, dm, archive_channel, unarchive_channel, delete_channel, leave_channel (the last four: internal dogfood, employee accounts only).
21
22
 
22
23
  ## Usage
23
24
 
@@ -29,13 +30,13 @@ gsk genteam [options]
29
30
 
30
31
  | Flag | Required | Description |
31
32
  |------|----------|-------------|
32
- | `<action>` (positional) | Yes | Action to perform. 'join': Join a GenTeam workspace or group chat from an invite link; 'channels': List the caller's workspaces, or one workspace's group chats by server_slug; 'agents': List a workspace's agents visible to the caller by server_slug; each id is a mention target for send; 'read': Read recent messages from a group chat, DM, or thread; around_message_id fetches the window around one message (e.g. a search hit); a thread is also addressable by its root message id via parent_message_id; 'threads': List a group chat's or DM's threads (thread channel id, root comet_message_id, caller_is_participant, reply count / last activity); channel membership is the only requirement; 'download': Download one message attachment (attachments[].attachment_ref from read output) to a fetchable file-wrapper URL; 'search': Search a workspace by server_slug, or one group chat, DM, or thread by channel_id; 'send': Send a message (text, attachment, or thread reply) to a group chat or DM as the caller; a thread reply is also addressable by its root message id via parent_message_id. Supports native @mentions (humans and agents) and native quote replies. Held for confirmation before anything is posted. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'react': Emoji-react to a message in a group chat, DM, or thread (or remove your own reaction). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'delete': Delete one of YOUR OWN messages in a group chat, DM, or thread (author-only, the same gate the app enforces). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'update': Edit the text of one of YOUR OWN messages (the caption on an attachment message); attachments and existing @mentions are preserved (author-only, the same gate the app enforces). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'create_channel': Create a group chat in a workspace; the caller becomes its manager and auto-joins. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'update_channel': Edit a group chat's display name, description, or member permission switches (manager only). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'invite_link': Create, list, or revoke the invite links that genteam_join consumes (workspace or group chat scoped). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'members': List, add, or remove group chat members (humans and agents) by actor id; op=list also reads a DM's or thread's roster. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'tasks': Task board: list a group chat's, DM's, or workspace's tasks, get one task with its event history, create a task from a message, claim/unclaim it, assign it to one of the caller's agents (op=candidates lists them), rename it, or change its status. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'mark_read': Mark a group chat, DM, or thread read (clears the caller's unread count), or back to unread with unread=true; 'forward': Forward one message to another group chat or DM you can post to. A plain message is normally re-sent as the caller's own message (no forward marker or original-author label); a display card or oversized text lands as a chat-history card that keeps the original speaker. An optional note is sent as a separate message right after it. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'pins': List a group chat's pinned messages, or pin/unpin one by its comet_message_id (any active member may, the same rule the app enforces; a thread id addresses its parent group chat's pins). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'dm': List the caller's DMs in a workspace (op=list: peer actor_type + actor_id per row), or open a DM with a human contact or agent (op=open: returns the app's deterministic channel_id, reusing an existing DM; held for confirmation). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes. (string, one of: join, channels, agents, read, threads, download, search, send, react, delete, update, create_channel, update_channel, invite_link, members, tasks, mark_read, forward, pins, dm) |
33
+ | `<action>` (positional) | Yes | Action to perform. 'join': Join a GenTeam workspace or group chat from an invite link; 'channels': List the caller's workspaces, or one workspace's group chats by server_slug; 'agents': List a workspace's agents visible to the caller by server_slug; each id is a mention target for send; 'read': Read recent messages from a group chat, DM, or thread; around_message_id fetches the window around one message (e.g. a search hit); a thread is also addressable by its root message id via parent_message_id; 'threads': List a group chat's or DM's threads (thread channel id, root comet_message_id, caller_is_participant, reply count / last activity); channel membership is the only requirement; 'download': Download one message attachment (attachments[].attachment_ref from read output) to a fetchable file-wrapper URL; 'search': Search a workspace by server_slug, or one group chat, DM, or thread by channel_id; 'send': Send a message (text, attachment, or thread reply) to a group chat or DM as the caller; a thread reply is also addressable by its root message id via parent_message_id. Supports native @mentions (humans and agents) and native quote replies. Held for confirmation before anything is posted. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'react': Emoji-react to a message in a group chat, DM, or thread (or remove your own reaction). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'delete': Delete one of YOUR OWN messages in a group chat, DM, or thread (author-only, the same gate the app enforces). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'update': Edit the text of one of YOUR OWN messages (the caption on an attachment message); attachments and existing @mentions are preserved (author-only, the same gate the app enforces). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'create_channel': Create a group chat in a workspace; the caller becomes its manager and auto-joins. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'update_channel': Edit a group chat's display name, description, or member permission switches (manager only). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'invite_link': Create, list, or revoke the invite links that genteam_join consumes (workspace or group chat scoped). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Not confirmation-gated when op is list: those values run immediately (no prompt, no pending_confirmation step).; 'members': List, add, or remove group chat members (humans and agents) by actor id; op=list also reads a DM's or thread's roster. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Not confirmation-gated when op is list: those values run immediately (no prompt, no pending_confirmation step).; 'tasks': Task board: list a group chat's, DM's, or workspace's tasks, get one task with its event history, create a task from a message, claim/unclaim it, assign it to one of the caller's agents (op=candidates lists them), rename it, or change its status. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Not confirmation-gated when op is list, get or candidates: those values run immediately (no prompt, no pending_confirmation step).; 'mark_read': Mark a group chat, DM, or thread read (clears the caller's unread count), or back to unread with unread=true; 'forward': Forward one message to another group chat or DM you can post to. A plain message is normally re-sent as the caller's own message (no forward marker or original-author label); a display card or oversized text lands as a chat-history card that keeps the original speaker. An optional note is sent as a separate message right after it. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'pins': List a group chat's pinned messages, or pin/unpin one by its comet_message_id (any active member may, the same rule the app enforces; a thread id addresses its parent group chat's pins). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Not confirmation-gated when op is list: those values run immediately (no prompt, no pending_confirmation step).; 'dm': List the caller's DMs in a workspace (op=list: peer actor_type + actor_id per row), or open a DM with a human contact or agent (op=open: returns the app's deterministic channel_id, reusing an existing DM; held for confirmation). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Not confirmation-gated when op is list: those values run immediately (no prompt, no pending_confirmation step).; 'archive_channel': Archive a group chat (manager only): reversible freeze, unarchive_channel restores it. Internal dogfood — employee accounts only. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'unarchive_channel': Restore an archived group chat to live (manager only). Internal dogfood — employee accounts only. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'delete_channel': Delete a group chat (manager only; DMs and threads refused); not restorable from the CLI — prefer archive_channel when the history may still be needed. Internal dogfood — employee accounts only. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'leave_channel': Leave a group chat you are a member of (the last manager must delegate or delete instead). Internal dogfood — employee accounts only. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). (string, one of: join, channels, agents, read, threads, download, search, send, react, delete, update, create_channel, update_channel, invite_link, members, tasks, mark_read, forward, pins, dm, archive_channel, unarchive_channel, delete_channel, leave_channel) |
33
34
  | `--invite_url` | No | [join] Full invite link URL, including the token query parameter. (string) |
34
35
  | `--invite_id` | No | [join] Invite link id (alternative to invite_url; requires token). \| [invite_link] Invite link id to revoke (from op=list or the create result). (string) |
35
36
  | `--token` | No | [join] Invite link token (alternative to invite_url; requires invite_id). (string) |
36
37
  | `--server_slug` | No | [channels] Workspace slug (from the workspace list or a GenTeam URL path segment). \| [agents] Workspace slug (from genteam_list_channels or a GenTeam URL path segment). \| [search] Workspace slug (from genteam_list_channels or a GenTeam URL path segment). Required unless channel_id is given. \| [create_channel] Workspace slug (from genteam_list_channels or a GenTeam URL path segment). \| [invite_link] Workspace slug; required unless channel_id is given. \| [tasks] list: workspace slug (from genteam_list_channels) for the caller's workspace-wide board. \| [dm] Workspace slug (from genteam_list_channels or a GenTeam URL path segment). (string) |
37
38
  | `--mine` | No | [agents] When true, return only agents the caller created. Default false. (boolean) |
38
- | `--channel_id` | No | [read] Group chat, DM, or thread id (group chats and DMs from genteam_list_channels; thread ids from genteam_threads or genteam_tasks output). Optional when parent_message_id is passed. \| [threads] Group chat or DM id whose threads to list (from genteam_list_channels). \| [download] Group chat, DM, or thread id the attachment's message lives in (the channel_id on the read output's attachment row). \| [search] Group chat, DM, or thread to search within (group chats and DMs from genteam_list_channels; thread ids from genteam_threads or genteam_tasks output). \| [send] Target group chat, DM, or thread id (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). Optional when parent_message_id is passed. \| [react] Group chat, DM, or thread id the message lives in (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). \| [delete] Group chat, DM, or thread id the message lives in (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). \| [update] Group chat, DM, or thread id the message lives in (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). \| [update_channel] Group chat id (from genteam_list_channels). \| [invite_link] Group chat id — scopes create/list to that group chat's join links. \| [members] Group chat id (from genteam_list_channels); op=list also accepts a DM or thread id. \| [tasks] list: group chat or DM board target (from genteam_list_channels). Mutually exclusive with server_slug. create/candidates: the group chat or DM whose board is targeted (required). \| [mark_read] Group chat, DM, or thread id (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). \| [forward] Group chat, DM, or thread id the message lives in (from genteam_list_channels; thread ids arrive in context, e.g. genteam_read output). \| [pins] Group chat id (from genteam_list_channels); a thread id resolves to its parent group chat's pins. (string) |
39
+ | `--channel_id` | No | [read] Group chat, DM, or thread id (group chats and DMs from genteam_list_channels; thread ids from genteam_threads or genteam_tasks output). Optional when parent_message_id is passed. \| [threads] Group chat or DM id whose threads to list (from genteam_list_channels). \| [download] Group chat, DM, or thread id the attachment's message lives in (the channel_id on the read output's attachment row). \| [search] Group chat, DM, or thread to search within (group chats and DMs from genteam_list_channels; thread ids from genteam_threads or genteam_tasks output). \| [send] Target group chat, DM, or thread id (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). Optional when parent_message_id is passed. \| [react] Group chat, DM, or thread id the message lives in (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). \| [delete] Group chat, DM, or thread id the message lives in (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). \| [update] Group chat, DM, or thread id the message lives in (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). \| [update_channel] Group chat id (from genteam_list_channels). \| [invite_link] Group chat id — scopes create/list to that group chat's join links. \| [members] Group chat id (from genteam_list_channels); op=list also accepts a DM or thread id. \| [tasks] list: group chat or DM board target (from genteam_list_channels). Mutually exclusive with server_slug. create/candidates: the group chat or DM whose board is targeted (required). \| [mark_read] Group chat, DM, or thread id (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). \| [forward] Group chat, DM, or thread id the message lives in (from genteam_list_channels; thread ids arrive in context, e.g. genteam_read output). \| [pins] Group chat id (from genteam_list_channels); a thread id resolves to its parent group chat's pins. \| [archive_channel] Group chat id (from genteam_list_channels). \| [unarchive_channel] Group chat id (from genteam_list_channels). \| [delete_channel] Group chat id (from genteam_list_channels). \| [leave_channel] Group chat id (from genteam_list_channels). (string) |
39
40
  | `--parent_message_id` | No | [read] comet_message_id of a thread's root message: read that message's thread without knowing the thread channel id. If channel_id is also passed it must agree (the thread itself, or the group chat/DM containing the root message). \| [send] comet_message_id of a thread's root message: post this message as a reply in that message's thread without knowing the thread channel id. If channel_id is also passed it must agree (the thread itself, or the group chat/DM containing the root message). (string) |
40
41
  | `--limit` | No | [read] Messages to return (1..200). Default 20. \| [search] Workspace mode only: max hits per group (default 8). Conversation mode pages are a fixed 20 per request. \| [tasks] list (channel_id mode): page size, 1..100 (default 20). (integer) |
41
42
  | `--before_message_id` | No | [read] Message id cursor: return messages strictly older than this id. (string) |
@@ -50,10 +51,8 @@ gsk genteam [options]
50
51
  | `--file_name` | No | [send] Display file name for the attachment; defaults to the name derived from file_path. (string) |
51
52
  | `--mentions` | No | [send] Members to @mention — humans or agents: agent ids (agent_…, from genteam_list_agents), human member ids (UUID), or exact display names (must be unambiguous in the target conversation). Each must already be a member of the target conversation. Mention chips render natively. Humans are notified; agents wake unless creator-only mode blocks the sender. Read any owner_only_mentions advisory in the reply before expecting an answer. A canonical @[name](id) token is auto-prepended to the body for each mention, skipped when the body already contains that member's token — so do NOT also write the token inline for the same member (it would be redundant, not doubled). (array) |
52
53
  | `--quote_message_id` | No | [send] comet_message_id of an existing message in this conversation (from genteam_read) to quote — renders as the app's native quote block. Text sends only. (string) |
53
- | `--operation_id` | No | [send] Idempotency key with two roles in the double-call confirmation flow: while the send is pending_confirmation, re-running the IDENTICAL call (same operation_id and arguments) is the confirmation itself and performs the send; after a successful send, retries with the same operation_id return the already-sent message instead of posting a duplicate. \| [forward] Optional idempotency key (8-64 chars of [A-Za-z0-9_-]). After a successful forward, retries with the same operation_id return the already-forwarded message instead of posting a duplicate. Without it a re-run posts a duplicate forward. (string) |
54
+ | `--operation_id` | No | [send] Optional idempotency key (8-64 chars of [A-Za-z0-9_-]). After a successful send, retries with the same operation_id return the already-sent message instead of posting a duplicate. A re-run of a send that was held for confirmation must carry the same operation_id and arguments to be recognised as the same send. \| [forward] Optional idempotency key (8-64 chars of [A-Za-z0-9_-]). After a successful forward, retries with the same operation_id return the already-forwarded message instead of posting a duplicate. Without it a re-run posts a duplicate forward. (string) |
54
55
  | `--skip_sent_via_tag` | No | [send] Messages sent through this tool carry a small 'via API' source tag next to the sender name. Set true to send this one message without the tag. (boolean) |
55
- | `--skip_confirmation` | No | [send] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending: the first call returns pending_confirmation and an identical re-run confirms). On LLM agent paths the flag is only honored after the user actually confirmed. \| [react] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [delete] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [update] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [create_channel] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [update_channel] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [invite_link] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [members] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [tasks] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [forward] If true, skip user confirmation and forward immediately. Default is false (require confirmation before posting: the first call returns pending_confirmation and an identical re-run confirms). \| [pins] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [dm] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). (boolean, default: `False`) |
56
- | `--auto_skip_confirmation` | No | [send] Set by the workflow engine when the node is configured to skip confirmation. \| [react] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [delete] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [update] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [create_channel] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [update_channel] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [invite_link] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [members] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [tasks] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [forward] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [pins] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [dm] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. (boolean) |
57
56
  | `--message_id` | No | [react] comet_message_id of the message to react to (from genteam_read). \| [delete] comet_message_id of YOUR OWN message to delete (from genteam_read). \| [update] comet_message_id of YOUR OWN message to edit (from genteam_read). \| [mark_read] Optional comet_message_id (from genteam_read). Marking read: the highest message to mark read (inclusive); omit to mark the whole conversation read. Marking unread: the first message to show as unread (group chats and DMs only — threads take no anchor); omit to anchor at the latest message. \| [forward] comet_message_id of the message to forward (from genteam_read of the source conversation). \| [pins] pin/unpin: comet_message_id of the target message (from genteam_read or op=list output). (string) |
58
57
  | `--emoji` | No | [react] The emoji as a unicode character itself, e.g. '👍' or '🎉' (not ':thumbsup:'). (string) |
59
58
  | `--remove` | No | [react] true removes YOUR OWN existing reaction instead of adding one. Default: false. (boolean, default: `False`) |
@@ -88,7 +87,7 @@ Parameters that accept URLs (`--invite_url`) also accept local file paths. The C
88
87
 
89
88
  ## Write Confirmation
90
89
 
91
- Confirmation-gated actions: `send`, `react`, `delete`, `update`, `create_channel`, `update_channel`, `invite_link`, `members`, `tasks`, `forward`, `pins`, `dm` (plus write methods through `api` where present). A CLI with client-side confirmation prompts `[y/N]` (or honors `--yes`) and executes in a single call; the rest of this section is the double-call contract for older CLIs. Completing that confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
90
+ Confirmation-gated actions: `send`, `react`, `delete`, `update`, `create_channel`, `update_channel`, `invite_link` (except `op=list`, which runs immediately), `members` (except `op=list`, which runs immediately), `tasks` (except `op=list/get/candidates`, which runs immediately), `forward`, `pins` (except `op=list`, which runs immediately), `dm` (except `op=list`, which runs immediately), `archive_channel`, `unarchive_channel`, `delete_channel`, `leave_channel`. An action marked `(except <param>=<values>)` is gated only for the other values of that argument — the listed values run immediately with no prompt and no confirmation step. The CLI shows a preview and asks `[y/N]` on stderr before the single server call; pass `--yes` (`-y`) for unattended runs. `--no-input` (or `--args-file -`, which consumes stdin) makes a gated call exit 2 with no server call instead of hanging. Never re-run a command to 'confirm' it — every call is a real execution. `--skip_confirmation true` / `--auto_skip_confirmation` are deprecated on this CLI (still accepted, warn on stderr): use `--yes`.
92
91
 
93
92
  ## See Also
94
93
 
@@ -31,7 +31,7 @@ gsk gmail [options]
31
31
 
32
32
  | Flag | Required | Description |
33
33
  |------|----------|-------------|
34
- | `<action>` (positional) | Yes | Action to perform. 'search': Search emails by query; 'read': Read a specific email by ID; 'send': Compose and send an email. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'draft': Save an email to the Drafts folder without sending; 'reply': Reply to an existing email. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'forward': Forward an email to new recipients. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'delete': Delete an email. Auto-approved: executes on the FIRST call — no [y/N] prompt and no pending_confirmation step. Do NOT re-run the command; a second call performs the operation again (e.g. sends a duplicate message).; 'archive': Archive an email; 'move': Move an email to a different label/folder. Auto-approved: executes on the FIRST call — no [y/N] prompt and no pending_confirmation step. Do NOT re-run the command; a second call performs the operation again (e.g. sends a duplicate message).; 'mark_as_read': Mark an email as read or unread; 'add_label': Add a label to an email; 'remove_label': Remove a label from an email; 'create_label': Create a new Gmail label; 'create_filter': Create a persistent Gmail filter. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'list_filters': List persistent Gmail filters; 'delete_filter': Delete a persistent Gmail filter. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'get_attachment': Download an email attachment; 'list_send_as': List available send-as aliases; 'get_vacation': Get the vacation (out-of-office) auto-reply settings; 'update_vacation': Enable, disable, or update the vacation (out-of-office) auto-reply. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'get_signature': Get the signature of a send-as address; 'update_signature': Set or clear the signature of a send-as address. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes. (string, one of: search, read, send, draft, reply, forward, delete, archive, move, mark_as_read, add_label, remove_label, create_label, create_filter, list_filters, delete_filter, get_attachment, list_send_as, get_vacation, update_vacation, get_signature, update_signature) |
34
+ | `<action>` (positional) | Yes | Action to perform. 'search': Search emails by query; 'read': Read a specific email by ID; 'send': Compose and send an email. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'draft': Save an email to the Drafts folder without sending; 'reply': Reply to an existing email. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'forward': Forward an email to new recipients. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'delete': Delete an email. Auto-approved: executes on the FIRST call — no [y/N] prompt and no pending_confirmation step. Do NOT re-run the command; a second call performs the operation again (e.g. sends a duplicate message).; 'archive': Archive one or more emails (pass message_ids to archive a whole set in one call); 'move': Move an email to a different label/folder. Auto-approved: executes on the FIRST call — no [y/N] prompt and no pending_confirmation step. Do NOT re-run the command; a second call performs the operation again (e.g. sends a duplicate message).; 'mark_as_read': Mark an email as read or unread; 'add_label': Add a label to an email; 'remove_label': Remove a label from an email; 'create_label': Create a new Gmail label; 'create_filter': Create a persistent Gmail filter. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'list_filters': List persistent Gmail filters; 'delete_filter': Delete a persistent Gmail filter. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'get_attachment': Download an email attachment; 'list_send_as': List available send-as aliases; 'get_vacation': Get the vacation (out-of-office) auto-reply settings; 'update_vacation': Enable, disable, or update the vacation (out-of-office) auto-reply. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'get_signature': Get the signature of a send-as address; 'update_signature': Set or clear the signature of a send-as address. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). (string, one of: search, read, send, draft, reply, forward, delete, archive, move, mark_as_read, add_label, remove_label, create_label, create_filter, list_filters, delete_filter, get_attachment, list_send_as, get_vacation, update_vacation, get_signature, update_signature) |
35
35
  | `--query` | No | [search] Query to filter emails using Gmail search syntax. Examples: - Simple: 'meeting' - From Sender: 'from:boss@example.com' - Subject: 'subject:report' - In Folder: 'in:spam', 'in:inbox', 'in:trash', 'in:sent' - Label: 'label:important' - Unread: 'is:unread' - Unread in Spam: 'in:spam is:unread' - Has Attachment: 'has:attachment' - Date Range: 'after:2024/01/01 before:2024/01/31' - Newer Than: 'newer_than:7d' (7 days) - Older Than: 'older_than:1m' (1 month) Note: Some queries like 'is:recent' are invalid. (string) |
36
36
  | `--after_date` | No | [search] Filter emails received after this date (inclusive). Format: YYYY/MM/DD (e.g., '2024/01/01'). This is equivalent to adding 'after:YYYY/MM/DD' to the query. (string) |
37
37
  | `--before_date` | No | [search] Filter emails received before this date (exclusive). Format: YYYY/MM/DD (e.g., '2024/01/31'). This is equivalent to adding 'before:YYYY/MM/DD' to the query. (string) |
@@ -53,21 +53,19 @@ gsk gmail [options]
53
53
  | `--bcc` | No | [send] Optional: BCC email address(es). For multiple recipients, separate with commas. \| [draft] BCC recipient(s), comma-separated. \| [forward] Optional: BCC email address(es). For multiple recipients, separate with commas. (string) |
54
54
  | `--content_type` | No | [send] Content type of the email body. Default: text/html (recommended) **CRITICAL**: This parameter defines the format of the 'body' field: - 'text/plain': body should be plain text only - 'text/html': body MUST be valid HTML (e.g., '<h1>Title</h1><p>Content</p>') **Common mistake**: Setting content_type='text/html' but providing Markdown text (# Title, **bold**). This will display raw Markdown symbols in the email. Always convert Markdown to HTML before passing to this tool. \| [reply] Content type of the reply body. Default: text/html (recommended) **CRITICAL**: This parameter defines the format of the 'body' field: - 'text/plain': body should be plain text only - 'text/html': body MUST be valid HTML (e.g., '<h1>Title</h1><p>Content</p>') **Common mistake**: Setting content_type='text/html' but providing Markdown text. This will display raw Markdown symbols. Always convert Markdown to HTML first. \| [forward] Content type of the body. Default: text/html (recommended) **CRITICAL**: This parameter defines the format of the 'body' field: - 'text/plain': body should be plain text only - 'text/html': body MUST be valid HTML (e.g., '<h1>Title</h1><p>Content</p>') **Common mistake**: Setting content_type='text/html' but providing Markdown text. This will display raw Markdown symbols. Always convert Markdown to HTML first. (string, one of: text/plain, text/html) |
55
55
  | `--from_address` | No | [send] Send-as email address to use as the sender. Use this to send as a group/alias address (e.g., 'feedback@company.com'). Must be configured in Gmail's 'Send mail as' settings. \| [draft] Optional 'From:' identity to send AS — Gmail verified alias, Outlook proxyAddress / mail-enabled group, or a granted SendAs / on-behalf address. Must be an address the from-account is authorized to send as (see 'send_as' on /api/ai-inbox/mailbox/accounts). For Gmail this becomes the draft's MIME 'From:' header; for Outlook the saved draft stays as the from-account and the alias is applied by the eventual send call. \| [reply] Send-as email address to use as the sender. Use this to reply as a group/alias address (e.g., 'feedback@company.com'). Must be configured in Gmail's 'Send mail as' settings. \| [forward] Send-as email address to use as the sender. Use this to forward as a group/alias address. Must be configured in Gmail's 'Send mail as' settings. (string) |
56
- | `--skip_confirmation` | No | [send] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [reply] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [forward] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [delete] If true, skip user confirmation and delete immediately. Default is false (require confirmation before deleting). \| [move] If true, skip user confirmation and move immediately. Default is false (require confirmation before moving). (boolean, default: `False`) |
57
- | `--auto_skip_confirmation` | No | [send] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [reply] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [forward] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [delete] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [move] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. (boolean, default: `False`) |
58
56
  | `--client_send_id` | No | [send] Optional stable idempotency key. When provided, stored in X-Genspark-Client-Send-Id and mirrored into a provider-safe Message-ID digest. Scheduled agent retries use it for internal deduplication. Usually auto-resolved from the active scheduled-action context — the LLM only needs to pass this when it wants to derive its own key (e.g. plan fan-out). (string) |
59
57
  | `--force_resend` | No | [send] Set true only when the user explicitly wants another copy of an otherwise identical email. This bypasses the 10-minute interactive-send deduplication window. (boolean, default: `False`) |
60
58
  | `--attachments` | No | [send] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). \| [draft] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). \| [reply] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). \| [forward] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). (array) |
61
59
  | `--body_type` | No | [draft] Body format: 'html' (default) or 'text'. (string) |
62
60
  | `--prompt` | No | [draft] Optional instruction describing the email to write, in the sender's own voice using their Email Brain (persona plus their handling and writing rules) — e.g. 'ask Ana to move the review to Friday, apologize for the short notice'. Use INSTEAD of 'body' to have the body written for you, or TOGETHER WITH 'body' to revise that text per the instruction (everything the instruction does not ask to change is preserved). Recipients and attachments are never inferred from the instruction — pass them explicitly. Omit to commit 'body' exactly as given. (string) |
63
- | `--message_id` | No | [reply] The Gmail message ID to reply to \| [forward] The Gmail message ID to forward \| [delete] The Gmail message ID to delete \| [archive] The Gmail message ID to archive \| [move] The Gmail message ID to move \| [mark_as_read] (Deprecated, use message_ids) A single Gmail message ID to mark \| [add_label] The Gmail message ID to add label to \| [remove_label] The Gmail message ID to remove label from \| [get_attachment] The Gmail message ID containing the attachment (string) |
61
+ | `--message_id` | No | [reply] The Gmail message ID to reply to \| [forward] The Gmail message ID to forward \| [delete] The Gmail message ID to delete \| [archive] (Deprecated, use message_ids) A single Gmail message ID to archive \| [move] The Gmail message ID to move \| [mark_as_read] (Deprecated, use message_ids) A single Gmail message ID to mark \| [add_label] The Gmail message ID to add label to \| [remove_label] The Gmail message ID to remove label from \| [get_attachment] The Gmail message ID containing the attachment (string) |
64
62
  | `--reply_all` | No | [reply] Whether to reply to all recipients (TO and CC). Default: true (reply to all recipients including CC) (boolean) |
65
63
  | `--include_original` | No | [reply] Whether to append the original message as a Gmail-style quoted block under the reply body so the recipient sees the thread context standard mail clients attach automatically. Default: true. Set to false only when the caller already embedded their own quoted block in `body` (the helper detects the canonical `gmail_quote_container` markup and short-circuits anyway, but this flag lets the caller opt out unconditionally — useful for terse one-line replies where the quote is noise). \| [forward] Whether to append the original message as a Gmail-style '---------- Forwarded message ----------' quoted block under the forwarder's note so the recipient sees the original verbatim — same shape as native Gmail forwards. Default: true. Set to false only when the caller already embedded their own forwarded block in `body` (e.g. the `.genmail` editor send path). (boolean, default: `True`) |
66
64
  | `--include_attachments` | No | [forward] Whether to include original email attachments in the forward. Default: true (boolean, default: `True`) |
65
+ | `--message_ids` | No | [archive] The Gmail message ID(s) to archive. Can be a single ID string or an array of IDs. \| [mark_as_read] The Gmail message ID(s) to mark. Can be a single ID string or an array of IDs. |
67
66
  | `--label_name` | No | [move] The target label name. Use '/' for nested labels (e.g., 'Work/Projects'). The label will be created if it doesn't exist. \| [add_label] The label name to add. Can be a new label or an existing one. \| [remove_label] The label name to remove \| [create_label] The name of the label to create. Use '/' for nested labels (e.g., 'Parent/Child'). (string) |
68
67
  | `--remove_from_inbox` | No | [move] Whether to remove the email from INBOX. Default: true (standard 'move' behavior). Set to false to just add the label without removing from inbox. (boolean) |
69
68
  | `--create_if_not_exists` | No | [move] Whether to create the label if it doesn't exist. Default: true (boolean) |
70
- | `--message_ids` | No | [mark_as_read] The Gmail message ID(s) to mark. Can be a single ID string or an array of IDs. |
71
69
  | `--is_read` | No | [mark_as_read] Set to true to mark as read, false to mark as unread. Default: true (boolean) |
72
70
  | `--label_list_visibility` | No | [create_label] The visibility of the label in the label list. Default: labelShow (string, one of: labelShow, labelShowIfUnread, labelHide) |
73
71
  | `--message_list_visibility` | No | [create_label] The visibility of messages with this label. Default: show (string, one of: show, hide) |
@@ -91,9 +89,11 @@ gsk gmail [options]
91
89
 
92
90
  ## Write Confirmation
93
91
 
94
- Confirmation-gated actions: `send`, `reply`, `forward`, `create_filter`, `delete_filter`, `update_vacation`, `update_signature` (plus write methods through `api` where present). A CLI with client-side confirmation prompts `[y/N]` (or honors `--yes`) and executes in a single call; the rest of this section is the double-call contract for older CLIs. Completing that confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
92
+ Confirmation-gated actions: `send`, `reply`, `forward`, `create_filter`, `delete_filter`, `update_vacation`, `update_signature`. The CLI shows a preview and asks `[y/N]` on stderr before the single server call; pass `--yes` (`-y`) for unattended runs. `--no-input` (or `--args-file -`, which consumes stdin) makes a gated call exit 2 with no server call instead of hanging. Never re-run a command to 'confirm' it — every call is a real execution. `--skip_confirmation true` / `--auto_skip_confirmation` are deprecated on this CLI (still accepted, warn on stderr): use `--yes`.
95
93
 
96
- Auto-approved actions: `delete`, `move` — the server skips the confirmation gate, so the operation executes on the FIRST call with no `[y/N]` prompt and no `pending_confirmation` step. Do NOT re-run the command expecting a confirmation arc: a second call performs the operation again (e.g. sends a duplicate message).
94
+ Interactive-only actions: `create_filter`, `delete_filter`, `update_vacation`, `update_signature` (the action excludes the skip params, e.g. Marketplace policy on Slack) — `--yes` is ignored and a real `[y/N]` answer is required.
95
+
96
+ Auto-approved actions: `delete`, `move` — the server skips the confirmation gate, so the operation executes on the FIRST call with no `[y/N]` prompt and no confirmation step. Do NOT re-run the command expecting a confirmation arc: a second call performs the operation again (e.g. sends a duplicate message).
97
97
 
98
98
  ## See Also
99
99
 
@@ -29,7 +29,7 @@ gsk google_calendar [options]
29
29
 
30
30
  | Flag | Required | Description |
31
31
  |------|----------|-------------|
32
- | `<action>` (positional) | Yes | Action to perform. 'list': List upcoming calendar events. Returns at most 'limit' (default 20) events; the response sets truncated=true when more events exist in the window; 'free_busy': Query free/busy intervals for calendars in a time window (find open meeting slots); 'create': Create a new calendar event. By default this returns a LOCAL DRAFT only — nothing lands in the calendar until the user confirms it in the Genspark UI. Callers without a confirmation UI (e.g. gsk) must pass --skip_confirmation to create the event directly; 'respond': RSVP (accept / decline / tentative) to an existing invite so the organizer's UI reflects the response; 'modify': Modify (events.patch) an existing event in place without delete+create; 'delete': Delete a calendar event. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes. (string, one of: list, free_busy, create, respond, modify, delete) |
32
+ | `<action>` (positional) | Yes | Action to perform. 'list': List upcoming calendar events. Returns at most 'limit' (default 20) events; the response sets truncated=true when more events exist in the window; 'free_busy': Query free/busy intervals for calendars in a time window (find open meeting slots); 'create': Create a new calendar event. By default this returns a LOCAL DRAFT only — nothing lands in the calendar until the user confirms it in the Genspark UI. Callers without a confirmation UI (e.g. gsk) must confirm the create (gsk: `--yes`) to write the event directly. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'respond': RSVP (accept / decline / tentative) to an existing invite so the organizer's UI reflects the response; 'modify': Modify (events.patch) an existing event in place without delete+create; 'delete': Delete a calendar event. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). (string, one of: list, free_busy, create, respond, modify, delete) |
33
33
  | `--filter_query` | No | [list] Text to filter calendar events, empty for listing all events (string) |
34
34
  | `--time_min` | No | [list] Optional. Start time of the search range (RFC3339 timestamp) (string) |
35
35
  | `--time_max` | No | [list] Optional. End time of the search range (RFC3339 timestamp) (string) |
@@ -49,8 +49,6 @@ gsk google_calendar [options]
49
49
  | `--event_id` | No | [create] The event identifier. If the request is to modify an existing event, provide the event_id of the event to be modified. If the request is to create a new event, leave this field empty. \| [respond] Google Calendar event id of the invitation to respond to. For a recurring-series instance, the id has shape '<seriesId>_<startTs>'. \| [modify] Google Calendar event id to modify. For a recurring-series instance, the id has shape '<seriesId>_<startTs>'. \| [delete] The Google Calendar event ID to delete (string) |
50
50
  | `--recurrence` | No | [create] Recurrence rules (e.g., ['RRULE:FREQ=DAILY;COUNT=2']) \| [modify] New recurrence rules (e.g. ['RRULE:FREQ=WEEKLY;BYDAY=MO']). Only honored when scope=series. (array) |
51
51
  | `--send_notifications` | No | [create] Whether to send email notifications to attendees \| [respond] Whether Google should notify the organizer of the response. Default true. \| [modify] Whether attendees get a notification of the change. Default true. (boolean) |
52
- | `--skip_confirmation` | No | [create] If true, create the event directly in Google Calendar instead of returning a local draft. Required when the caller has no UI to review/confirm a draft (e.g. sandbox agents shelling out via gsk). (boolean, default: `False`) |
53
- | `--auto_skip_confirmation` | No | [create] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. (boolean, default: `False`) |
54
52
  | `--is_all_day` | No | [create] Whether to create an all-day busy/block event. (boolean, default: `False`) |
55
53
  | `--all_day` | No | [create] Alias for is_all_day. (boolean, default: `False`) |
56
54
  | `--skip_conflict_check` | No | [create] Set true ONLY after the user has explicitly confirmed they want to book despite a conflict/warning surfaced by a prior needs_confirmation result. Leave false (default) normally. (boolean, default: `False`) |
@@ -63,7 +61,7 @@ gsk google_calendar [options]
63
61
 
64
62
  ## Write Confirmation
65
63
 
66
- Confirmation-gated actions: `delete` (plus write methods through `api` where present). A CLI with client-side confirmation prompts `[y/N]` (or honors `--yes`) and executes in a single call; the rest of this section is the double-call contract for older CLIs. Completing that confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
64
+ Confirmation-gated actions: `create`, `delete`. The CLI shows a preview and asks `[y/N]` on stderr before the single server call; pass `--yes` (`-y`) for unattended runs. `--no-input` (or `--args-file -`, which consumes stdin) makes a gated call exit 2 with no server call instead of hanging. Never re-run a command to 'confirm' it — every call is a real execution. `--skip_confirmation true` / `--auto_skip_confirmation` are deprecated on this CLI (still accepted, warn on stderr): use `--yes`.
67
65
 
68
66
  ## See Also
69
67
 
@@ -30,15 +30,13 @@ gsk google_chat [options]
30
30
 
31
31
  | Flag | Required | Description |
32
32
  |------|----------|-------------|
33
- | `<action>` (positional) | Yes | Action to perform. 'list_spaces': List spaces (rooms, group chats, and DMs); 'read': Read recent messages from a space; 'send': Send a message to a space (recipients see a Genspark app label next to the sender's name — Google adds it, it cannot be hidden). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'upload': Upload a file (local path, file-wrapper URL, AI Drive path, or text content) to a space as a message attachment. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'update': Edit the text of one of your own messages. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'delete': Delete one of your own messages. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'react': Add or remove an emoji reaction on a message (unicode emoji; remove affects your own reaction only). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'list_members': List all members of a space (full roster) (string, one of: list_spaces, read, send, upload, update, delete, react, list_members) |
33
+ | `<action>` (positional) | Yes | Action to perform. 'list_spaces': List spaces (rooms, group chats, and DMs); 'read': Read recent messages from a space; 'send': Send a message to a space (recipients see a Genspark app label next to the sender's name — Google adds it, it cannot be hidden). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'upload': Upload a file (local path, file-wrapper URL, AI Drive path, or text content) to a space as a message attachment. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'update': Edit the text of one of your own messages. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'delete': Delete one of your own messages. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'react': Add or remove an emoji reaction on a message (unicode emoji; remove affects your own reaction only). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'list_members': List all members of a space (full roster) (string, one of: list_spaces, read, send, upload, update, delete, react, list_members) |
34
34
  | `--search_query` | No | [list_spaces] Optional case-insensitive filter on the space display name. (string) |
35
35
  | `--limit` | No | [list_spaces] Maximum number of spaces to return (1-200). Default: 50 \| [read] Maximum number of messages to return (1-100). Default: 25 (integer) |
36
36
  | `--space` | No | [read] Space resource name, e.g. 'spaces/AAAAxxxx'. \| [send] Space resource name, e.g. 'spaces/AAAAxxxx'. \| [upload] Space resource name, e.g. 'spaces/AAAAxxxx'. \| [list_members] Space resource name, e.g. 'spaces/AAAAxxxx'. (string) |
37
37
  | `--thread` | No | [read] Optional thread resource name (e.g. 'spaces/AAAAxxxx/threads/yyyy') to return only that thread's messages — e.g. to verify where a threaded reply landed. \| [send] Optional thread resource name (e.g. 'spaces/AAAAxxxx/threads/yyyy') to reply in a thread. Omit to start a new thread. If the thread cannot be replied to, the API starts a NEW thread instead — the response then carries 'thread_fallback': true and 'actual_thread' (set 'strict_thread' to fail instead). \| [upload] Optional thread resource name (e.g. 'spaces/AAAAxxxx/threads/yyyy') to attach in a thread. Omit to start a new thread. If the thread cannot be replied to, the API starts a NEW thread instead — the response then carries 'thread_fallback': true and 'actual_thread' (set 'strict_thread' to fail instead). (string) |
38
38
  | `--message` | No | [send] The message text to send. Supports Google Chat formatting. To @mention someone, embed '<users/{user_id}>' in the text — a plain '@Name' renders as literal text and notifies nobody. User ids come from google_chat_list_members ('user' field) or the 'mentions' field on read messages; '<users/all>' mentions the whole space. 'content' is accepted as an alias for this parameter. \| [upload] Optional caption text sent with the attachment. \| [update] Message resource name to edit, e.g. 'spaces/AAAAxxxx/messages/yyyy'. \| [delete] Message resource name to delete, e.g. 'spaces/AAAAxxxx/messages/yyyy'. \| [react] Message resource name, e.g. 'spaces/AAAAxxxx/messages/yyyy'. (string) |
39
39
  | `--strict_thread` | No | [send] If true and 'thread' is set, fail with an error when the thread cannot be replied to instead of falling back to a new thread. Default: false. \| [upload] If true and 'thread' is set, fail with an error when the thread cannot be replied to instead of falling back to a new thread. Default: false. (boolean, default: `False`) |
40
- | `--skip_confirmation` | No | [send] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [upload] If true, skip user confirmation and send immediately. Default is false. \| [update] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [delete] If true, skip user confirmation and delete immediately. Default is false (require confirmation before deleting). \| [react] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). (boolean, default: `False`) |
41
- | `--auto_skip_confirmation` | No | [send] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [upload] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. \| [update] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [delete] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [react] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. (boolean, default: `False`) |
42
40
  | `--file_path` | No | [upload] Path or URL of the file to upload. Accepts (1) a local server filesystem path; (2) a Genspark file-wrapper URL (``https://www.genspark.ai/api/files/s/<code>``); or (3) an AI Drive path (``/mnt/aidrive/...``, ``/aidrive/...``, ``aidrive://...``). Mutually exclusive with ``content``. (string) |
43
41
  | `--content` | No | [upload] Text content to upload as the file body (UTF-8). Requires ``file_name``. Mutually exclusive with ``file_path``. (string) |
44
42
  | `--file_name` | No | [upload] File name including extension (e.g. 'report.pdf'). Required with ``content``; defaults to the source basename with ``file_path``. (string) |
@@ -48,7 +46,7 @@ gsk google_chat [options]
48
46
 
49
47
  ## Write Confirmation
50
48
 
51
- Confirmation-gated actions: `send`, `upload`, `update`, `delete`, `react` (plus write methods through `api` where present). A CLI with client-side confirmation prompts `[y/N]` (or honors `--yes`) and executes in a single call; the rest of this section is the double-call contract for older CLIs. Completing that confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
49
+ Confirmation-gated actions: `send`, `upload`, `update`, `delete`, `react`. The CLI shows a preview and asks `[y/N]` on stderr before the single server call; pass `--yes` (`-y`) for unattended runs. `--no-input` (or `--args-file -`, which consumes stdin) makes a gated call exit 2 with no server call instead of hanging. Never re-run a command to 'confirm' it — every call is a real execution. `--skip_confirmation true` / `--auto_skip_confirmation` are deprecated on this CLI (still accepted, warn on stderr): use `--yes`.
52
50
 
53
51
  ## See Also
54
52
 
@@ -30,7 +30,7 @@ gsk gdrive [options]
30
30
 
31
31
  | Flag | Required | Description |
32
32
  |------|----------|-------------|
33
- | `<action>` (positional) | Yes | Action to perform. 'list': List files directly inside a Google Drive folder; 'search': Search files by name, type, or owner; 'read': Read and extract content from a file; 'upload': Upload a new file to Google Drive, or overwrite an existing one in place by passing its file_id (the ID, link, and shares are preserved); 'share': Grant access to a file (specific emails or anyone-with-link; app-created/opened files only under drive.file). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes. (string, one of: list, search, read, upload, share) |
33
+ | `<action>` (positional) | Yes | Action to perform. 'list': List files directly inside a Google Drive folder; 'search': Search files by name, type, or owner; 'read': Read and extract content from a file; 'upload': Upload a new file to Google Drive, or overwrite an existing one in place by passing its file_id (the ID, link, and shares are preserved); 'share': Grant access to a file (specific emails or anyone-with-link; app-created/opened files only under drive.file). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). (string, one of: list, search, read, upload, share) |
34
34
  | `--folder_id` | No | [list] Google Drive folder ID or folder URL. \| [search] Search within a specific folder for 'search' action. Accepts a folder ID or Google Drive folder URL. \| [upload] Google Drive folder ID to upload to. Optional, uploads to root if not specified. Ignored when 'file_id' is set. (string) |
35
35
  | `--folder_url` | No | [list] Google Drive folder URL. \| [search] Google Drive folder URL to list/search within. (string) |
36
36
  | `--mime_type` | No | [list] Optional MIME type filter. \| [search] Filter by MIME type for 'search' (e.g., 'application/pdf'). \| [upload] The MIME type of the file (optional, will be auto-detected from file_name extension). Examples: 'text/plain', 'text/csv', 'application/json', 'image/png'. (string) |
@@ -59,7 +59,9 @@ Parameters that accept URLs (`--folder_url`, `--file_url`) also accept local fil
59
59
 
60
60
  ## Write Confirmation
61
61
 
62
- Confirmation-gated actions: `share` (plus write methods through `api` where present). A CLI with client-side confirmation prompts `[y/N]` (or honors `--yes`) and executes in a single call; the rest of this section is the double-call contract for older CLIs. Completing that confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
62
+ Confirmation-gated actions: `share`. The CLI shows a preview and asks `[y/N]` on stderr before the single server call; pass `--yes` (`-y`) for unattended runs. `--no-input` (or `--args-file -`, which consumes stdin) makes a gated call exit 2 with no server call instead of hanging. Never re-run a command to 'confirm' it — every call is a real execution. `--skip_confirmation true` / `--auto_skip_confirmation` are deprecated on this CLI (still accepted, warn on stderr): use `--yes`.
63
+
64
+ Interactive-only actions: `share` (the action excludes the skip params, e.g. Marketplace policy on Slack) — `--yes` is ignored and a real `[y/N]` answer is required.
63
65
 
64
66
  ## See Also
65
67
 
@@ -33,7 +33,7 @@ gsk teams [options]
33
33
 
34
34
  | Flag | Required | Description |
35
35
  |------|----------|-------------|
36
- | `<action>` (positional) | Yes | Action to perform. 'send': Send a message in Teams (reply_to_message_id replies in a channel thread or quotes a chat message). Auto-approved: executes on the FIRST call — no [y/N] prompt and no pending_confirmation step. Do NOT re-run the command; a second call performs the operation again (e.g. sends a duplicate message).; 'list_channels': List hosted and shared channels for an associated team; 'list_chats': List recent chats; 'read_chat': Read a chat's recent messages by chat_id; 'list_channel_messages': List root messages in a channel; one traversal is not a deletion snapshot; 'list_channel_replies': List replies to a channel message; one traversal is not a deletion snapshot; 'download_attachment': Download one attachment or inline hosted image from a message; returns a file URL; 'mark_chat_read': Mark a chat as read for the connected user (clears its unread badge; own read state only); 'api': Raw Graph call with the connected account, for resources the typed actions do not cover; GET immediate, writes held for confirmation. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'list_teams': List direct teams and shared-channel host teams; 'search': Search messages; 'search_users': Search for users; 'create_chat': Create a new chat; 'react': Emoji-react to a chat or channel message (or remove your reaction). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'upload': Share a file into a chat (uploads to the sender's OneDrive Teams folder, posts a file card). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'list_members': List ALL members of a team with roles and emails (full roster, internally paginated); 'create_team': Create a new team (you become owner) and optionally add members by email; 'delete_message': Soft-delete one of your own messages (chat, channel, or threaded reply). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes.; 'update_message': Edit the body of one of your own messages (chat, channel, or threaded reply). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes. (string, one of: send, list_channels, list_chats, read_chat, list_channel_messages, list_channel_replies, download_attachment, mark_chat_read, api, list_teams, search, search_users, create_chat, react, upload, list_members, create_team, delete_message, update_message) |
36
+ | `<action>` (positional) | Yes | Action to perform. 'send': Send a message in Teams (reply_to_message_id replies in a channel thread or quotes a chat message). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'list_channels': List hosted and shared channels for an associated team; 'list_chats': List recent chats; 'read_chat': Read a chat's recent messages by chat_id; 'list_channel_messages': List root messages in a channel; one traversal is not a deletion snapshot; 'list_channel_replies': List replies to a channel message; one traversal is not a deletion snapshot; 'download_attachment': Download one attachment or inline hosted image from a message; returns a file URL; 'mark_chat_read': Mark a chat as read for the connected user (clears its unread badge; own read state only); 'api': Raw Graph call with the connected account, for resources the typed actions do not cover; GET immediate, writes held for confirmation. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Not confirmation-gated when method is GET (also the default when method is omitted): those values run immediately (no prompt, no pending_confirmation step).; 'list_teams': List direct teams and shared-channel host teams; 'search': Search messages; 'search_users': Search for users; 'create_chat': Create a new chat; 'react': Emoji-react to a chat or channel message (or remove your reaction). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'upload': Share a file into a chat (uploads to the sender's OneDrive Teams folder, posts a file card). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'list_members': List ALL members of a team with roles and emails (full roster, internally paginated); 'create_team': Create a new team (you become owner) and optionally add members by email; 'delete_message': Soft-delete one of your own messages (chat, channel, or threaded reply). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'update_message': Edit the body of one of your own messages (chat, channel, or threaded reply). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). (string, one of: send, list_channels, list_chats, read_chat, list_channel_messages, list_channel_replies, download_attachment, mark_chat_read, api, list_teams, search, search_users, create_chat, react, upload, list_members, create_team, delete_message, update_message) |
37
37
  | `--content` | No | [send] The message content to send. Accepts either Markdown or HTML. Markdown (e.g. '## Heading', '**bold**', '- item', tables) is automatically rendered to formatted HTML. You may also pass raw HTML directly: <a href='URL'>text</a> for links, <b>text</b> for bold, <i>text</i> for italic, <br> for line breaks, and other standard HTML tags. INLINE IMAGES are supported: embed <img src="data:image/png;base64,..."> (any image/* data URI) and the bytes are automatically relocated into Microsoft Graph hostedContents so the image renders in the message — no manual Graph calls needed. 'message' is accepted as an alias for this parameter. How this text is rendered is governed by content_format; declare it explicitly when the text could be mistaken for markup (code, '#'-prefixed lines, '**'). \| [upload] Text content to upload as a file (UTF-8). Provide exactly one of 'content' or 'file_path'. \| [update_message] New message body that REPLACES the current one. Accepts Markdown, plain text, or HTML; rendering is governed by content_format. Inline data-URI images are not supported on edit; use send for new images. 'message' is accepted as an alias for this parameter. (string) |
38
38
  | `--content_format` | No | [send] Declares how 'content' should be rendered — the server cannot reliably guess (a Python comment and a Markdown heading are byte-identical). 'plain': send the text literally, nothing is interpreted as markup — use this for code snippets or any text containing '#', '**', '\|' etc. that must appear verbatim. 'markdown': always render Markdown to formatted HTML. 'html': send the content as authored HTML unchanged. 'auto' (default): legacy guessing — HTML-looking content passes through, anything else renders as Markdown. \| [update_message] Declares how 'content' should be rendered -- the server cannot reliably guess. 'plain': render the text literally, nothing is interpreted as markup. 'markdown': always render Markdown to formatted HTML. 'html': send the content as authored HTML unchanged. 'auto' (default): HTML-looking content passes through, anything else renders as Markdown. (string, one of: auto, plain, markdown, html, default: `auto`) |
39
39
  | `--chat_id` | No | [send] Optional chat ID to send the message to. If not specified or set to 'self', sends to yourself as a DM. Use chat IDs from microsoft_teams_search_messages results. \| [read_chat] The Teams chat ID (e.g. '19:...@thread.v2'). Required. \| [download_attachment] Chat ID ('19:…@thread.v2') for a chat message. Mutually exclusive with team_id/channel_id. \| [mark_chat_read] Chat ID ('19:…@thread.v2') to mark as read, from microsoft_teams_list_chats. \| [react] ID of the chat containing the message. Provide either chat_id, or team_id + channel_id for a channel message. \| [upload] Target chat ID (e.g. '19:…@thread.v2', from list_chats/search_users). \| [list_members] Chat ID ('19:…@thread.v2') to list a group chat's or DM's members instead of a team's. \| [delete_message] ID of the chat containing the message. Provide either chat_id, or team_id + channel_id for a channel message. \| [update_message] ID of the chat containing the message. Provide either chat_id, or team_id + channel_id for a channel message. (string) |
@@ -45,8 +45,6 @@ gsk teams [options]
45
45
  | `--mention_user_ids` | No | [send] List of user IDs (GUIDs) to @mention in the message. Use search_users to find user IDs first. The message content should include {mention_N} placeholders where N is the index (0-based), e.g., '{mention_0} thank you' will @mention the first user in the list. (array) |
46
46
  | `--mention_user_names` | No | [send] Display names for mentioned users, in same order as mention_user_ids. If not provided, will use user IDs as display names. (array) |
47
47
  | `--reply_to_message_id` | No | [send] Optional ID of an existing message to reply to. For team channels: posts this message as a threaded reply under that root message. For chats: renders a quoted block of the referenced message above your text (like the Teams client's Reply action). Message IDs come from microsoft_teams_read_chat / microsoft_teams_list_channel_messages. \| [download_attachment] For a channel reply: the ROOT message ID the reply belongs to. (string) |
48
- | `--skip_confirmation` | No | [send] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [api] Skip the user-confirmation step for a write method. Only honored right after this tool returned pending_confirmation and the user confirmed. Default: false. \| [react] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [upload] If true, skip user confirmation and upload immediately. Default is false (require confirmation before uploading). \| [delete_message] If true, skip user confirmation and delete immediately. Default is false (require confirmation before deleting). \| [update_message] If true, skip user confirmation and apply the edit immediately. Default is false (require confirmation before editing). (boolean, default: `False`) |
49
- | `--auto_skip_confirmation` | No | [send] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [api] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [react] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [upload] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [delete_message] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [update_message] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. (boolean, default: `False`) |
50
48
  | `--cursor` | No | [list_channels] Opaque next_cursor from the previous page. \| [list_chats] Pagination cursor returned in a previous response's ``next_cursor`` field. Pass it back verbatim to fetch the next page; omit on the first call. \| [read_chat] Pagination cursor from a previous response's ``next_cursor``; omit on the first call. \| [list_channel_messages] Opaque next_cursor from the previous page. \| [list_channel_replies] Opaque next_cursor from the previous page. \| [list_teams] Opaque next_cursor from the previous page. \| [search] Pagination cursor returned in a previous response's ``next_cursor`` field. Pass it back verbatim to fetch the next page; omit on the first call. Stop paging as soon as the returned hits satisfy your need. (string) |
51
49
  | `--topic` | No | [list_chats] Search for chats by topic/name (case-insensitive partial match). Use this to find a specific group chat by its name. Example: 'WorkflowTest' to find a chat with that topic. Filter is applied per-page; if no match on the current page, use ``next_cursor`` to keep searching. \| [create_chat] Topic/name for the group chat. Required for group chats (2+ members), ignored for 1:1 chats. (string) |
52
50
  | `--chat_type` | No | [list_chats] Filter by chat type. 'oneOnOne' for 1:1 chats, 'group' for group chats, 'meeting' for meeting chats, 'all' for all types. Default: 'all' (string, one of: oneOnOne, group, meeting, all) |
@@ -58,7 +56,7 @@ gsk teams [options]
58
56
  | `--attachment_id` | No | [download_attachment] Attachment ID from the message's attachments list — for file attachments with a contentUrl. (string) |
59
57
  | `--path` | No | [api] Graph resource path starting with '/', query string allowed, e.g. '/me/chats?$top=5'. Passed through verbatim — percent-encode segment values yourself. (string) |
60
58
  | `--graph_version` | No | [api] Graph API version. Default v1.0; 'beta' is an explicit opt-in. (string, one of: v1.0, beta) |
61
- | `--method` | No | [api] HTTP method. Default GET. Write methods are held for user confirmation before executing. (string, one of: GET, POST, PATCH, PUT, DELETE) |
59
+ | `--method` | No | [api] HTTP method. Default GET (omitting it runs immediately). Write methods are held for user confirmation before executing. (string, one of: GET, POST, PATCH, PUT, DELETE, default: `GET`) |
62
60
  | `--body` | No | [api] JSON request body for write methods (object or array, passed to Graph verbatim). Not allowed on GET. (string) |
63
61
  | `--query` | No | [search] The search query using KQL (Keyword Query Language). **Query Behavior**: • Spaces = AND: 'project meeting' finds messages with BOTH terms • OR operator: 'project OR meeting' finds messages with EITHER term • KQL modifiers: 'from:john', 'hasAttachment:true', 'IsRead:false' • Date filters: prefer the ``since``/``until`` arguments; inline date ops ('sent>=2026-02-01 sent<=2026-03-05', 'sent:2026-02-01..2026-03-05') are also honored — both bounds are enforced • Examples: 'urgent project', 'bug OR issue', 'from:alice budget', 'hasAttachment:true report' \| [search_users] Search query - can be a name, email, or partial match. Example: 'John', 'john@company.com', 'Smith' (string) |
64
62
  | `--unread_only` | No | [search] Set to true to search for unread messages only. Default is false. (boolean) |
@@ -80,9 +78,7 @@ gsk teams [options]
80
78
 
81
79
  ## Write Confirmation
82
80
 
83
- Confirmation-gated actions: `api`, `react`, `upload`, `delete_message`, `update_message` (plus write methods through `api` where present). A CLI with client-side confirmation prompts `[y/N]` (or honors `--yes`) and executes in a single call; the rest of this section is the double-call contract for older CLIs. Completing that confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
84
-
85
- Auto-approved actions: `send` — the server skips the confirmation gate, so the operation executes on the FIRST call with no `[y/N]` prompt and no `pending_confirmation` step. Do NOT re-run the command expecting a confirmation arc: a second call performs the operation again (e.g. sends a duplicate message).
81
+ Confirmation-gated actions: `send`, `api` (except `method=GET` or `method` omitted, which runs immediately), `react`, `upload`, `delete_message`, `update_message`. An action marked `(except <param>=<values>)` is gated only for the other values of that argument — the listed values run immediately with no prompt and no confirmation step. The CLI shows a preview and asks `[y/N]` on stderr before the single server call; pass `--yes` (`-y`) for unattended runs. `--no-input` (or `--args-file -`, which consumes stdin) makes a gated call exit 2 with no server call instead of hanging. Never re-run a command to 'confirm' it — every call is a real execution. `--skip_confirmation true` / `--auto_skip_confirmation` are deprecated on this CLI (still accepted, warn on stderr): use `--yes`.
86
82
 
87
83
  ## See Also
88
84
 
@@ -28,7 +28,7 @@ gsk onedrive [options]
28
28
 
29
29
  | Flag | Required | Description |
30
30
  |------|----------|-------------|
31
- | `<action>` (positional) | Yes | Action to perform. 'list': List files in a folder; 'search': Search files; 'read': Read and extract content from a file; 'upload': Upload a file (local path, file-wrapper URL, AI Drive path, or text content) to OneDrive; 'share': Create a sharing link (view/edit/embed; anonymous or organization scope) for a file or folder. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes. (string, one of: list, search, read, upload, share) |
31
+ | `<action>` (positional) | Yes | Action to perform. 'list': List files in a folder; 'search': Search files; 'read': Read and extract content from a file; 'upload': Upload a file (local path, file-wrapper URL, AI Drive path, or text content) to OneDrive; 'share': Create a sharing link (view/edit/embed; anonymous or organization scope) for a file or folder. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). (string, one of: list, search, read, upload, share) |
32
32
  | `--onedrive_url` | No | [list] A OneDrive URL to list files from. Can be a sharing link, folder link, or any OneDrive URL. (string) |
33
33
  | `--folder_id` | No | [list] The folder item ID to list contents of. Get folder IDs from previous onedrive_list_files or onedrive_search results. \| [upload] Target folder item ID (from onedrive_list_files or onedrive_search). If omitted, ``folder_path`` is used; if both are omitted, the upload goes to the OneDrive root. (string) |
34
34
  | `--folder_path` | No | [list] The folder path relative to OneDrive root. Example: 'Documents/Projects' to list files in that subfolder. \| [upload] Target folder path relative to the OneDrive root, e.g. 'Documents/Reports'. The folder must already exist. Ignored when ``folder_id`` is provided. (string) |
@@ -52,7 +52,9 @@ Parameters that accept URLs (`--onedrive_url`) also accept local file paths. The
52
52
 
53
53
  ## Write Confirmation
54
54
 
55
- Confirmation-gated actions: `share` (plus write methods through `api` where present). A CLI with client-side confirmation prompts `[y/N]` (or honors `--yes`) and executes in a single call; the rest of this section is the double-call contract for older CLIs. Completing that confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
55
+ Confirmation-gated actions: `share`. The CLI shows a preview and asks `[y/N]` on stderr before the single server call; pass `--yes` (`-y`) for unattended runs. `--no-input` (or `--args-file -`, which consumes stdin) makes a gated call exit 2 with no server call instead of hanging. Never re-run a command to 'confirm' it — every call is a real execution. `--skip_confirmation true` / `--auto_skip_confirmation` are deprecated on this CLI (still accepted, warn on stderr): use `--yes`.
56
+
57
+ Interactive-only actions: `share` (the action excludes the skip params, e.g. Marketplace policy on Slack) — `--yes` is ignored and a real `[y/N]` answer is required.
56
58
 
57
59
  ## See Also
58
60
 
@@ -29,7 +29,7 @@ gsk outlook_calendar [options]
29
29
 
30
30
  | Flag | Required | Description |
31
31
  |------|----------|-------------|
32
- | `<action>` (positional) | Yes | Action to perform. 'list': List upcoming calendar events. Returns at most 'limit' (default 20) events; the response sets truncated=true when more events exist in the window; 'free_busy': Query free/busy availability for people (any org member) in a time window (find open meeting slots); 'create': Create a new calendar event. By default this returns a LOCAL DRAFT only — nothing lands in the calendar until the user confirms it in the Genspark UI. Callers without a confirmation UI (e.g. gsk) must pass --skip_confirmation to create the event directly; 'respond': RSVP (accept / decline / tentative) to an existing invite. Supports --comment and --proposed_new_time (Outlook-only counter-proposal); 'modify': Modify (Graph PATCH /me/events/{id}) an existing event in place without delete+create; 'delete': Delete a calendar event. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). Older CLIs require --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, and re-running the identical command executes. (string, one of: list, free_busy, create, respond, modify, delete) |
32
+ | `<action>` (positional) | Yes | Action to perform. 'list': List upcoming calendar events. Returns at most 'limit' (default 20) events; the response sets truncated=true when more events exist in the window; 'free_busy': Query free/busy availability for people (any org member) in a time window (find open meeting slots); 'create': Create a new calendar event. By default this returns a LOCAL DRAFT only — nothing lands in the calendar until the user confirms it in the Genspark UI. Callers without a confirmation UI (e.g. gsk) must confirm the create (gsk: `--yes`) to write the event directly. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'respond': RSVP (accept / decline / tentative) to an existing invite. Supports --comment and --proposed_new_time (Outlook-only counter-proposal); 'modify': Modify (Graph PATCH /me/events/{id}) an existing event in place without delete+create; 'delete': Delete a calendar event. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes). (string, one of: list, free_busy, create, respond, modify, delete) |
33
33
  | `--filter_query` | No | [list] Text to filter calendar events by subject. Empty for listing all events in the time range. (string) |
34
34
  | `--time_min` | No | [list] Optional. Start time for the calendar view (ISO 8601 timestamp). Defaults to 30 days ago. (string) |
35
35
  | `--time_max` | No | [list] Optional. End time for the calendar view (ISO 8601 timestamp). Defaults to 60 days from now. (string) |
@@ -53,8 +53,6 @@ gsk outlook_calendar [options]
53
53
  | `--importance` | No | [create] Event importance (low, normal, high) \| [modify] Event importance: low / normal / high. (string) |
54
54
  | `--sensitivity` | No | [create] Event sensitivity (normal, personal, private, confidential) \| [modify] Event sensitivity: normal / personal / private / confidential. (string) |
55
55
  | `--show_as` | No | [create] Show as status (free, tentative, busy, oof, workingElsewhere, unknown) \| [modify] Show-as status: free / tentative / busy / oof / workingElsewhere / unknown. (string) |
56
- | `--skip_confirmation` | No | [create] If true, create the event directly in Outlook Calendar instead of returning a local draft. Required when the caller has no UI to review/confirm a draft (e.g. sandbox agents shelling out via gsk). (boolean, default: `False`) |
57
- | `--auto_skip_confirmation` | No | [create] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. (boolean, default: `False`) |
58
56
  | `--is_all_day` | No | [create] Whether to create an all-day busy/block event. (boolean, default: `False`) |
59
57
  | `--all_day` | No | [create] Alias for is_all_day. (boolean, default: `False`) |
60
58
  | `--skip_conflict_check` | No | [create] Set true ONLY after the user has explicitly confirmed they want to book despite a conflict/warning surfaced by a prior needs_confirmation result. Leave false (default) normally. (boolean, default: `False`) |
@@ -69,7 +67,7 @@ gsk outlook_calendar [options]
69
67
 
70
68
  ## Write Confirmation
71
69
 
72
- Confirmation-gated actions: `delete` (plus write methods through `api` where present). A CLI with client-side confirmation prompts `[y/N]` (or honors `--yes`) and executes in a single call; the rest of this section is the double-call contract for older CLIs. Completing that confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
70
+ Confirmation-gated actions: `create`, `delete`. The CLI shows a preview and asks `[y/N]` on stderr before the single server call; pass `--yes` (`-y`) for unattended runs. `--no-input` (or `--args-file -`, which consumes stdin) makes a gated call exit 2 with no server call instead of hanging. Never re-run a command to 'confirm' it — every call is a real execution. `--skip_confirmation true` / `--auto_skip_confirmation` are deprecated on this CLI (still accepted, warn on stderr): use `--yes`.
73
71
 
74
72
  ## See Also
75
73