- 01 One PSI bot in Slack — each coworker has its own alias
- 02 Multiple coworkers can live in the same channel
- 03 Replies, progress updates, and results come back to the same thread
Product | psi* Coworkers
Slack-invoked AI coworkers that operate your business from a channel.
Create job-function principals like customer-service or sales-ops, scope them to apps and flows, bind them into Slack channels, and let your team invoke them by mention. Every action runs through psi*'s orchestrator with the same policy, tools, approvals, and audit as browser-side work.
What it's like to use
psi* Coworkers use your apps exactly like a person would.
Apps and flows become the harness for your agents to do specific and open-ended tasks — while only giving agents access to the exact data and tools they need, without the risk of agent escape.
- 01 Navigates pages, sets values, and triggers actions in your apps
- 02 Can also do research and browser work when the task needs it
- 03 Only gets access to the specific apps and flows you assign — nothing more
- 01 Per-channel memory so the coworker knows your customers and accounts
- 02 Memory is versioned — you can see what it learned and when
- 03 Bad data and prompt injections are quarantined before they stick
- 01 Risky actions pause for human approval before running
- 02 Approvals happen in psi* — Slack shows the link to review
- 03 Every action is logged with who asked, who approved, and what happened
How it works
How a principal coworker gets started.
From identity to live Slack invocation — psi* runs a continuous loop of principal creation, configuration, channel binding, and governed execution.
01
Create
Define a job-function principal — customer-service, sales-ops, runtime-qa — with identity and execution mode (authoring, runtime, or both).
02
Configure
Assign explicit app/branch/publication/flow scope, prompt profile, tool policy, channel memory, and approval gates through the Principals control center.
03
Bind
Connect Slack via WorkOS Pipes and bind principal aliases into channels. Multiple principals can share the same channel.
04
Operate
Team mentions the PSI bot with a principal alias in Slack. psi* resolves the principal, runs the work through the orchestrator, and posts status back to the same thread.
What changes
From Slack request to governed execution.
A psi* Coworker does more than answer. It enters the applications and flows assigned to it, performs bounded work, and returns the result with its operating record intact.
01
Work execution
Before
A Slack request waits for someone to recover context across CRM records, email, spreadsheets, and previous conversations.
After
The coworker starts with channel memory and assigned app context, performs bounded work, and returns progress and results to the same thread.
02
Access control
Before
Teams rely on broad automation permissions or repeated manual handoffs whenever a workflow reaches a sensitive step.
After
Each principal receives explicit app, flow, and tool scope. Approval-gated actions pause for a human decision before execution.
03
Accountability
Before
A result arrives without a consistent record of the actions, approvals, and production resources behind it.
After
Sessions, actions, approvals, and affected resources remain attributable to the coworker, channel, and originating request.
Principal control center
One surface to provision, scope, tune, and inspect every coworker.
The Principals page becomes the coworker control center — identity, apps, prompts, tools, Slack channels, memory, approvals, and activity in one place.
- 01Job-function identity (customer-service, sales-ops, runtime-qa)
- 02Explicit app/branch/publication/flow scope binding
- 03Execution mode: authoring-only, runtime-only, or both
- 01Principal prompt profile with app/context inheritance
- 02Channel overlay prompts for per-channel behavior
- 03Memory with revision history, compaction, and quarantine rules
- 01Tool policy per principal with descriptor-level overrides
- 02Capability-family ceilings in Config above tool overrides
- 03Approvals stay in PSI — Slack shows status links only
- 01WorkOS Pipes connection status and setup handoff
- 02Alias/channel binding editor with collision feedback
- 03Readiness states: draft, configured, active, suspended, disabled
- 01Principal-filtered session and orchestrator audit
- 02Memory, lineage, and replay inspection
- 03Debug deep links from activity summaries
Power that stays safe
Governed coworker systemYour apps are the harness
A psi* coworker can use any app you build exactly like a person would — navigate pages, fill forms, trigger actions, run research, and hand work off to flows.
But it can only touch the apps and tools you assigned to it. No agent escape, no unscoped access, no working outside the lines.
Outcome Full agent capability. Explicit operating boundaries.
From Slack mention to work done — every step is visible and controlled.
Surface What you see What psi* handles
Mention @psi customer-service: check Acme's ticket verify, dedupe, resolve the right coworker
Work coworker navigates your app and does the task memory, tools, approvals, and app scope enforced
Result reply lands in the Slack thread full audit trail logged in psi*
Repeat same request works on a cron flow binding and schedule reuse
App access only the apps and flows you assign — nothing more
Tools pick exactly which tools each coworker can use
Approvals risky actions pause for a human yes before running
Memory the coworker remembers your channel context — and you can see what it learned
Audit trail every action logged — who asked, what ran, what it touched
Schedules turn a working request into a cron job when the pattern is ready