docs: AW harness design plan (Pi SDK + extensions)#29667

Merged

pelikhan merged 15 commits intomainfrom

pelikhan/aw-harness-plan

May 2, 2026

Commits on May 2, 2026

docs: add AW harness design plan

pelikhan
and
Copilot
committed
docs: gh-proxy and cli-proxy always enabled for engine: aw (Pi SDK no native MCP)

Copilot
and
pelikhan
authored
docs(specs): rewrite aw-harness.md in W3C specification format

Copilot
and
pelikhan
authored
docs(specs): address review feedback on aw-harness W3C spec

Copilot
and
pelikhan
authored
docs: add §6.4 initial prompt context — no predefined context, all imports must be declared

Copilot
and
pelikhan
authored
docs: remove mcp-bridge extension; harness reads compiler-generated config.json+prompt.txt

Copilot
and
pelikhan
authored
docs: remove --agent-file flag; direct provider env vars; no harness key; rename steps→tasks

Copilot
and
pelikhan
authored
Merge remote-tracking branch 'origin/main' into pelikhan/aw-harness-plan
Copilot
authored
docs: skills must be declaratively imported via imports: key

Copilot
and
pelikhan
authored
docs: remove subagents - simplify aw-harness to single-session execution

Copilot
and
pelikhan
authored
docs: add context observability section to aw-harness spec

Copilot
and
pelikhan
authored
docs: add §4.3 Pi SDK and OpenClaw extension format compatibility

Copilot
and
pelikhan
authored
docs: remove OpenClaw section; add harness.extensions for user Pi extensions

Copilot
and
pelikhan
authored
docs: remove openclaw section, add piagent extensions support, fix budget/safe-outputs design

Copilot
and
pelikhan
authored
docs: fix code review issues - duplicate diagram entry, sequential numbering

Copilot
and
pelikhan
authored

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docs: AW harness design plan (Pi SDK + extensions)#29667

docs: AW harness design plan (Pi SDK + extensions)#29667
pelikhan merged 15 commits intomainfrom
pelikhan/aw-harness-plan

Commits on May 2, 2026

docs: add AW harness design plan

docs: gh-proxy and cli-proxy always enabled for engine: aw (Pi SDK no native MCP)

docs(specs): rewrite aw-harness.md in W3C specification format

docs(specs): address review feedback on aw-harness W3C spec

docs: add §6.4 initial prompt context — no predefined context, all imports must be declared

docs: remove mcp-bridge extension; harness reads compiler-generated config.json+prompt.txt

docs: remove --agent-file flag; direct provider env vars; no harness key; rename steps→tasks

Merge remote-tracking branch 'origin/main' into pelikhan/aw-harness-plan

docs: skills must be declaratively imported via imports: key

docs: remove subagents - simplify aw-harness to single-session execution

docs: add context observability section to aw-harness spec

docs: add §4.3 Pi SDK and OpenClaw extension format compatibility

docs: remove OpenClaw section; add harness.extensions for user Pi extensions

docs: remove openclaw section, add piagent extensions support, fix budget/safe-outputs design

docs: fix code review issues - duplicate diagram entry, sequential numbering