@inboxapi/cli 0.2.25 → 0.3.1

package/README.md

@@ -185,7 +185,7 @@ inboxapi get-email "<message-id>"
 ### `search-emails`
 
 ```bash
-inboxapi search-emails --query "invoice" --limit 10
+inboxapi search-emails --subject "invoice" --limit 10
 ```
 
 ### `get-attachment`

package/claude/hooks/email-activity-logger.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 // InboxAPI Activity Logger — PostToolUse hook
-// Logs all InboxAPI MCP tool usage to .claude/inboxapi-activity.log
+// Logs InboxAPI tool usage (MCP tool calls and CLI via Bash) to .claude/inboxapi-activity.log
 // Always exits 0 (non-blocking)
 
 const fs = require("fs");
@@ -19,13 +19,25 @@ function main() {
   const toolInput = data.tool_input || {};
   const cwd = data.cwd || process.cwd();
 
-  // Only log inboxapi tools
-  if (!toolName.includes("inboxapi")) {
+  // Only log inboxapi tools (MCP or CLI via Bash)
+  let shortName;
+  if (toolName === "Bash") {
+    const cmd = (toolInput.command || "");
+    if (!cmd.includes("inboxapi")) {
+      process.exit(0);
+    }
+    // Extract subcommand: first non-flag arg after the binary name (skips global options like --human)
+    const parts = cmd.split(/\s+/);
+    const idx = parts.findIndex(p => p === "inboxapi" || p.endsWith("/inboxapi") || p === "@inboxapi/cli");
+    const subcommand = idx > -1 ? parts.slice(idx + 1).find(p => !p.startsWith("-")) : undefined;
+    shortName = subcommand || "unknown-cli-cmd";
+  } else if (toolName.includes("inboxapi")) {
+    shortName = toolName.replace("mcp__inboxapi__", "");
+  } else {
     process.exit(0);
   }
 
   const timestamp = new Date().toISOString();
-  const shortName = toolName.replace("mcp__inboxapi__", "");
 
   // Build a concise log entry (logs identifiers and lengths, not email content)
   let details = "";

package/claude/hooks/email-send-guard.js

@@ -17,25 +17,51 @@ function main() {
   const toolName = data.tool_name || "";
   const toolInput = data.tool_input || {};
 
-  // Only inspect send-related tools
-  if (
-    !toolName.includes("send_email") &&
-    !toolName.includes("send_reply") &&
-    !toolName.includes("forward_email")
-  ) {
-    process.exit(0);
-  }
+  let toDisplay, subject, body, action;
+
+  if (toolName === "Bash") {
+    // Check if this is an inboxapi CLI send command
+    const cmd = (toolInput.command || "");
+    if (!cmd.includes("inboxapi")) {
+      process.exit(0);
+    }
+    const isSend = cmd.includes("send-email");
+    const isReply = cmd.includes("send-reply");
+    const isForward = cmd.includes("forward-email");
+    if (!isSend && !isReply && !isForward) {
+      process.exit(0);
+    }
 
-  const rawTo = toolInput.to || toolInput.recipient || "(unknown)";
-  const toList = Array.isArray(rawTo) ? rawTo : [rawTo];
-  const toDisplay = toList.join(", ");
-  const subject = toolInput.subject || "(no subject)";
-  const body = toolInput.body || toolInput.message || "";
-  const action = toolName.includes("forward")
-    ? "FORWARD"
-    : toolName.includes("reply")
-      ? "REPLY"
-      : "SEND";
+    // Best-effort extraction from CLI flags
+    // Captures: "quoted", 'quoted', or unquoted value until next --flag or end of string
+    const toMatch = cmd.match(/--to(?:=|\s+)(?:"([^"]+)"|'([^']+)'|(.+?)(?=\s+--|$))/);
+    toDisplay = (toMatch && (toMatch[1] || toMatch[2] || toMatch[3] || "").trim()) || "(unknown)";
+    const subjectMatch = cmd.match(/--subject(?:=|\s+)(?:"([^"]+)"|'([^']+)'|(.+?)(?=\s+--|$))/);
+    subject = (subjectMatch && (subjectMatch[1] || subjectMatch[2] || subjectMatch[3] || "").trim()) || "(no subject)";
+    const bodyMatch = cmd.match(/--body(?:=|\s+)(?:"([^"]+)"|'([^']+)'|(.+?)(?=\s+--|$))/);
+    body = (bodyMatch && (bodyMatch[1] || bodyMatch[2] || bodyMatch[3] || "").trim()) || "";
+    action = isForward ? "FORWARD" : isReply ? "REPLY" : "SEND";
+  } else {
+    // MCP tool call path (existing logic)
+    if (
+      !toolName.includes("send_email") &&
+      !toolName.includes("send_reply") &&
+      !toolName.includes("forward_email")
+    ) {
+      process.exit(0);
+    }
+
+    const rawTo = toolInput.to || toolInput.recipient || "(unknown)";
+    const toList = Array.isArray(rawTo) ? rawTo : [rawTo];
+    toDisplay = toList.join(", ");
+    subject = toolInput.subject || "(no subject)";
+    body = toolInput.body || toolInput.message || "";
+    action = toolName.includes("forward")
+      ? "FORWARD"
+      : toolName.includes("reply")
+        ? "REPLY"
+        : "SEND";
+  }
 
   // Log details to stderr so the user sees them in the Claude Code UI
   process.stderr.write(`\n[InboxAPI Send Guard] ${action}\n`);
@@ -48,9 +74,7 @@ function main() {
   process.stderr.write("\n");
 
   // Check for self-send (common AI agent mistake)
-  const hasInboxApiRecipient = toList.some(
-    (addr) => typeof addr === "string" && (addr.includes("@inboxapi.ai") || addr.includes("@inboxapi.com")),
-  );
+  const hasInboxApiRecipient = toDisplay.includes("@inboxapi.ai") || toDisplay.includes("@inboxapi.com");
   if (hasInboxApiRecipient) {
     process.stderr.write(
       `  [WARNING] Recipient is an @inboxapi address. Did you mean to send to an external address?\n\n`,

package/claude/skills/check-inbox/SKILL.md

@@ -11,10 +11,9 @@ Fetch and display a summary of recent emails from the user's InboxAPI inbox.
 
 ## Steps
 
-1. Call the `mcp__inboxapi__whoami` tool to identify the current account and email address
-2. Call `mcp__inboxapi__get_email_count` to show the total number of emails
-3. Call `mcp__inboxapi__get_emails` with:
-   - `limit`: Use `$ARGUMENTS` if provided, otherwise default to `20`
+1. Run: `npx -y @inboxapi/cli whoami` to identify the current account and email address
+2. Run: `npx -y @inboxapi/cli get-email-count` to show the total number of emails
+3. Run: `npx -y @inboxapi/cli get-emails --limit <N>` where `<N>` is `$ARGUMENTS` if provided, otherwise `20`
 4. Present results in a formatted table with columns:
    - **From** — sender name or address
    - **Subject** — email subject line (truncated to 60 chars)
@@ -35,5 +34,6 @@ If the inbox is empty, display: "Your inbox is empty. Your email address is <ema
 
 ## Notes
 
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
 - Do NOT read full email bodies — only show the summary list
-- If the user asks to read a specific email after seeing the list, use `mcp__inboxapi__get_email` with the email ID
+- If the user asks to read a specific email after seeing the list, run `npx -y @inboxapi/cli get-email "<message-id>"` with the email ID

package/claude/skills/compose/SKILL.md

@@ -12,11 +12,11 @@ Guide the user through composing and sending an email safely.
 
 ## Steps
 
-1. **Identify sender**: Call `mcp__inboxapi__whoami` to get the current account email address
+1. **Identify sender**: Run: `npx -y @inboxapi/cli whoami` to get the current account email address
 
 2. **Resolve recipient**:
    - If `$ARGUMENTS` is provided, use it as the recipient hint
-   - Call `mcp__inboxapi__get_addressbook` to check for matching contacts
+   - Run: `npx -y @inboxapi/cli get-addressbook` to check for matching contacts
    - If multiple matches found, ask the user to pick one
    - If no match, ask the user to confirm or provide the full email address
 
@@ -41,13 +41,17 @@ Guide the user through composing and sending an email safely.
 
 6. **Confirm**: Ask the user to confirm: "Send this email? (yes/no)"
 
-7. **Send**: Call `mcp__inboxapi__send_email` with `to`, `subject`, and `body`
+7. **Send**: Run: `npx -y @inboxapi/cli send-email --to "<recipient>" --subject "<subject>" --body "<body>"`
 
 8. **Confirm delivery**: Report the result to the user
 
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
+
 ## Rules
 
 - ALWAYS show a preview before sending
-- ALWAYS ask for explicit confirmation before calling send_email
+- ALWAYS ask for explicit confirmation before calling send-email
 - NEVER send an email without the user confirming
 - If the user cancels, acknowledge and do not send

package/claude/skills/email-digest/SKILL.md

@@ -13,13 +13,13 @@ Generate a structured digest of recent email activity.
 
 1. **Determine timeframe**: Use `$ARGUMENTS` if provided (e.g., "today", "this week", "last 3 days"), otherwise default to "last 24 hours"
 
-2. **Get account info**: Call `mcp__inboxapi__whoami` for the account email
+2. **Get account info**: Run: `npx -y @inboxapi/cli whoami` for the account email
 
-3. **Get total count**: Call `mcp__inboxapi__get_email_count` for inbox statistics
+3. **Get total count**: Run: `npx -y @inboxapi/cli get-email-count` for inbox statistics
 
-4. **Fetch recent emails**: Call `mcp__inboxapi__get_emails` with an appropriate limit (50 for digest)
+4. **Fetch recent emails**: Run: `npx -y @inboxapi/cli get-emails --limit 50`
 
-5. **Group by thread**: For threads with multiple emails, call `mcp__inboxapi__get_thread` to understand the conversation
+5. **Group by thread**: For threads with multiple emails, run `npx -y @inboxapi/cli get-thread --message-id "<message-id>"` to understand the conversation
 
 6. **Generate digest** with these sections:
 
@@ -53,6 +53,7 @@ Generate a structured digest of recent email activity.
 
 ## Notes
 
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
 - Focus on actionable insights, not raw data
 - Highlight emails that likely need a response
 - Keep the digest concise — summarize, don't reproduce full emails

package/claude/skills/email-forward/SKILL.md

@@ -13,8 +13,8 @@ Help the user forward an email to another recipient.
 ## Steps
 
 1. **Find the email to forward**:
-   - If `$ARGUMENTS` looks like an email ID, call `mcp__inboxapi__get_email` directly
-   - Otherwise, call `mcp__inboxapi__search_emails` with the argument
+   - Try `npx -y @inboxapi/cli get-email "$ARGUMENTS"` first — if it succeeds, use that email
+   - If it fails (e.g., not a valid message ID), fall back to `npx -y @inboxapi/cli search-emails --subject "<query>"` with the argument
    - If multiple results, show them and ask the user to pick one
 
 2. **Show email content**: Display the email being forwarded:
@@ -29,7 +29,7 @@ Help the user forward an email to another recipient.
 
 3. **Resolve recipient**:
    - Ask "Who do you want to forward this to?"
-   - Call `mcp__inboxapi__get_addressbook` to check for matching contacts
+   - Run: `npx -y @inboxapi/cli get-addressbook` to check for matching contacts
    - Confirm the recipient email address
 
 4. **Optional message**: Ask "Add a message? (or press enter to skip)"
@@ -44,7 +44,11 @@ Help the user forward an email to another recipient.
 
 6. **Confirm**: Ask "Forward this email? (yes/no)"
 
-7. **Send**: Call `mcp__inboxapi__forward_email` with the email ID, recipient, and optional message
+7. **Send**: Run: `npx -y @inboxapi/cli forward-email --message-id "<id>" --to "<recipient>"` (add `--note "<message>"` if provided)
+
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
 
 ## Rules
 

package/claude/skills/email-reply/SKILL.md

@@ -13,11 +13,11 @@ Help the user reply to an email with full thread context.
 ## Steps
 
 1. **Find the email**:
-   - If `$ARGUMENTS` looks like an email ID (alphanumeric string), call `mcp__inboxapi__get_email` directly
-   - Otherwise, call `mcp__inboxapi__search_emails` with the argument as subject/keyword
+   - Try `npx -y @inboxapi/cli get-email "$ARGUMENTS"` first — if it succeeds, use that email
+   - If it fails (e.g., not a valid message ID), fall back to `npx -y @inboxapi/cli search-emails --subject "<query>"` with the argument as subject/keyword
    - If multiple results, present them and ask the user to pick one
 
-2. **Load thread context**: Call `mcp__inboxapi__get_thread` with the email's thread ID to show the full conversation
+2. **Load thread context**: Run: `npx -y @inboxapi/cli get-thread --message-id "<message-id>"` with the email's message ID to show the full conversation
 
 3. **Display thread**: Show the conversation history in chronological order:
    ```
@@ -45,7 +45,11 @@ Help the user reply to an email with full thread context.
 
 6. **Confirm**: Ask "Send this reply? (yes/no)"
 
-7. **Send**: Call `mcp__inboxapi__send_reply` with the email ID and reply body
+7. **Send**: Run: `npx -y @inboxapi/cli send-reply --message-id "<id>" --body "<reply>"`
+
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
 
 ## Rules
 

package/claude/skills/email-search/SKILL.md

@@ -14,13 +14,13 @@ Search emails using natural language and present results clearly.
 1. Take the user's query from `$ARGUMENTS`
    - If no arguments provided, ask: "What are you looking for?"
 
-2. Translate the natural language query into a `mcp__inboxapi__search_emails` call:
-   - Extract sender hints (e.g., "from John" -> search by sender)
-   - Extract subject hints (e.g., "about invoices" -> search by subject)
-   - Extract date hints (e.g., "last week", "yesterday")
-   - Use the full query as the search term
+2. Translate the natural language query into CLI flags for `search-emails`:
+   - Extract sender hints (e.g., "from John" -> `--sender "John"`)
+   - Extract subject hints (e.g., "about invoices" -> `--subject "invoices"`)
+   - Extract date hints (e.g., "last week", "yesterday" -> `--since "..."`, `--until "..."`)
+   - Combine with `--limit` as needed
 
-3. Call `mcp__inboxapi__search_emails` with the interpreted parameters
+3. Run: `npx -y @inboxapi/cli search-emails` with the appropriate flags (`--sender "..."`, `--subject "..."`, `--since "..."`, `--until "..."`)
 
 4. Present results in a formatted table:
    ```
@@ -30,10 +30,14 @@ Search emails using natural language and present results clearly.
 
 5. After showing results, offer: "Would you like to read any of these emails? Provide the number."
 
-6. If the user picks one, call `mcp__inboxapi__get_email` with the email ID
+6. If the user picks one, run `npx -y @inboxapi/cli get-email "<message-id>"` with the email ID
 
 7. If no results, suggest alternative searches or broader terms
 
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
+
 ## Examples
 
 - `/email-search invoices from accounting` -> search for "invoices" filtered by sender containing "accounting"

package/claude/skills/setup-inboxapi/SKILL.md

@@ -31,7 +31,7 @@ Configure InboxAPI email tools for this Claude Code project.
 3. **Install skills**: Run `npx -y @inboxapi/cli setup-skills` to copy bundled skills and hooks into the project's `.claude/` directory
 
 4. **Verify credentials**:
-   - Call `mcp__inboxapi__whoami` to check if credentials are set up
+   - Run: `npx -y @inboxapi/cli whoami` to check if credentials are set up
    - If not authenticated, instruct the user: "Run `npx -y @inboxapi/cli login` in a terminal to authenticate"
 
 5. **Show summary**:
@@ -61,6 +61,7 @@ Configure InboxAPI email tools for this Claude Code project.
 
 ## Notes
 
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
 - This skill is safe to run multiple times — it won't duplicate entries or overwrite local edits
 - Existing `.mcp.json` entries, skill files, and hook files with local edits are preserved
 - `.claude/settings.json` is merged with new hook config (may be reformatted when hooks are updated)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inboxapi/cli",
-  "version": "0.2.25",
+  "version": "0.3.1",
   "description": "📧 Email for your AI 🤖",
   "main": "index.js",
   "bin": {
@@ -28,13 +28,10 @@
     "test": "cargo test"
   },
   "optionalDependencies": {
-    "@inboxapi/cli-darwin-arm64": "0.2.25",
-    "@inboxapi/cli-darwin-x64": "0.2.25",
-    "@inboxapi/cli-linux-arm64": "0.2.25",
-    "@inboxapi/cli-linux-x64": "0.2.25",
-    "@inboxapi/cli-win32-x64": "0.2.25"
-  },
-  "dependencies": {
-    "@inboxapi/cli": "^0.2.25"
+    "@inboxapi/cli-darwin-arm64": "0.3.1",
+    "@inboxapi/cli-darwin-x64": "0.3.1",
+    "@inboxapi/cli-linux-arm64": "0.3.1",
+    "@inboxapi/cli-linux-x64": "0.3.1",
+    "@inboxapi/cli-win32-x64": "0.3.1"
   }
 }