Repository navigation
Extract the Agent package from Core - #1343
Merged
Merged
Conversation
taras
force-pushed
the
codex/extract-agent-first
branch
from
November 15, 2026 23:19
36706f9 to
4e763c3
Compare
taras
marked this pull request as ready for review
November 15, 2026 23:23
taras
force-pushed
the
codex/extract-agent-first
branch
from
November 16, 2026 00:15
4e763c3 to
93e48cb
Compare
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
force-pushed
the
codex/extract-agent-first
branch
from
November 16, 2026 02:10
93e48cb to
74238ac
Compare
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>
4 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
deno task verify:cleanexercises 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.