Skip to content

Extract the Agent package from Core - #1343

Merged
taras merged 2 commits into
mainfrom
codex/extract-agent-first
Nov 16, 2026
Merged

taras merged 2 commits into
mainfrom
codex/extract-agent-first

Conversation

@taras

@taras taras commented Nov 15, 2026

Copy link
Copy Markdown
Owner

Why

Land the Agent package boundary on its own so the package move can merge before the reply-approval work in #1327 and #1337.

What changes

Agent source and its tests move to packages/agent. Consumers import Agent, provider and session APIs from @executablemd/agent/api, and installers and held-conversation APIs from @executablemd/agent/host. Core stops exporting Agent APIs.

Build tooling carries the Agent documentation into the compiled binary, npm and JSR. The generated release workflow publishes Agent after Core and before its consumers.

Review guide

Start with the new public Agent entries and the package-boundary tests. The six public Core entry points resolve zero Agent modules. The CLI still installs Agent's existing vocabulary. Agent preserves the registered component origin and held-conversation identity used to read existing journals.

How to verify it

  • The Deno Agent suites cover held conversations, Session and Prompt integration, and the package boundary. The focused conversation and boundary suites pass on Node and Bun as well.
  • The same synthetic withheld-reply journey on main and this branch produces seven byte-identical journal records. The candidate reopens the original bytes and continues with one fresh turn.
  • The artifact tests import both Agent entry points from the emitted npm packages and render shipped Prompt documentation in a staged JSR consumer.
  • deno task verify:clean exercises the offline builds and Deno, Node and Bun dependency interference checks from a clean checkout.

Scope

This PR carries the package move, consumer imports, and release wiring. The follow-up carries foreground reply approval, scoped append approval, and generated-source provenance.

@taras
taras force-pushed the codex/extract-agent-first branch from 36706f9 to 4e763c3 Compare November 15, 2026 23:19
@taras
taras marked this pull request as ready for review November 15, 2026 23:23
@taras
taras force-pushed the codex/extract-agent-first branch from 4e763c3 to 93e48cb Compare November 16, 2026 00:15
Move Core's Agent vocabulary, conversation, journal and their tests into
@executablemd/agent with its ./api and ./host entries, and migrate every
consumer to them. The components keep the registered origin
@executablemd/core, the held conversation keeps its exact retained root, and
Prompt records keep their shapes, append order and withheld encoding. Core
gains only the neutral host readers the package needs; the Agent
documentation contribution moves to the Agent package's own installer.

The pending reply review and acceptance work stays out of this change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@taras
taras force-pushed the codex/extract-agent-first branch from 93e48cb to 74238ac Compare November 16, 2026 02:10
@taras
taras merged commit 8c71b35 into main Nov 16, 2026
64 checks passed
@taras
taras deleted the codex/extract-agent-first branch November 16, 2026 03:47
taras added a commit that referenced this pull request Nov 16, 2026
Restack the reviewed #1327 reply approval feature (tree delta
853e862..35dcb34, previously at 88703be) onto main after the Agent
package extraction (#1343), without the #1337 extraction spike.

Agent owns the conversation, reply review, acceptance record and replay
(packages/agent/src/reply-acceptance.ts, reply-review.ts, exported from
@executablemd/agent/host). Core keeps the generic pieces the feature needs:
the accepted-reply copy grants, reply secret location and text checks,
Elicit answer readers, and executeInstalledBound with the evaluator that
takes an AcceptedRootReply, all exported from @executablemd/core/host.
Core imports nothing from the Agent package.

The approval drawer takes precedence over main's Sidekick inspection view,
and the chat projection keeps both main's request reading and the
feature's control outcomes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant