@genspark/cli 1.7.1 → 1.8.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.
@@ -44,7 +44,7 @@ gsk slides [options]
44
44
 
45
45
  ## Write Confirmation (double-call)
46
46
 
47
- Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. 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: 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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
47
+ Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the 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.
48
48
 
49
49
  ## See Also
50
50
 
@@ -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); '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; '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); 'upload': Share a file into a chat (uploads to the sender's OneDrive Teams folder, posts a file card); '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) (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) |
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: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; '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: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, 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: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, 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: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, 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: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, 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) |
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'. (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. (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. (string) |
@@ -80,7 +80,7 @@ gsk teams [options]
80
80
 
81
81
  ## Write Confirmation (double-call)
82
82
 
83
- Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. 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: 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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
83
+ Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the 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
84
 
85
85
  ## See Also
86
86
 
@@ -38,7 +38,7 @@ gsk notion [options]
38
38
 
39
39
  ## Write Confirmation (double-call)
40
40
 
41
- Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. 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: 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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
41
+ Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the 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.
42
42
 
43
43
  ## See Also
44
44
 
@@ -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 (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: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes. (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,7 @@ Parameters that accept URLs (`--onedrive_url`) also accept local file paths. The
52
52
 
53
53
  ## Write Confirmation (double-call)
54
54
 
55
- Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. 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: 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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
55
+ Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the 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.
56
56
 
57
57
  ## See Also
58
58
 
@@ -69,7 +69,7 @@ gsk outlook_calendar [options]
69
69
 
70
70
  ## Write Confirmation (double-call)
71
71
 
72
- Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. 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: 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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
72
+ Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the 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.
73
73
 
74
74
  ## See Also
75
75
 
@@ -33,7 +33,7 @@ gsk outlook [options]
33
33
 
34
34
  | Flag | Required | Description |
35
35
  |------|----------|-------------|
36
- | `<action>` (positional) | Yes | Action to perform. 'search': Search emails by query; 'read': Read a specific email by ID; 'list_folders': List structured Outlook mail folders; 'list_emails': List structured emails with explicit body coverage; 'list_email_changes': List folder-scoped email upserts and tombstones with body coverage using a delta cursor; 'send': Compose and send an email; 'draft': Save an email to the Drafts folder without sending; 'reply': Reply to an existing email; 'reply_draft': Create a reply draft without sending; 'forward': Forward an email to new recipients; 'delete': Delete an email; 'archive': Archive an email; 'move': Move an email to a different folder; 'mark_as_read': Mark an email as read or unread; 'add_category': Add a category to an email; 'remove_category': Remove a category from an email; 'get_attachment': Download an email attachment; 'group_list': List Microsoft 365 groups; 'group_search': Search group emails; 'group_read': Read a group email; 'group_reply': Reply to a group email (string, one of: search, read, list_folders, list_emails, list_email_changes, send, draft, reply, reply_draft, forward, delete, archive, move, mark_as_read, add_category, remove_category, get_attachment, group_list, group_search, group_read, group_reply) |
36
+ | `<action>` (positional) | Yes | Action to perform. 'search': Search emails by query; 'read': Read a specific email by ID; 'list_folders': List structured Outlook mail folders; 'list_emails': List structured emails with explicit body coverage; 'list_email_changes': List folder-scoped email upserts and tombstones with body coverage using a delta cursor; 'send': Compose and send an email. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'draft': Save an email to the Drafts folder without sending; 'reply': Reply to an existing email. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'reply_draft': Create a reply draft without sending; 'forward': Forward an email to new recipients. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'delete': Delete an email. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'archive': Archive an email; 'move': Move an email to a different folder. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'mark_as_read': Mark an email as read or unread; 'add_category': Add a category to an email; 'remove_category': Remove a category from an email; 'get_attachment': Download an email attachment; 'group_list': List Microsoft 365 groups; 'group_search': Search group emails; 'group_read': Read a group email; 'group_reply': Reply to a group email (string, one of: search, read, list_folders, list_emails, list_email_changes, send, draft, reply, reply_draft, forward, delete, archive, move, mark_as_read, add_category, remove_category, get_attachment, group_list, group_search, group_read, group_reply) |
37
37
  | `--queryString` | No | [search] The search query using KQL (Keyword Query Language). Examples:\n- Simple: 'project meeting'\n- From Sender: 'from:boss@example.com'\n- With Subject: 'subject:"Weekly Report"'\n- Unread Emails: 'isRead=false'\n- Has Attachments: 'hasAttachments=true'\n- Cc Recipient: 'cc:user@example.com'\n- Important: 'importance:high'\n- Complex: 'from:admin@co.com AND (subject:urgent OR body:critical)'\nNote: Use after_date/before_date params for date filtering (recommended), or use KQL syntax like 'received:2024-06-01..2024-06-30' in queryString. (string) |
38
38
  | `--after_date` | No | [search] Filter emails received on or after this date (inclusive). Format: YYYY-MM-DD (e.g., '2024-01-01'). Works for both enterprise and personal accounts. (string) |
39
39
  | `--before_date` | No | [search] Filter emails received before this date (exclusive). Format: YYYY-MM-DD (e.g., '2024-01-31'). Works for both enterprise and personal accounts. (string) |
@@ -67,6 +67,8 @@ gsk outlook [options]
67
67
  | `--content_type` | No | [send] Content type of the body. Default: text/html (recommended) **CRITICAL**: body field format MUST match this parameter: - 'text/plain': body should be plain text - 'text/html': body MUST be valid HTML (not Markdown) Always convert Markdown to HTML before passing to this tool. \| [reply] Content type of the reply body. Default: text/html (recommended) **CRITICAL**: body field format MUST match this parameter: - 'text/plain': body should be plain text - 'text/html': body MUST be valid HTML (not Markdown) Always convert Markdown to HTML before passing to this tool. \| [forward] Content type of the body. Default: text/html \| [group_reply] The format of the content. Use 'text/plain' for plain text or 'text/html' for HTML content. Default is 'text/plain'. (string, one of: text/plain, text/html) |
68
68
  | `--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`) |
69
69
  | `--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`) |
70
+ | `--client_send_id` | No | [send] Optional stable idempotency key. Normally generated automatically for scheduled and interactive sends. (string) |
71
+ | `--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`) |
70
72
  | `--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). \| [reply_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). \| [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). \| [group_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). (array) |
71
73
  | `--body_type` | No | [draft] Body format: 'html' (default) or 'text'. (string) |
72
74
  | `--from_address` | No | [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. (string) |
@@ -96,7 +98,7 @@ gsk outlook [options]
96
98
 
97
99
  ## Write Confirmation (double-call)
98
100
 
99
- Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. 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: 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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
101
+ Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the 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.
100
102
 
101
103
  ## See Also
102
104
 
@@ -57,7 +57,7 @@ Parameters that accept URLs (`--sharepoint_url`) also accept local file paths. T
57
57
 
58
58
  ## Write Confirmation (double-call)
59
59
 
60
- Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. 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: 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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
60
+ Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the 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.
61
61
 
62
62
  ## See Also
63
63
 
@@ -29,7 +29,7 @@ gsk slack [options]
29
29
 
30
30
  | Flag | Required | Description |
31
31
  |------|----------|-------------|
32
- | `<action>` (positional) | Yes | Action to perform. 'send': Send a message to a channel or user; 'search': Search messages by keyword; 'read': Read recent message history of a channel (or one thread); 'lookup': Look up users, channels, or groups; 'react': Emoji-react to a message (or remove your reaction); 'invite': Invite workspace members into a channel; 'upload': Upload a file into a channel, group, or DM; 'update': Edit one of the user's own messages; 'delete': Delete one of the user's own messages; 'permalink': Get the permanent link for a message; 'connect_invites': List pending Slack Connect shared-channel invites (workspace owner/admin only); 'connect_approve': Approve a pending Slack Connect shared-channel invite by invite ID (workspace owner/admin only); 'connect_decline': Decline a pending Slack Connect shared-channel invite by invite ID (workspace owner/admin only) (string, one of: send, search, read, lookup, react, invite, upload, update, delete, permalink, connect_invites, connect_approve, connect_decline) |
32
+ | `<action>` (positional) | Yes | Action to perform. 'send': Send a message to a channel or user. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'search': Search messages by keyword; 'read': Read recent message history of a channel (or one thread); 'lookup': Look up users, channels, or groups; 'react': Emoji-react to a message (or remove your reaction). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'invite': Invite workspace members into a channel. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'upload': Upload a file into a channel, group, or DM. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'update': Edit one of the user's own messages. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'delete': Delete one of the user's own messages. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'permalink': Get the permanent link for a message; 'connect_invites': List pending Slack Connect shared-channel invites (workspace owner/admin only); 'connect_approve': Approve a pending Slack Connect shared-channel invite by invite ID (workspace owner/admin only). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'connect_decline': Decline a pending Slack Connect shared-channel invite by invite ID (workspace owner/admin only). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes. (string, one of: send, search, read, lookup, react, invite, upload, update, delete, permalink, connect_invites, connect_approve, connect_decline) |
33
33
  | `--message` | No | [send] The message content to send. Supports Slack markdown formatting. To @mention someone, embed '<@USER_ID>' (e.g. '<@U01234567>') in the text — a plain '@Name' renders as literal text and notifies nobody. User IDs come from the lookup action. 'content' is accepted as an alias for this parameter. (string) |
34
34
  | `--recipient` | No | [send] Optional recipient: 'self' (default), channel ID (e.g., 'C01234567'), or user ID (e.g., 'U01234567'). If not specified, sends to yourself. (string) |
35
35
  | `--title` | No | [send] Optional title for the message. If provided, creates a rich formatted message with a header. \| [upload] Optional title shown on the Slack file card. Defaults to the file name. (string) |
@@ -61,7 +61,7 @@ gsk slack [options]
61
61
 
62
62
  ## Write Confirmation (double-call)
63
63
 
64
- Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. 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: 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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
64
+ Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the 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.
65
65
 
66
66
  ## See Also
67
67