# Workweaver User Guide Workweaver is the Organization Operating System (OrgOS) -- Mission Control for AI-Ops Teams that ship together, and prove it. This guide covers everything an operator or administrator needs to get started, manage AI agents, run missions, and maintain the platform. > **Product stage**: Workweaver is currently in guided rollout. Features, > pricing, and integrations may evolve as access expands. Founding member > pricing is locked for 12 months from enrollment. See the > [Terms of Service](https://workweaver.ai/terms.html) for full rollout terms. --- ## Table of Contents 1. [Getting Started](#getting-started) 2. [Workspace Overview](#workspace-overview) 3. [AI-Ops Management](#ai-ops-management) 4. [Mission Control](#mission-control) 5. [Task Management](#task-management) 6. [Evidence and Proof](#evidence-and-proof) 7. [Integrations and Connectors](#integrations-and-connectors) 8. [WorkMemory](#workmemory) 9. [Voice, Meetings, and Calendar](#voice-meetings-and-calendar) 10. [Flows and Custom Outcome Loops](#flows-and-custom-outcome-loops) 11. [Quick Agent](#quick-agent) 12. [The Coding Bridge](#the-coding-bridge) 13. [Security and Access Control](#security-and-access-control) 14. [Billing and Metering](#billing-and-metering) 15. [Troubleshooting](#troubleshooting) 16. [FAQ](#faq) 17. [Known Boundaries and Limitations](#known-boundaries-and-limitations) 18. [Public References](#public-references) --- ## Getting Started ### Signing In 1. Navigate to . 2. Sign in with one of the supported identity providers: - **Google** (Gmail / Google Workspace) - **Microsoft** (Azure AD / Microsoft 365) - **Zoho** 3. On first login you will land on the Mission Control dashboard. > **Guided rollout access**: During guided rollout, access is invitation-based. > If you received an invite token, enter it when prompted during sign-in. ### First-Run Checklist After signing in for the first time, complete these steps in order: 1. **Choose a flagship workflow** -- start with one of the three pre-built options: - Morning Briefing - Inbox + Calendar Triage - Lead Follow-up Agent 2. **Connect the minimum tools** -- open the Connection Center and link only the integrations that your chosen workflow requires. 3. **Review and approve the plan** -- Workweaver generates a bounded execution plan. Review it, approve any gated actions, and let the run execute. 4. **Inspect proof** -- after the run completes, check proof cards, the Decision Trace, and the Evidence Trail to verify results. ### Account Settings Access your account settings from the Settings anchor in the top-level navigation. From here you can: - Update your profile and notification preferences. - Manage connected integrations (add, remove, re-authorize). - View API keys for the WorkMemory API. - Export your data at any time (unconditional right, per Terms of Service). --- ## Workspace Overview The Workweaver workspace is organized around three anchors and a right dock: ### Three Anchors | Anchor | Purpose | |------------|--------------------------------------------------------| | **Mission** | View and manage active missions, runs, and AI-Ops | | **Inbox** | Review items that need your attention or approval | | **Settings**| Configure integrations, preferences, and account details| ### Right Dock Panels The right dock provides contextual information alongside any view: | Panel | Purpose | |------------|-------------------------------------------------------| | **Chat** | Converse with your AI-Ops directly | | **Proof** | Inspect evidence, approvals, and decision traces | | **Memory** | Browse and search WorkMemory entries | | **Tools** | Access quick actions and connected tool status | ### Omnibox The omnibox at the top of the workspace accepts natural-language commands and a six-verb grammar: - `go ` -- navigate to a surface (e.g., `go mission calendar`) - `open ` -- open a specific mission, agent, or integration - `start ` -- launch a workflow or quick agent run - `ask ` -- ask your AI-Ops a question - `review ` -- review a pending approval or proof card - `configure ` -- jump to a configuration panel --- ## AI-Ops Management ### What Is an AI-Ops? An AI-Ops is a governed, autonomous agent with its own identity, memory, tools, and budget. Each AI-Ops: - Operates with an explicit identity mode (`shared` by default, `dedicated` through explicit elevation). - Has scoped credential access -- cross-agent credential sharing is denied by default. - Maintains private memory at the `agent` scope, with explicit promotion to `team`, `department`, or `org` scope. - Executes within bounded TimeBlocks with spend and time limits. ### Activating (Creating) an AI-Ops 1. Navigate to **Mission > AI-Ops**. 2. Select **Activate New AI-Ops** or use the omnibox: `start activate`. 3. Define the agent's role, responsibilities, and which tools it should have access to. 4. Set budget and authority limits (maximum spend per run, approval gates for high-risk actions). 5. Confirm and activate. ### Configuring an AI-Ops From the AI-Ops detail view you can: - **Edit role and responsibilities** -- update the agent's mission scope. - **Manage tool access** -- add or revoke access to specific integrations. - **Set budget limits** -- configure per-run and per-day spend caps. - **Configure approval gates** -- define which action categories require human approval before execution. - **View activity history** -- see all runs, TimeBlocks, and outcomes. ### Monitoring AI-Ops The Mission dashboard shows the status of each AI-Ops: - **Active** -- currently executing a mission or TimeBlock. - **Idle** -- available and waiting for work. - **Waiting** -- paused, waiting for human approval. - **Error** -- encountered an issue; check the Evidence Trail for details. --- ## Mission Control ### Creating a Mission A mission is a high-level objective that one or more AI-Ops execute. 1. Navigate to **Mission > New Mission** or use: `start mission`. 2. Describe the objective in plain language. Be specific about the desired outcome. 3. Assign one or more AI-Ops. 4. Review the generated plan -- Workweaver decomposes the mission into bounded TimeBlocks with explicit action steps. 5. Approve any gated actions and launch. ### Tracking Mission Progress The Mission Calendar provides a time-first view of all work: - **Day view** -- shows TimeBlocks for the current day. - **Week view** -- shows planned, active, and completed work across the week. - **Status indicators**: - Planned (grey) - Active (blue) - Waiting for approval (amber) - Completed (green) - Failed (red) - Cancelled (strikethrough) ### Mission Lifecycle ``` Describe -> Plan -> Approve -> Execute -> Prove -> Complete ^ | | v +---- Steering -------+ ``` At any point during execution you can: - **Pause** a mission to review intermediate results. - **Steer** by providing additional instructions or constraints. - **Cancel** if the mission is no longer needed. - **Resume** a paused mission. --- ## Task Management ### Creating Tasks Tasks are the atomic units of work within a mission. They can be: - **Auto-generated** by Workweaver when decomposing a mission. - **Manually created** by an operator via Mission Control. - **Spawned** by an AI-Ops during execution (bounded delegation). ### Assigning Tasks Tasks are assigned to AI-Ops based on: - Role fit (which agent has the right tools and capabilities). - Capacity (which agent is available). - Budget (which agent has remaining spend allocation). You can override automatic assignment and manually assign tasks to a specific AI-Ops. ### Task States | State | Meaning | |-------------|--------------------------------------------------| | `pending` | Created but not yet started | | `active` | Currently being executed | | `waiting` | Blocked on human approval or external dependency | | `completed` | Finished successfully with proof | | `failed` | Encountered an unrecoverable error | | `cancelled` | Manually cancelled by an operator | ### Completing Tasks When an AI-Ops completes a task: 1. Results and artifacts are attached to the task record. 2. A proof card is generated with linked evidence. 3. The parent mission status updates to reflect progress. 4. If follow-up actions are needed, new tasks may be spawned (within delegation bounds). --- ## Evidence and Proof ### How Evidence Is Tracked Workweaver records an append-only evidence graph for every action: - **Plan** -- the bounded execution plan that was approved. - **TimeBlocks** -- each bounded unit of work with start/end times. - **Approvals** -- which human approved which gated action, and when. - **Outputs** -- the results produced (emails sent, CRM records updated, documents created, etc.). - **Decision Trace** -- the reasoning chain that led to each decision. - **Linked Evidence** -- references to external artifacts (CRM records, calendar events, email threads). ### Viewing Proof Proof is accessible from multiple surfaces that all read the same underlying execution ledger: - **Mission Calendar** -- time-ordered view of what happened and when. - **Proof Cards** -- per-task summary with linked evidence. - **Decision Trace** -- full reasoning chain for audit. - **Evidence Trail** -- chronological log of all actions and outcomes. ### Honest Degradation If an external provider is unavailable or a capability is degraded during a run, Workweaver surfaces that fact honestly. The proof record shows: - Which channels or actions were attempted. - Which succeeded, which were skipped, and why. - Per-channel results so you can see exactly what happened. --- ## Integrations and Connectors ### Supported Connectors **First-run connectors** (strongest integration support): | Connector | Capabilities | |------------------|---------------------------------------| | Gmail | Read, send, label, archive | | Google Calendar | Read events, create events | | Slack | Read channels, post messages | | HubSpot | Full CRUD (contacts, deals, tasks) | | Salesforce | Full CRUD (contacts, opportunities) | | WhatsApp | Send and receive messages | **Demand-based connectors**: Telegram. **Standards-based extensions**: OAuth2, REST/OpenAPI, webhooks, and a organization-owned coding bridge for custom integrations. ### Connecting a Tool 1. Go to **Settings > Connection Center**. 2. Select the integration you want to connect. 3. Follow the connection flow shown for the integration. Zoho products are connected through Workweaver-owned, product-scoped consent, one product at a time. 4. Once connected, the integration appears as available in your AI-Ops' tool inventory. ### Connection Best Practices - Start with the minimum connector set needed for your chosen workflow. - Add integrations incrementally as you expand to more workflows. - Gmail, Google Calendar, and Slack are the recommended first-run connectors. - Credentials are organization-owned and organization-scoped. Workweaver does not share credentials across organizations. ### Disconnecting a Tool 1. Go to **Settings > Connection Center**. 2. Find the integration and select **Disconnect**. 3. Confirm the action. Active missions using that integration will be notified and will degrade gracefully. --- ## WorkMemory WorkMemory is Workweaver's structured memory system. It stores context, facts, and history so AI-Ops consult history before acting -- never starting from zero. ### Memory Scopes | Scope | Visibility | |--------------|-------------------------------------------| | `agent` | Private to the individual AI-Ops | | `team` | Shared within a team of AI-Ops | | `department` | Shared within a department | | `org` | Organization-wide shared knowledge | Memory is private-by-default at the `agent` scope. Promotion to broader scopes requires explicit intent and creates an audit trail. ### Memory Operations - **Store** -- AI-Ops automatically capture relevant context during runs. - **Retrieve** -- tiered retrieval: high-level summaries first, drill down when needed. - **Reconcile** -- contradictions are resolved by overwriting stale facts with newer truth, preserving provenance. - **Decay** -- memory is maintained through consolidation, summarization, and re-indexing to prevent rot. ### WorkMemory API Operators can interact with WorkMemory programmatically: ```bash # Store a memory curl -X POST https://api.workweaver.ai/memory/v1/memories \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"content": "Q3 sales target is 500 units", "scope": "org"}' # Search memories curl "https://api.workweaver.ai/memory/v1/memories?q=sales+target" \ -H "Authorization: Bearer YOUR_API_KEY" ``` API keys are managed in **Settings > API Keys**. --- ## Voice, Meetings, and Calendar ### Voice Calls Workweaver supports inbound and outbound voice calls through AI-Ops: - **Inbound**: AI-Ops answer calls, qualify leads, handle inquiries, and route to humans when needed. - **Outbound**: AI-Ops make calls for follow-ups, appointment confirmations, and outreach. - **Recording**: Call recording requires explicit caller consent. Recordings are stored encrypted and linked to evidence. - **Transcription**: AI-powered speech-to-text generates searchable transcripts from recorded calls. ### Meetings - **Joining**: AI-Ops can join scheduled meetings to take notes and track action items. - **Follow-through**: Automated extraction of action items and CRM updates from meeting notes is expanding (partially shipped). ### Calendar - **Reading events**: AI-Ops can read your calendar to plan around existing commitments. - **Creating events**: AI-Ops can create calendar events for meetings, follow-ups, and deadlines. - **Conflict resolution**: Automatic conflict detection and intelligent rescheduling is in progress. --- ## Flows and Custom Outcome Loops Beyond the flagship workflows, you can compose custom outcome loops using the Flows builder: 1. Design outcome loops as trigger-branch-action graphs. 2. Use shipped templates as your baseline. 3. Customize by adding or removing nodes to produce your desired end outcome (follow-up, escalation, task handoff, etc.). 4. Save and schedule workflow instances. 5. Approvals, monitoring, and evidence stay in the same Mission surface. --- ## Quick Agent Quick Agent is the fastest way to run a one-off task: 1. Use the omnibox: `start quick agent` or the Quick Agent button. 2. Describe your objective. 3. Quick Agent automatically selects the smallest safe swarm shape based on: - The objective complexity. - Side-effect risk assessment. - Recent TimeBlock history. 4. Manual override is available if you need a specific execution shape. 5. Autoresearch runs before the first TimeBlock to improve planning, delegation, swarm posture, and block allocation. --- ## The Coding Bridge Workweaver includes a governed coding bridge for development tasks: - The GitHub coding bridge creates issue-level artifacts that keep work traceable. - Governed coding workers can clone or fork repos, run bounded plan/edit/test loops, and stop at approval before push or PR delivery. - **Organization rule**: External coding subscriptions and GitHub credentials remain organization-owned and organization-scoped. Workweaver does not host a shared global subscription. --- ## Security and Access Control ### Authentication - All sign-in flows use OAuth 2.0 with supported identity providers (Google, Microsoft, Zoho). Zoho sign-in is separate from Zoho product connections, which are managed in Integrations. - Multi-factor authentication is supported through your identity provider. - Session tokens are short-lived with automatic refresh. ### Authorization - AI-Ops operate with scoped credentials -- each agent can only access the tools explicitly granted to it. - High-risk actions are approval-gated by default. - Cross-agent credential access is denied by default. - Delegation is bounded by configurable depth, concurrency, wall-clock, and spend limits. ### Data Protection - All data is encrypted at rest (AES-256) and in transit (TLS). - Primary storage is in US East (`us-east-1`). - Workweaver complies with GDPR, CCPA, and UAE Data Protection Law. - You can export or delete your data at any time. --- ## Billing and Metering ### How Billing Works Workweaver uses usage-based billing. You pay for what your AI-Ops actually do: - Metering tracks actions across voice, messaging, CRM operations, and compute time. - Cost visibility is built into the Mission dashboard so you can see spend per mission and per AI-Ops. - Budget limits prevent runaway costs. ### Viewing Usage - Navigate to **Settings > Billing** to see current usage and invoices. - Per-mission and per-agent cost breakdowns are available in Mission Control. --- ## Troubleshooting ### Sign-in or OAuth Callback Failed 1. Confirm the identity provider redirected you back to Workweaver, not a stale login route. 2. Clear your browser cookies for `workweaver.ai` and retry. 3. Try signing in through . 4. If the problem persists, contact support via . ### A Run Shows "Partial" or a Warning - This means an external provider was unavailable or a step was skipped. - Workweaver surfaces per-channel results so you can see what actually happened and what was skipped. - Check the Evidence Trail for the specific failure reason. ### A Workflow Needs More Tools Than Are Connected 1. Go to **Settings > Connection Center**. 2. Connect only the missing integrations. 3. Re-run the workflow. The goal is to complete one workflow with proof, not to pre-configure everything up front. ### An AI-Ops Is Stuck in "Waiting" State - Check **Inbox** for pending approval requests. - The agent may be waiting for your approval on a gated action. - Approve or reject the pending item to unblock execution. ### Connection Center Shows "Re-authorize Required" - OAuth tokens expire periodically. - Click **Re-authorize** to refresh the connection. - No data is lost during re-authorization. ### Evidence Trail Shows Gaps - Evidence coverage is expanding toward full action tracing. - Key actions and outcomes are always traced with full reasoning. - Minor internal steps may not yet appear in the trail. --- ## FAQ ### What is the difference between a mission and a task? A **mission** is a high-level objective (e.g., "Follow up with all leads from last week's webinar"). A **task** is an atomic unit of work within a mission (e.g., "Send follow-up email to john@example.com"). Missions decompose into tasks automatically. ### Can I have multiple AI-Ops? Yes. You can activate multiple AI-Ops, each with different roles, tool access, and budget limits. They operate independently with private memory by default, and can share context through promoted memory scopes. ### Is my data safe? Yes. All data is encrypted at rest and in transit. Credentials are organization-scoped and never shared across organizations. You can export or delete your data at any time. See the [Privacy Policy](https://workweaver.ai/privacy.html) for full details. ### What happens if an external service goes down? Workweaver degrades gracefully. If a connected service (Gmail, Slack, CRM) is unavailable, the run continues with available channels and reports exactly which steps succeeded and which were skipped. No silent failures. ### Can AI-Ops access my desktop or local apps? No. Workweaver operates through cloud, SaaS, and channel execution only. It does not control your desktop, browser, or local/edge devices. ### How do I cancel my account? Contact support via or email contact@bitfoundry.ai. You have 30 days to export your data after cancellation. See the [Terms of Service](https://workweaver.ai/terms.html) Section 10 for full termination terms. ### Is there a refund policy? Yes. There is a 14-day unconditional refund window from your first payment. Additionally, a 30-day Evidence Graph Guarantee applies: if your AI-Ops fails to deliver 40+ verifiable hours of autonomous work in month one, you receive a free extension or full refund at your election. See Terms of Service Section 7. ### Can I use my own AI models? Workweaver manages the AI infrastructure. The models powering your AI-Ops are selected for reliability and governed execution. Custom model selection is not currently available during guided rollout. ### What is the coding bridge? The coding bridge is an orchestrated handoff for development tasks. It lets your AI-Ops create GitHub issues, clone repos, make code changes within a bounded plan/edit/test loop, and deliver pull requests -- all traceable and approval-gated. --- ## Known Boundaries and Limitations - Workweaver operates through cloud, SaaS, and channel execution. It does not control your desktop or local apps. - Mobile parity is still behind the desktop experience. - Some WorkMemory extraction paths remain partial when vision infrastructure is not configured. - **Calendar dispatch**: Reading and creating calendar events is shipped. Automatic conflict resolution and intelligent rescheduling are in progress. - **Meeting dispatch**: Joining meetings is shipped. Automated follow-through actions (action item extraction, CRM updates from meeting notes) are expanding. - **Evidence coverage**: Key actions and outcomes are traced with full reasoning. Not every internal step is captured yet -- coverage is expanding toward full action tracing. - **Computer use / GUI automation**: Screenshot capture is shipped. Full GUI interaction (clicking, typing, navigating desktop apps) is planned but not yet available. - **Document processing**: Text extraction is shipped. Vision-based and multimodal extraction (images, diagrams, handwriting) is in progress. --- ## Public References - Product: - Platform: - Guides index: - Agent knowledge: - Brand facts: - LLM assets: and - About and contact: - Privacy policy: - Terms of service: