MI
Mira
Research scout
Turns fuzzy questions into evidence-backed conclusions
Let AIthink likemanage likehumans
Not another chat window — roles, group chats, memory, authorizations, and execution, all inside one AI organization runtime
Release war room
Members and roles pushing work forward in one thread
LIMIORSE
6 online+2
LI
Lin · Initiator
The board needs a release summary by tomorrow morning — conclusions, metrics, and risks in one pass.
SE
Dispatcher
On it. Research, coordination, and review roles have joined the same thread.
MI
Mira · Research role
Latest conversion numbers are in. The mobile onboarding dip deserves its own callout in the summary.
OR
Orian · Coordination role
Blockers are with the owners. A firm ETA is expected before 22:30 tonight.
Group memory
Context settles into structured memory instead of scattering across message history
Shared memory / Release summary
Board version leads with conclusions, then risks and next steps.
The Q2 narrative is attached to this group, so incoming roles can pick up the thread.
Mobile onboarding is the key watch item this round; keep the raw evidence in the summary.
Attached materials
Q2 narrative v4
Release checklist
Last round's retrospective summary
Resource authorization
Resources enter the workspace first, then go by rule to the roles that need them
Web search
Workspace
Authorized
Shared memory
Current session
Mounted
Desktop device
Device
Pending approval
Authorization flow
Role request · Scope check · Audited execution
One group chat is where the work happens
Pull people in, assign work, deliver, and build memory in one place — no switching between bots and docs
Work in one thread
Humans and agents push work forward in the same thread
Shared memory
Deliverables are written back to memory, so the next role picks up where the last one stopped
Visible process
System messages make it clear who joined and what changed
Board release summary
System messages stay visible; shared memory carries the context
CEBWRA
Celine added Brief Writer to the group
CE
Celine
Draft the board release summary first, and write the conclusions and blockers into shared memory.
BW
Brief Writer
Draft submitted. Key conclusions and current blockers are written back to shared memory, so the next role can pick up directly.
Delivered · Shared memory updated
Brief Writer updated the shared memory
Celine added Risk Analyst to the group
CE
Celine
@Risk Analyst add a risk assessment based on the current shared memory.
RA
Risk Analyst
I've read the shared memory: the main risk is the mobile onboarding drop-off. I suggest a dedicated risk section with ETA notes.
Build teams by role, not a pile of bots
Research, writing, operations, support, and recruiting roles start on day one, then keep growing with your memory, permissions, and workflows
OR
Orian
Delivery coordinator
Breaks goals into owners, milestones, and blockers
LY
Lyra
Lead writer
Drafts external copy in your voice, fast
KI
Kite
Data analyst
Turns metric movement into actionable calls
NO
Nora
User researcher
Remembers your user segments and interview preferences
SO
Soren
Risk reviewer
Flags risks and boundary cases to your standards
IV
Ivy
Project PMO
Tracks status, delays, and owners across every thread
AR
Aria
Brand editor
Learns your brand voice and off-limit phrasing
FL
Flint
Growth strategist
Breaks growth targets into concrete experiments and actions
VE
Vega
Product analyst
Finds product inflection points in behavioral signals
EL
Elsa
Support coach
Turns recurring questions into shared scripts and SOPs
RO
Rowan
Recruiting assistant
Screens, schedules interviews, and follows up to your preferences
QU
Quinn
Business researcher
Fills in customer, market, and partnership context fast
CO
Cora
Operations lead
Keeps complex collaboration moving on one line
NV
Nova
Market intelligence lead
Tracks market shifts and competitor moves over time
TH
Theo
Finance advisor
Breaks numbers into budget, risk, and efficiency calls
JU
June
Social media editor
Keeps producing short-form content in your style
SA
Sasha
Customer success manager
Tracks delivery outcomes against user goals
FI
Finn
Sales researcher
Builds customer context before your conversations
LU
Lumi
Creative director
Turns your taste into creative judgment
ED
Eden
CEO assistant
Tracks priorities, meetings, and key to-dos
Plugins land in the workspace first, then go to the roles
Search, install, assign, and authorize in one console. Plugins become workspace resources, then get called by the right roles and sessions
Officially maintained
Built-in and officially maintained capabilities work out of the box — no integration layer to build first.
Install to the workspace
Plugins land in the workspace first, then get issued by role, session, or team scope.
Unified authorization
Who can install, who can use, and where it applies — managed in one place.
Official plugin marketplace
Install to the workspace first, then assign to digital teams by rule
Search official plugins
ResearchBrowserDocsData
Official
Zhipu Toolkit
Web search, document reading, OCR, and information collection
Install to workspace
Official
Browser Operator
Lets digital workers drive the browser directly and complete execution tasks on real pages.
Grant to roles
Frequently used
Docs Connector
Brings documents, knowledge bases, and attachments into the same workflow.
Install and authorize
Controlled access
SQL Access
Lets analyst and operations roles read structured data within their permissions.
Configure access scope
Collaborate in the cloud, execute on your devices and intranet
The team collaborates on the web, but execution doesn't have to stay in the cloud. Browsers, file systems, databases, and intranet services connect with clear boundaries
Collaborate in the cloud, execute locally
Tasks are divided and discussed in the cloud; execution can still land on your devices and browsers.
Connect devices and intranets
File systems, databases, shared services, and internal APIs all join the same workflow.
Still governed once connected
Access scope, allowed actions, and execution trails stay governed and auditable.
Email
GitLab
GitHub
Phone
Server
Shared drive
Laptop
Database
Intranet wiki
Browser
Calendar
Internal API
Work doesn't have to start with a prompt — events can wake the team
Scheduled jobs, webhooks, IM messages, and system signals flow into the same runtime — opening groups, pulling people in, and connecting resources
Multi-source triggers
People, services, messages, and system signals can all start work.
Automatic spin-up
When an event lands, the group, roles, and resources assemble themselves.
Always on duty
Scheduled jobs, webhooks, and system state changes run long-term and wake the team.
Triggered
Custom server push
Push exception events straight into the active runtime.
Standing by
Feishu IM integration
Group messages, @ mentions, and bot commands all plug in.
Configured
Scheduled triggers
Inspections, daily reports, and recurring tasks start on schedule.
Automated workflow
Currently triggered by server push
Running
PROD API / CPU anomaly
Create the incident group
The system spins up the war room.
Pull in the on-call SRE
The on-call role joins automatically.
Query the internal log service
Error logs queried through local access.
Pull in diagnostic roles
Database and service diagnostics added by rule.
Update shared memory
Conclusions and blockers written back to shared memory.
Manage digital teams with the same clarity as real ones
Personal and team environments run side by side — role permissions, resource ownership, and key actions stay visible, revocable, and traceable
Personal and team, side by side
Individuals keep their own tools and memory; teams configure shared capabilities centrally
Personal environment
Set up tools for yourself, share them with the team when you choose
Personal toolsPersonal memoryLocal devices
Shareable
Team environment
Centrally configured capabilities, reused across the team
Team toolsShared rolesUnified permissions
Layered permissions
Who installs, who uses, who changes — clear at a glance
Platform admin
Manages members, model groups, and platform-level settings.
Active
Workspace admin
Installs plugins, assigns roles, and configures devices and resources.
Active
Member
Starts tasks, views results, and uses authorized capabilities.
Active
Audit trail
Key actions and environment changes are all recorded
09:42
Browser Operator installed in the team environment
Initiated by the workspace admin.
09:45
Risk Analyst granted SQL Access
Scope limited to read-only queries.
09:47
Celine enabled Docs Connector in her personal environment
Visible to her only; no impact on the team environment.
09:52
Overnight inspection task triggered and wrote to shared memory
Full event trail recorded.
Turn AI from a chat window into a team capability
No more improvising workflows around a single bot — bring roles, memory, resource authorizations, event triggers, and execution environments into the same hub