Product capabilities
One assistant.
Every tool your team uses.
A practical guide to what Pecus AI does today, and what needs account or provider setup.
Ask across your tools
AI provider key required- Questions across tools
- Ask in the web app or Slack. Pecus picks the relevant enabled tools, reads them, and answers in one run, continuing in the background for longer investigations.
- Sources on every answer
- Answers end with a list generated by code of each source used (tool, retrieval time, links, and whether more results existed) and each source that could not be read.
- Partial results, disclosed
- If a sign-in expired or a provider is down, Pecus continues with the other sources and says what is missing. Transient read failures are retried once.
- Evidence rules
- Counts and dates come from tool results. Pecus is instructed to separate verified facts from correlations and hypotheses, and tool content is treated as data, never as instructions.
- Relevant tools only
- Only tools that match the request are sent to the model (at most 30), keeping prompts bounded.
Connected tools
Account authorization required- Tool catalog
- Official MCP servers for Jira & Confluence (Atlassian), Stripe, Linear, Notion, Sentry and GitHub, with sign-in on the provider’s page (OAuth with automatic app registration) or an access token.
- Any MCP server
- Add other MCP servers approved by your administrator, using OAuth or a token. Tools are discovered automatically and each starts disabled.
- Built-in connections
- Gmail, Google Calendar and Slack through their own OAuth, plus GitHub with a token. Google and Slack need OAuth app configuration by the administrator.
- Read or write, labeled
- Each tool is labeled Read or Can change data, from the server’s own annotations or its name. Only read tools can run automatically.
- Reconnect when needed
- An expired or revoked sign-in marks the connection as needing attention, with a Reconnect button.
Slack
Slack app installation required- Mentions and direct messages
- Mention @Pecus in a channel or send it a direct message. Requests are signature-verified and duplicates are ignored.
- Private answers
- In shared channels, answers built from someone’s private data are sent to that person directly; the thread gets a short pointer.
- Approve from Slack
- Approve, reject or stop a task with buttons. Only the verified owner of the request can approve, and an approved action runs exactly once.
- Account linking
- The installer is linked through Slack sign-in; teammates confirm a one-time link while signed in to Pecus.
Delegation and control
Available- Durable tasks
- Hand over an outcome. Pecus works step by step, records every action and receipt, pauses for approvals and resumes afterwards, even after a restart.
- Approvals before changes
- Anything that can change data waits for approval in the web app or Slack. If a provider does not confirm a change, Pecus flags it instead of retrying.
- Budgets and limits
- Each task has a step limit, a 24-hour expiry and an AI-usage budget, with a daily limit per account. You can stop any task.
- Routines
- Save instructions and run them on demand, on a timezone-aware schedule, or from authenticated webhooks with duplicate protection.
- Always-on worker
- An optional worker process runs tasks, schedules and Slack replies continuously on any server, alongside the built-in scheduler.
Team and privacy
Available- Workspaces and roles
- Owners and admins invite teammates with single-use links and can remove access; removed members’ pending replies are withheld.
- Your permissions, no more
- Each request runs with the requester’s own connections and data. A Slack seat alone grants no tool access.
- Private accounts
- Supabase sign-in and database row policies keep each account’s records, memory, connections and tasks isolated.
- Encrypted credentials
- Provider tokens stay encrypted on the server and never reach the AI model, logs or Slack.
- Memory, activity and undo
- Save facts and preferences for Pecus to use, follow every change, and undo supported edits.
Current boundaries
Pecus does not yet join or transcribe meetings, connect to Microsoft Teams, or control a computer or browser. Approvals are per action; there is no bulk approval. Budgets count AI tokens, not money, and there is no billing yet. A user who belongs to several workspaces sees one of them. Answers from shared Slack channels use the requester’s private context only; there is no shared team knowledge base yet.
Provider-backed workflows need live verification after accounts are connected. Fixture tests do not prove behavior against a specific provider.