Amplifier Unified is a local, authenticated workspace for Amplifier. It provides a web app for chat, voice, and work with your configured Amplifier bundles and tools.
The chat input formats Markdown as you type: **bold**, _emphasis_, headings
with # , and lists with * or 1. . Press Enter to send, or Shift+Enter
or Ctrl+Enter to continue writing. In a list, these continue the list;
Backspace at the beginning of an empty item returns to a paragraph.
Undo and redo work as usual. Pasted images remain attachments, and pasted text
longer than 10,000 characters becomes a Pasted text attachment.
In Settings → Appearance, enable Collapse interim replies to move earlier assistant updates into the existing work details after a confirmed final response. It is off by default and applies to this browser. Expand the disclosure to read, copy, or reply to those messages; exports retain the complete conversation. The explicit option also collapses these groups at the Everything detail level, but preserves details you opened manually. Active, interrupted, or unqualified older turns remain visible. Turning the option off restores normal placement.
On a fresh Ubuntu or Debian computer (including WSL), first install the download prerequisites together:
sudo apt-get update && sudo apt-get install -y curl git ca-certificatesOn macOS, install Apple's command line tools if Git is not already available:
xcode-select --install. Other Linux distributions need curl, Git, and CA
certificates from their package manager.
Then, for macOS and Linux (including WSL with systemd), paste this into your terminal:
curl -fsSL https://raw.githubusercontent.com/microsoft/amplifier-unified/main/scripts/install.sh | bashThe installer finds or installs uv and Python, verifies the latest stable release, installs Unified, starts its per-user service, and opens your browser. Git and curl must be available. Existing Amplifier CLI configuration, accounts, and history are kept. Run the Amplifier installer as your normal user, without sudo. You do not need to install uv or Python yourself, reopen your terminal, or reboot.
For more detail, add -s -- --verbose after bash. Use --version 0.20.101
for a specific stable release or --no-open to print the address without opening
a browser. Installation logs are private and their location is printed.
In the web app, connect an AI account if needed. You can finish setup with an assistant alongside Settings, or go straight to a new chat. Component preparation continues there with expandable details; errors remain visible for review.
To manage prerequisites and package installation yourself, use the instructions below. These use Python 3.13+ and uv.
Linux
Install Unified, then set it up as a background service:
uv tool install git+https://github.com/microsoft/amplifier-unified@v0.20.101
amplifier-unifiedOpen http://127.0.0.1:8941 and sign in with the account that runs Unified.
Windows with WSL
Use a Linux distribution in WSL with systemd enabled. In the WSL distribution,
add this to /etc/wsl.conf:
[boot]
systemd=trueFrom Windows PowerShell, restart WSL:
wsl --shutdownOpen WSL again, then install Unified and set it up as a background service:
uv tool install git+https://github.com/microsoft/amplifier-unified@v0.20.101
amplifier-unifiedOpen http://127.0.0.1:8941 in your Windows browser and sign in with the account that runs Unified.
macOS
Install Unified, then set it up as a background service:
uv tool install git+https://github.com/microsoft/amplifier-unified@v0.20.101
amplifier-unifiedOpen http://127.0.0.1:8941 and sign in with the account that runs Unified.
The first launch sets up and starts your background service, waits until it responds,
and opens your browser. Later launches reuse it. To run only in the current
terminal, use amplifier-unified serve. Package installation alone does not
register a service. On macOS, the background activity notification confirms
registration; the launcher separately checks that the app responds.
The first message can take a few minutes while Unified prepares its runtime.
After installation, open Settings → Updates to check for and install updates, review any failed checks, or choose the automatic check interval. See the update guide for active-work handling and recovery details.
For opt-in, read-only local observations shared with CLI tools, see the status emitter guide. Publication is disabled by default.
Ordinary conversations compose Unified shell, image generation, Computer Use, full Context Intelligence, and Model Routing over the selected root bundle. Existing explicit capability lists gain the latter four unless opted out; chosen source revisions and list order are retained. Saved snapshot bundles are complete plans and do not gain these additions.
Use Settings → Configured bundles to disable or remove a default. A retained routing-matrix setting does not re-enable a disabled routing behavior. The Context Intelligence opt-out removes its analysis/navigation capabilities; Unified's existing local capture hook remains.
New Computer Use access is read-only. It targets the host computer, not the
browser's shared screen. Explicit module configuration can enable writes with
overrides.tool-computer-use.config.read_only: false; existing explicit access
settings remain authoritative. Child sessions cannot widen a parent's desktop
restrictions.
Context Intelligence forwarding requires explicit destination configuration;
ambient server credentials alone do not enable it. Explicit routing matrices,
agent provider choices, and per-delegation model pins take precedence over
default role routing. When only automatically added routing has no candidate,
the child inherits the conversation's selected provider, model, and effort
(retaining that snapshot on resume). If there is no selected model to inherit,
the delegation fails visibly. Explicit matrices, including an explicitly chosen
balanced matrix or a user-authored override, remain strict, as do unavailable
provider/model pins and resolver errors. A saved explicit app-behavior list is
treated as explicit routing when its original intent is ambiguous.
An effective-plan edit containing hooks also makes routing explicit, even if
the hook values are unchanged. A custom child orchestrator that cannot apply the
inherited selection fails visibly rather than substituting another model.
For ordinary roots already including the upstream logging behavior, its ambient
URL/key placeholders alone no longer opt into forwarding; configure a destination
or explicit scoped legacy URL/key settings. An explicit empty destination map
still disables forwarding. A named agent's explicit provider/model pin also
outranks a call's role-based default; pass explicit provider_preferences to
override that pin. Snapshot roots retain their saved composition and prior
routing lifecycle rather than adopting this ordinary-root policy.
You can add Unified to a desktop or mobile device as its own app-like window or home-screen icon. This does not install or move the Unified service; it opens the same workspace more directly.
After opening Unified in a browser:
- Chrome or Edge: use the install icon in the address bar or the browser's install menu.
- Safari on macOS: choose File → Add to Dock.
- Safari on iPhone or iPad: choose Share → Add to Home Screen.
This works on desktop and mobile platforms supported by your browser. Unified must keep running at the same address.
Set up access from another device
Unified listens only on 127.0.0.1:8941 by default. To use it from another
device, configure trusted HTTPS with the exact address you will use:
amplifier-unified config set public_origins '["https://your-host.tailnet.ts.net:8941"]'
amplifier-unified setup-tls
amplifier-unified config set bind '["100.64.0.10", "127.0.0.1"]'
amplifier-unified doctorReplace the example origin and Tailscale IP with your host's real addresses. Before opening the remote address, export Unified's public CA on the host, verify its fingerprint with amplifier-unified setup-tls status, and trust that CA on each device. Do not disable certificate checks.
For the complete setup—including certificate transfer and trust, reverse-proxy limits, and Linux service management—see the deployment guide.
Repair a broken installation
First, get the latest recovery command:
uv tool install --force git+https://github.com/microsoft/amplifier-unified@mainThen preview the repair or run it:
amplifier-unified reset --dry-run
amplifier-unified resetReset reinstalls Unified while keeping your chats, settings, sign-ins, and files.
It handles stopping and restarting the app, then runs the installation and service
checks for you. Allow a few minutes. Public releases do not require GitHub sign-in.
Use reset --anonymous if personal Git configuration or organization sign-in
policy prevents public downloads. More recovery options.
Review the repository privacy guidance before publishing examples, diagnostics or screenshots.
The AHP/ACP architecture design packet describes the proposed protocol boundaries, client-local state, bounded history discovery and repository decomposition. It includes ratified vision/contracts and parallel implementation lanes; it is not a claim about current release capabilities.
Note
This project is not currently accepting external contributions, but we're actively working toward opening this up. We value community input and look forward to collaborating in the future. For now, feel free to fork and experiment!
Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit Contributor License Agreements.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.