Self-hosted · Works with Microsoft 365

AI help for code and office work
Run it on your own machine

Write code, work with email and files, and schedule recurring tasks. Use the terminal, Web Console, Desktop preview, or Teams. Your security settings apply to every tool call.

One-click Install Read the Docs
runs locally tool risk scored 0–10 code + office
Choose models from GPT Claude Gemini & more

One assistant, every channel

Animated walkthroughs of office tasks and project workflows in Teams and Cloud Web. Hosted access requires an approved account and a connected local WorkPilot instance.

Workflow demos — animated examples across channels
Teams Morning briefing, email triage, and approval workflows
workpilot.newfuture.cc/chat Spec review, design drafting, and cross-system orchestration

New features

What's available now, what needs setup, and what to know before trying it.

Desktop app

Preview

Use the Web Console in a desktop window on Windows x64 / ARM64 or an Apple Silicon Mac.

Desktop guide CLI guide

Coding tasks

Opt-in

Enable coding.enabled to work in a separate Git clone. Commands run on your machine, not in a container, and follow your usual approval rules.

Coding guide

Browser Agent

Default on

Let the agent fill forms, switch tabs, and take screenshots. Set up the browser and sign in first; existing browser permissions still apply.

Browser guide

Code mode

Default on

Use Python to combine tool calls in a Monty sandbox. Each call still goes through the usual risk checks and approvals.

Code mode guide

Persistent agents

Available

Create agents with separate conversations, memory, and workspaces in local Web or Desktop. Use @name to continue a conversation.

Agent guide

Plugins & Store

Available

Install skills and MCP configurations from the plugin store. Plugin MCP servers start disabled; review their commands and scripts before enabling them.

Plugin guide

Triggers & automation

Experimental

Subscribe to events from GitHub, Azure DevOps, email, chat, files, and more, or define your own trigger conditions. Run tasks automatically when conditions are met.

Automation guide

Command hooks

Experimental

Run reviewed local commands when agent events occur. Content changes need another review. Future versions may break compatibility.

Hooks guide

Schedule work and get the results

Tell WorkPilot what to do and when. Enable the scheduler manually and keep WorkPilot running to receive results in your connected channels. A background service can start it at login.

Scheduled

Cron, interval, one-time, and bus-event jobs, with run history and optional persistent sessions.

"Every weekday 8am, brief me."

Heartbeat

When enabled, periodic preflight checks select maintenance that needs attention — updates, memory hygiene, skills, and storage health. Quiet checks skip the model call.

Background

Fork a long job in the background or delegate to Claude Code or GitHub Copilot.

"Run this migration in the background."

Pushed to you

Results land in Teams or Web Chat; a decision needed → an approval card on your phone.

Permissions still apply. Scheduled tasks still go through permission and risk checks and leave an audit trail. Auto reduces repeated prompts without bypassing hard blocks or required human approval. E-Stop blocks further tool calls.Memory is stored as text on your machine. You can read, edit, or delete it.

Permissions, approvals, and E-Stop

Each tool call gets a 0–10 risk score. Your profile decides whether to run it, use delayed approval, ask you, or block it. Auto uses Standard's access boundaries and reviews actions in the context of your task.

Risk-based approvals

Tool calls are scored 0–10. Low-risk actions can run directly; actions that need your approval send a card to Teams or another connected channel.

Global E-Stop

One command halts all tool calls. Must be explicitly reset by an authorized user.

Credential protection

Two-stage leak scanning with auto-redaction. Token cache encrypted at rest.

Where your data goes

Sessions, memory, and credentials stay on your machine. Prompts and tool content go to the providers and services you configure. The optional Cloud Gateway relays traffic without persisting conversation history.

Command Sandbox Path Sandbox SSRF Protection Audit Logging Security Profiles Entra ID Auth MCP Risk Policy Injection Defense Sub-agent Isolation Approval Escalation Secret Redaction Encrypted Secrets
Security guide

Native to Microsoft 365

Connect Microsoft 365 and development tools to work with them in chat. Set up credentials and permissions for each service; some also need administrator consent.

Teams

Chat with your AI assistant directly in Teams. Read and send Teams messages, approve risky actions with interactive cards — without switching apps.

Outlook

Read, triage, and draft email replies. Check your calendar and manage meetings — in conversation or automatically in the background.

OneDrive

Search, read, and manage files in OneDrive and SharePoint. Access team documents and shared libraries through natural language.

Copilot + Claude

Local Copilot / Claude Code on coding, review, and research — Delegate for background tasks, Bridge to drive the CLI from Teams or Web Chat.

Entra

Use Entra ID for Microsoft identity and cloud connections. Microsoft 365 permissions and consent remain separate from GitHub Copilot sign-in.

Azure

DevOps work items, pipelines, repos, and deployments. Manage Azure resources, subscriptions, and resource groups.

GitHub

Create issues, open PRs, search code, and manage repos. Combine with Copilot for end-to-end AI-assisted development.

Microsoft+

Connect services such as ICM, Service Tree, and Kusto through configured integrations, subject to your organization's access and authentication requirements.

One command, ready to go

Run locally in the terminal or Web Console, or connect Teams and Cloud Web through the optional stateless Cloud Gateway. Hosted preview access requires allowlisting; local use does not.

Preview and experimental features are still changing. Check their limits before using them for critical work, and report issues you find.

Install WorkPilot

PowerShell / Terminal — auto-installs uv + Python if needed

irm https://aka.ms/workpilot/install.ps1 | iex

Run wp for guided setup and enterprise GitHub Copilot sign-in. Use wp chat for the terminal, wp serve for the Web Console, or wp cloud for Teams and Cloud Web. Cloud access also requires Microsoft sign-in. Rerun the bootstrap command to upgrade.

Full documentation: aka.ms/workpilot/docs

Illustrative local-first setup below. Cloud and MCP connections are optional; available integrations and consent prompts vary by environment.

Add WorkPilot to Microsoft Teams

Connect your local instance to the Cloud Gateway, then install the Teams app. Tenant policy or administrator consent may be required.

wp teams install

Or download: teams-app.zip → Teams → Apps → Upload a custom app.

To remove: run wp teams uninstall, or in Teams → Apps → Manage your apps → remove WorkPilot.

Get on the Cloud Gateway allowlist

Hosted Teams & Web Chat are in preview — open a request to get on the allowlist, or join our Teams thread to read the details.

How the agent runs on your device

Messages from each channel pass through the local message bus to the agent. Tool calls go through permission checks, risk assessment, execution, and output checks.

Channels Message bus Agent loop Extensible tooling Governed gate Models (endpoints) Cloud & external servers
Channels outside the loop CLI Cloud relay stateless relay Teams Web Chat Your device the whole agent runs locally Message bus Inbound admits sends Events typed pub/sub Outbound returns answers send reply send reply Agent loop · reason ⇄ act Tool sources extensible · governed by the gate admit research · prime context light · optional Context assembly • system prompt • memory facts • relevant history (auto-injected) • recent messages Memory facts · sessions compaction · loop feeds LLM Provider reason · decide · call prompts + context → ← tokens stream back tool calls cleared repeat until final answer publishes final answer → bus Tool calls — governed & executed · no bypass Preflight e-stop · permissions · risk 0–10 · approve Execute runs in parallel Postflight leak-scan · append-only audit Branch 1 Dynamic tools loaded on demand Always-on core + on demand expands as needed Branch 2 Sub-agents spawned + delegated FileSearch HistorySession Copilot Claude Support Branch 3 Skills markdown workflows SKILL.md bundled · project Procedures install from multiple stores reusable playbooks Branch 4 MCP open protocol many servers hundreds of tools → External servers behind the gate untrusted by default Models Endpoints Fallback your provider · primary + fallback your provider · your tenant External servers Microsoft work ecosystem · via MCP Incidents Kusto DevOps Graph Teams / Outlook … SharePoint reached through the governed MCP tools untrusted · always behind the gate reaches out Channels outside the loop CLI Cloud relay stateless relay Teams Web Chat ↓ both channels send into the device's inbound bus ↓ Your device bus + agent loop Message bus Inbound Events typed pub/sub Outbound admit final answer → bus Agent loop · reason ⇄ act research · prime context light · optional Context assembly system prompt memory facts relevant history recent messages Memory facts · history sessions compaction loop detect LLM Provider reason · decide · call Models Endpoints primary · fallback ↑ ↓ tool calls cleared repeats Tool calls — governed & executed · no bypass Preflight e-stop · permissions · risk 0–10 · approve Execute runs in parallel Postflight leak-scan · audit cleared results Tool sources · the gate runs each one Branch 1 · Dynamic tools loaded on demand always-on core + standard tools, activated as needed Branch 2 · Sub-agents FileSearch · HistorySession · Support · Copilot · Claude scoped helpers · restricted · results return to the loop Branch 3 · Skills markdown workflows SKILL.md — bundled · project · install from multiple stores Branch 4 · MCP open protocol many servers · hundreds of tools connected on demand · untrusted by default links to External servers ↓ — every reach-out is gated reaches out External servers Microsoft work ecosystem · via MCP Incidents Kusto Azure DevOps Graph Teams / Outlook SharePoint … reached through the governed MCP tools untrusted · always behind the gate

The message bus connects local and cloud channels to the agent. Tool calls go through checks, execution, and audit. Conversation records and memory files stay on your machine; prompts and tool content are sent to the configured models, services, and channels. The optional cloud relay does not store conversations.

Handling long tasks and conversations

How WorkPilot manages context, tool calls, and permissions during longer sessions.

// the agent loop
Thinks before it actsPrimes context from your workspace and memory before the first token.
Parallel, safelyPreflight → concurrent execute → postflight; repeated calls to the same tool run in order.
Catches itselfLoop detection (repeat · poll · ping-pong) course-corrects mid-run.
// context & memory
Context that lastsContext compaction helps keep long conversations within the selected model's limits.
Learns what mattersSearchable long-term memory; unused facts fade, affirmed ones reinforce.
Lean tool schemaOn-demand tool loading keeps unused schemas out of the prompt.
// models, your way
Your configured modelsChoose the providers and models your organization permits, and switch per task.
Adapts per taskReasoning depth auto-tuned; vision switches on for attachments.
Change direction mid-taskAdd instructions or change direction while a task is running, without waiting for it to finish.
// governance & infra
Deterministic risk scoringMost shell operations are scored by fixed rules, without another model call.
Decoupled by designTyped message bus, bounded queues, a 3-phase hook pipeline.
Inspectable, not a black boxMemory, config, and history are plain text you can read, version, and audit.

Ready to try it?

One command to install. WorkPilot runs on your machine.