The puck. ecosystem
Your agents.
Your apps.
One little puck.
A physical front door to the tools you already use. Talk to an agent, capture a thought, or move a task forward without getting lost in your phone.
What you can do depends on your agent setup, connected accounts, and permissions.
Your agents
Use a Puck workflow or bring your own agent. Models and tools depend on what your agent or desktop setup supports.
- Voice via local agent
Hermes - Voice via local agent
OpenClaw
- Anthropic model via compatible agent
Claude
- Google model via compatible agent
Gemini
- xAI model via compatible agent
Grok
- Model via compatible agent
DeepSeek
- Moonshot AI model via compatible agent
Kimi
- Model via compatible agent
Qwen
- Model via compatible agent
Mistral
- Model via compatible agent
Llama
- Local model runtime · custom setup
Ollama
Coding agents and tools
Codex uses desktop dictation. Other tools shown here are examples for custom workflows. The available actions depend on your editor, agent, or repository setup.
- Desktop dictation
Codex
- Terminal and editor agent
Claude Code
- Google terminal agent
Gemini CLI
- Agentic editor
Cursor
- IDE, CLI, and cloud agent
GitHub Copilot
- Repository and pull request workflows
GitHub
- Editor coding agent
Cline
- Terminal coding agent
OpenCode
- Terminal coding agent
Amp
- Terminal coding agent
Qwen Code
- Editor with agent tools
Zed
- Spec-driven coding agent
Kiro
- Coding agent for JetBrains IDEs
JetBrains Junie
- Editor and agent tools
Windsurf
- Terminal with coding agents
Warp
- Coding agent for delegated tasks
Devin
- Browser-based app builder
Replit Agent
- Agentic development environment
Google Antigravity
Your everyday apps
Examples of what an app connector or automation can do. Each workflow needs the relevant service, account permissions, and setup.
Communication
- Email drafts
Gmail
- Email and inbox
Outlook
- Team messages
Slack
- Team messages
Microsoft Teams
- Channel updates
Discord
- Bot messages
Telegram
Notes and files
- Notes and pages
Notion
- Documents
Google Docs
- Spreadsheet rows
Google Sheets
- Files and folders
Google Drive
- File workflows
Dropbox
- Local notes and vaults
Obsidian
Tasks and calendars
- Tasks and follow-ups
Todoist
- Issue tracking
Linear
- Project tasks
Asana
- Task workflows
ClickUp
- Calendar events
Google Calendar
- Scheduling workflows
Calendly
Build and operate
- Issues and pull requests
GitHub
- Records and tables
Airtable
- CRM records
HubSpot
- Cards and boards
Trello
- Design workflow updates
Figma
- Payment event workflows
Stripe
Beyond the built-in workflows
Thousands of apps via automation platforms.
Build a workflow from your agent to the apps you use with a webhook or connector. Platforms like Make offer 3,000+ app connections in their own catalogs. You can also build with Zapier or n8n. These are third-party catalogs and require your own setup.
Choose a connection path
- Talk to a local agent
- Use Hermes or OpenClaw for voice requests. Choose the model and tools inside your agent’s setup.
- Work on your desktop
- Use the Codex desktop dictation workflow or set up another compatible desktop tool. Dot delegation is available where supported.
- Send a task to an app
- Connect a tool to your agent, or create an automation triggered by a webhook. Give it only the permissions it needs. Try a low-risk task, such as saving a draft note, before enabling more actions.
Integration questions
Can I use Claude or Gemini?
Choose a compatible agent that supports the model provider you want. You may need a provider account and an API key.
Does every listed app connect directly to Puck?
App workflows run through your chosen agent, connector, or automation platform. Check that your setup supports the action you want, and authorize the app before using it.
Can I use a local model?
Use an agent configured for a local runtime such as Ollama. You’ll need a host running the model and an agent that can reach it.
Authorize each app you want your agent to access. Logos identify their respective products and do not imply endorsement.