Pages or apps: what Bob builds, and which to ask for
Bob builds pages you look at and apps your team works in. What each one is, who can open it, what it costs to keep, how to pick, and what neither does yet.
Read →What we learned building the AI employee with 3,200+ connections, scoped memory, approval workflows, and a receipt for the work.

Bob builds pages you look at and apps your team works in. What each one is, who can open it, what it costs to keep, how to pick, and what neither does yet.
Read →The HeyBob app for Mac and Windows writes your meeting notes with no bot joining, nothing to connect, and no call at all. Then Bob does the follow-ups after you tap Do it. With the limits spelled out.
Read →We timed the same ten questions in Slack and in the HeyBob app. Answers land at about the same time. The app feels faster because Bob shows he has your message the instant you hit enter, and shows his steps while he works.
Read →Credit-priced AI employees mark up every token. Bob's new BYOK tier is $349/month: bring your own Anthropic and OpenAI keys, pay your provider for tokens, and pay us only for the platform.
Read →Claude is a general AI assistant across web, desktop, and Slack. Bob is an AI employee in your Slack with 3,200+ connections, approvals, and receipts. How to choose.
Read →Search email, summarize threads, create drafts, and send approved replies from Slack through a personal Google connection.
Read →List events, find free time, create meetings, and respond to invites with the calendar owner in control.
Read →Search and read files, copy documents, and upload approved text artifacts while the team works in Slack.
Read →Read ranges, append rows, update cells, and create spreadsheets with personal OAuth and reviewable writes.
Read →Use authenticated Outlook actions with a deliberate workspace identity and default approvals for external writes.
Read →Use available workbook actions, join Excel with other systems, and keep changes explicit and reviewable.
Read →Use authenticated OneDrive file actions with clear account scope, tenant permissions, and write gates.
Read →Bring account context into Slack, reconcile systems, and prepare supported CRM changes for approval.
Read →Search code, read diffs, create issues and branches, commit files, and open approved pull requests.
Read →Search pages, query databases, and create or update approved Notion content from the conversation.
Read →Search CRM records, create contacts, update deals, and add approved notes with per-user access.
Read →Use available meeting actions with clear account scope and join Zoom to the preparation and follow-through.
Read →Launch Cursor Cloud Agents for bugs, check their work, send follow-ups, and hand reviewable pull requests back to the team.
Read →Search, create, update, and comment on Linear issues from Slack with per-user OAuth, approval gates, and a receipt for the work.
Read →Use Jira Cloud from Slack for issue triage, reporting, creation, comments, and transitions while keeping writes reviewable.
Read →Why finished work, 3,200+ connections, scoped memory, per-user access, approvals, and receipts separate Bob from a chatbot in Slack.
Read →Claude is not leaving Slack. It is becoming Claude Tag. A fair look at what Tag does well and where Bob's connections, controls, memory, and receipts differ.
Read →Four steps, about five minutes: install the app, invite it to channels, connect Drive, Gmail, Notion or GitHub, then ask in plain English.
Read →Workflow Builder now has AI steps, 70+ connectors, and branching. Bob adds 3,200+ connections, durable memory, open-ended judgment, approvals, and receipts.
Read →How Bob lets reads move, gates sensitive writes in Slack, scopes standing access to the action that earned it, and keeps every decision reviewable.
Read →What to log in 2026, plus an honest map of Bob's encrypted tool history, approval record, provenance, cost receipts, and remaining compliance boundary.
Read →Why Bob uses per-user OAuth, keeps sends and calendar changes behind approval, records email provenance, and refuses to shortcut Google's verification process.
Read →Bob's standard for the category: 3,200+ connections, scoped memory, external triggers, human gates, isolated execution, and a receipt for finished work.
Read →Readable approval cards, narrow standing grants, cost estimates, receipts, hard caps, and isolated sandboxes. Five controls Bob ships instead of slides.
Read →Person, channel, and company memory with provenance, correction receipts, and Slack-native edit/delete. Memory that can answer “says who?”
Read →OpenClaw is a capable local-first platform. Bob is the managed Slack coworker with 3,200+ connections, per-user access, approvals, and receipts already assembled.
Read →Hermes is a powerful self-hosted agent with memory, skills, schedules, and safety controls. Bob turns that class of capability into a managed team product.
Read →A fair, current comparison of Claude Tag's shared-channel agent and Bob's 3,200+ connections, per-user access, scoped memory, triggers, approvals, and receipts.
Read →