Repository navigation
Conversation
Fodesu
force-pushed
the
feat/agent-runtime-deploy
branch
from
October 3, 2026 14:43
8f3b553 to
f846126
Compare
Fodesu
force-pushed
the
feat/agent-runtime-executor-tests
branch
from
October 3, 2026 14:55
2a110c6 to
7fe95bf
Compare
Fodesu
force-pushed
the
feat/agent-runtime-deploy
branch
2 times, most recently
from
October 3, 2026 15:35
1218d16 to
75db257
Compare
Fodesu
force-pushed
the
feat/agent-runtime-executor-tests
branch
from
October 3, 2026 15:35
7fe95bf to
2b34e11
Compare
Fodesu
force-pushed
the
feat/agent-runtime-deploy
branch
from
October 3, 2026 15:47
75db257 to
33ee876
Compare
Fodesu
force-pushed
the
feat/agent-runtime-executor-tests
branch
from
October 3, 2026 15:47
2b34e11 to
06eb7cf
Compare
Fodesu
force-pushed
the
feat/agent-runtime-executor-tests
branch
from
October 3, 2026 16:05
06eb7cf to
84ebc7a
Compare
Fodesu
force-pushed
the
feat/agent-runtime-deploy
branch
from
October 3, 2026 16:05
33ee876 to
1901b24
Compare
Member
Author
|
Removed from stack: deployment entrypoints are not part of this agentcore runtime change. The deployable command packaging will be handled separately. |
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.
Summary
Adds deployable service entrypoints and local manifests for the runtime components: owner, worker, model backend, and tool backend.
Each command is a small process boundary that constructs the corresponding application component and runs its service lifecycle. Keeping these roles in separate binaries matches the runtime topology: the owner coordinates durable session and Run state, the worker executes effect Assignments, and model/tool backends provide the implementation-specific execution capabilities behind the executor contracts.
The local deployment manifests describe the four processes and their configuration shape so the components can be started together without changing application code. The local README documents the intended process arrangement and the environment/configuration inputs needed to run it. The entrypoints leave persistence, ownership, dispatch, and observation semantics to the packages introduced in the preceding stack; they are wiring and lifecycle adapters rather than alternate implementations of those protocols.
This separation also preserves the recovery model. An owner restart can reopen durable state, while worker and backend processes can be replaced independently and reconciled through stable effect keys and execution records. The manifests therefore provide a concrete local topology for testing the same cross-process contracts used by the runtime.
Scope
This is a deployment/documentation PR. It adds commands and local JSON manifests; it does not introduce new event or executor semantics.