microsoft/amplifier-bundle-work

microsoft/amplifier-bundle-work

Description: Work bundle for the Amplifier project

Language: Python

License: MIT

Stars: 0

Forks: 0

Open issues: 0

Created: 2026-09-21T00:16:29Z

Pushed: 2026-09-26T05:33:38Z

Default branch: main

Fork: no

Archived: no

README:

Amplifier Work

A small, provider-neutral bundle for working with a live Amplifier host. It combines background delegation, visible boundary compaction, transcript retrieval, and filesystem, shell, and search tools. The host supplies credentials, approvals, canonical history, live input, and presentation.

This repository and the loop dependency are private during development. Normal GitHub access is required. No credentials are included in the bundle.

Select the bundle

Use this source as a conversation's root bundle:

git+https://github.com/microsoft/amplifier-bundle-work@main#subdirectory=bundle.md

The bundle and its module sources follow main, so host ecosystem updates can advance them together. Hosts should stage and validate updates before activation and retain the installed revisions for rollback. A local checkout can also be selected by its absolute bundle.md path.

The root contributes nine tool modules, including apply_patch, delegate, read_transcript, load_skill, managed bash, tool_exec, web_search and web_fetch. Modules may expose more than one callable tool. It does not select a provider, model, or reasoning effort. Other capabilities must be composed explicitly.

Extend an existing bundle

Compose the behavior last to retain the existing provider and tool configuration:

includes:
- bundle:
- bundle: git+https://github.com/microsoft/amplifier-bundle-work@main#subdirectory=behaviors/work-local.yaml

The behavior selects managed context and adds transcript retrieval while preserving the host's orchestrator. It does not install the root's filesystem, shell, search, or delegate tools. Its sources follow main through the host ecosystem updater.

To also select Work's live loop, compose bundles/work-session.yaml from your root instead. That standalone composition includes the same behavior and supplies the orchestrator. Work and Anchors + Work already use it; their effective execution settings are unchanged. Existing consumers of behaviors/work-local.yaml that relied on it to select the loop should move that root include to bundles/work-session.yaml.

Behavior and boundaries

• Eligible delegate calls run in the background only with async: true.

A pending receipt is not a completed result; live_job provides result and cancellation controls. Waiting can wake for user input.

• The root enables self-delegation with agent: self and excludes recursive

delegation from children. Four pending jobs is a per-loop limit.

• On hosts that support effective model inheritance, children follow the parent's

selected model and reasoning settings unless an explicit override applies.

• Context preparation pauses at a request boundary for a continuation summary,

configured to trigger at 70% of the budget and target 1,500 summary tokens. Recent work and pending operation references remain available. Original admitted history belongs to the host and can be retrieved with read_transcript.

• The host owns actual concurrency, event delivery, and recovery. A finite host

stays finite; this bundle alone does not create a concurrent user interface.

• Patch editing reuses the existing filesystem bundle's patch module. Its native

operation schema also works as a function tool for other providers. Hosts must apply their shared write policy to both filesystem and patch tools; the portable module itself defaults to the session workspace and follows symlinks before checking its configured allow/deny lists. Adding a tool is not permission to bypass a denied write.

• Conversation search, application actions, artifact presentation, and worker controls

are discovered from the host when present. The root does not emulate those application services or assume every host supplies them.

The root and Anchors preset also include behaviors/work-execution.yaml, which adds managed Bash handles, tool_exec, and real DDGS web search. This behavior preserves the host's orchestrator. The complete Work and Anchors roots enable approved programmatic dispatch through their orchestrator configuration; other compatible roots can explicitly opt in with session.orchestrator.config.programmatic_dispatch: true. The standalone bundles/work-session.yaml keeps its existing loop defaults. The lightweight work-local.yaml overlay remains limited to context and transcript retrieval; include work-execution.yaml for the additional tools. Existing tool safety policies still apply. Raw interpreter stdin requires an unrestricted trusted host policy. Explicitly requested PTYs are supported on POSIX hosts when the mounted Bash module and host policy permit them. Process handles do not remain live after their owner exits; inspect retained operation evidence rather than replaying an uncertain effect.

Programmatic JavaScript runs in a fresh bounded process and calls only through normal tool permissions, with attributable call receipts. It cannot delegate, run background calls or retain variables. Durable operation records, asynchronous questions, saved task state and derived compaction persistence are optional host services discovered through shared actions. Unknown effects are never replayed. This composition alone is not evidence of ChatGPT output-quality parity.

This change requires the managed-process, truthful-web and approved-dispatch upstream changes to be merged before publication. Draft integration uses reviewed local overrides; maintained sources stay on main. Tested revision receipts are evidence, never source pins. See docs/EXECUTION-VALIDATION.md for acceptance state.

Work skill library

The root and Anchors + Work preset include 33 on-demand skills: documents, PDF, presentations, spreadsheets, live Excel guidance, visualization, template creation, integration management, five core authoring/research/image workflows, and 20 original reference templates. Use load_skill or a host's /skill-name support. Work owns 32 skill bodies; the canonical imagegen bundle supplies the remaining imagegen skill through its skill-only behavior. The default Work root does not mount an image generator. The library is discovered...