Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Voice Mode
  • Voice HUD
  • Web Search
  • Image Generation
  • Video Generation
  • Audio Generation
  • Transcription
  • Drive
  • Credentials
  • Sharing
  • Workspaces
  • Tasks
  • Memory
  • Agents
  • Subagents
  • Automations
  • Skills
  • idapt Code
  • Code Execution
  • Computers
  • Computer Use
  • Computer Assist · Soon
  • Containers · Soon
  • Cloud Computers
  • Local AI
  • AI Gateway
  • API & SDK
  • CLI
  • MCP
  • Tunnels
  • All features →
  • LLM cost calculator
  • Token counter
  • Context window checker
  • Can I run it
  • Model picker quiz
  • Savings finder
  • Video cost estimator
  • Text to speech cost
  • Transcription cost
  • API endpoint tester
  • All free tools →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Skills
  • Learn
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)
Help Center
🔔

Notifications from the CLI

Found this helpful? Share it:

The idapt notification commands read your inbox and send notifications to workspace members, all with your CLI credentials 🔔

Commands

CommandWhat it does
idapt notification listList notifications.
idapt notification preferencesGet notification preferences.
idapt notification update-preferencesBulk update notification preferences.
idapt notification configGet notification config (toasts, sound, quiet hours).
idapt notification update-configUpdate notification config.
idapt notification getGet a notification.
idapt notification sendSend a notification.
idapt notification updateUpdate a notification (mark read, …).
idapt notification deleteDelete a notification.
idapt notification read-allMark all notifications read.

Run idapt help notification <verb>for the exact arguments of any of these.

Send to workspace members

Pass the recipients and content as structured input. target is one of all_members, admins, or owner, or supply explicit recipient_ids instead:

idapt notification send --workspace-id <workspace-id> --json '{
  "target": "all_members",
  "title": "Build passed",
  "message": "Staging deploy succeeded",
  "dedup_key": "build-1421"
}'

A dedup_key makes retries idempotent for 24 hours per recipient. A single send to many people counts as one notification. You can send up to 100 notifications per 24 hours.

The response includes a resolved deep_link with a kind, path, and url, so you can drop the link straight into a log.

Deep-link to a resource

Attach a deep link so recipients land on the right place from the bell, an email button, or a push action. The supported kinds are chat, file, workspace, agent, computer, settings, billing, usage, support-ticket, hub, and home. Run idapt help notification send for the exact fields each kind takes.

A deep link does not grant access. Recipients sign in as usual and meet the normal permission checks at the destination.

Preferences and quiet hours

Manage delivery channels and quiet hours with the preferences and config verbs above. Quiet hours mute email and push, while in-app notifications still land in the bell. Three events always break through: a computer that auto-terminated, usage crossing 90%, and a computer workflow error.

Related articles

🔔

Notifications API

Send notifications to workspace members and manage your inbox programmatically.

🔔

Notifications over MCP

Send notifications from Claude, Cursor, or any MCP-compatible tool.

📖

Command reference

The idapt <resource> <verb> grammar, how to discover any command from the terminal, and the full command list.

Was this helpful?