Skip to content

Plan ACP agent chat integration#241

Draft
mariusvniekerk wants to merge 8 commits into
mainfrom
acp-agent-chat-design
Draft

Plan ACP agent chat integration#241
mariusvniekerk wants to merge 8 commits into
mainfrom
acp-agent-chat-design

Conversation

@mariusvniekerk

Copy link
Copy Markdown
Collaborator
  • Add an ACP-backed chat design for workspace sessions with detachable ambient-sidebar boundaries
  • Define protocol lifecycle, server APIs, persistence, permissions, and safety rules
  • Capture composer autocomplete, process indicators, tool-call grouping, and GFM chat rendering

@roborev-ci

roborev-ci Bot commented May 3, 2026

Copy link
Copy Markdown

roborev: Combined Review (91a341a)

No Medium, High, or Critical issues found.

All reviewers agree the change is clean.


Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

@roborev-ci

roborev-ci Bot commented May 21, 2026

Copy link
Copy Markdown

roborev: Combined Review (91a341a)

No Medium, High, or Critical findings were reported.

All review agents reported no actionable issues at or above Medium severity.


Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

@roborev-ci

roborev-ci Bot commented Jun 1, 2026

Copy link
Copy Markdown

roborev: Combined Review (91a341a)

No issues found.


Synthesized from 2 reviews (agents: codex | types: default, security)

mariusvniekerk and others added 7 commits June 29, 2026 08:32
Document the ACP-backed chat architecture for workspace sessions, including the detachable frontend boundary needed for future ambient sidebar use. Capture protocol lifecycle, API shape, storage, permissions, and testing scope before implementation planning.
Tighten the ACP chat design before implementation by adding acceptance criteria, server-owned workspace cwd validation, a normalized event contract, staged rollout tasks, API generation expectations, and resource/redaction constraints.
Capture composer support for @ file mentions and / skill suggestions in the ACP chat design, including scoped suggestion APIs, prompt conversion behavior, rollout slices, and tests.
Update the ACP chat design so session/update plan entries become durable process indicators with normalized task status, aggregate progress, UI surfaces, rollout steps, and tests.
Document collapsed grouping for successive ACP tool calls, including individual persistence, first-two/last-two default rendering, expansion behavior, aggregate status, and tests.
Document sanitized GitHub Flavored Markdown rendering for ACP chat messages, including table support, overflow behavior, structured event separation, and frontend tests.
ACP has added stable session lifecycle, metadata, command, and config-option surfaces since this design was written. The plan now accounts for session list/resume/close/delete capabilities, session_info_update, available_commands_update, config_option_update, and current tool-call patch semantics so future implementation slices do not bake in stale protocol assumptions.

The tool-call section also calls out the ACP v2 draft direction as compatibility guidance because agents may already send update-only tool-call streams.

Validation: git diff --check

Generated with Codex
Co-authored-by: Codex <codex@openai.com>
@mariusvniekerk mariusvniekerk force-pushed the acp-agent-chat-design branch from 91a341a to 0feaa58 Compare June 29, 2026 12:41
@roborev-ci

roborev-ci Bot commented Jun 29, 2026

Copy link
Copy Markdown

roborev: Combined Review (0feaa58)

No issues found.


Panel: ci_default_security | Synthesis: codex | Members: codex_default (codex/default, done, 2m29s), codex_security (codex/security, done, 7s) | Total: 2m36s

The previous spec refresh relied on the published ACP docs but did not exercise the installed codex-acp adapter. Local validation against codex-acp 0.16.0 showed that initialize advertises loadSession, session list/resume/close, prompt, MCP, and auth capabilities, while session configuration arrives from session/new rather than an initialize capability.

The transport guidance now preserves ACP newline-delimited writes while requiring the reader to tolerate complete JSON responses that are not newline-terminated, which matches the observed codex-acp initialize response.

Validation: codex-acp initialize, session/new, session/close, and session/list smoke tests; git diff --check

Generated with Codex
Co-authored-by: Codex <codex@openai.com>
@roborev-ci

roborev-ci Bot commented Jun 29, 2026

Copy link
Copy Markdown

roborev: Combined Review (33818df)

No issues found.


Panel: ci_default_security | Synthesis: codex | Members: codex_default (codex/default, done, 26s), codex_security (codex/security, done, 15s) | Total: 41s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant