8000 feat(agent): add application topology and execution services by Fodesu · Pull Request #97 · felinics/twilight · GitHub
[go: up one dir, main page]

Skip to content

feat(agent): add application topology and execution services - #97

Closed
Fodesu wants to merge 2 commits into
feat/agent-runtime-storagefrom
feat/agent-runtime-app
Closed

Fodesu wants to merge 2 commits into
feat/agent-runtime-storagefrom
feat/agent-runtime-app

Conversation

@Fodesu
@Fodesu Fodesu commented Oct 3, 2026 •
Copy link
Copy Markdown
Member

Summary

Adds the application topology that composes the runtime, owner, stores, model/tool backends, workers, session APIs, and HTTP surfaces into a usable agent service. The agent/app package is the orchestration boundary; components remain replaceable behind explicit interfaces.

Design

Application activation resolves a session, obtains or creates its owner, drains durable inbox commands, and connects the owner to the runtime and Loop. Component constructors wire stores, model backends, tool backends, executor workers, and local/cloud implementations without moving their state machines into the app package. Session helpers expose submission, Turn lifecycle, compaction, fork, restart, and workspace operations while preserving command idempotency and projection-backed reads.

The executor topology includes local and HTTP backends, a sandbox, backend client/server bindings, and the model/tool/worker component wrappers. Tool definitions and model catalogs are resolved through application configuration; the executor still receives frozen Assignments and returns effect outcomes. spawn and responder code adapt model responses into the Loop’s decision boundary rather than writing Run facts directly.

The HTTP server/client wire carries application commands, session state, progress, and terminal results. Progress is forwarded as observation, while committed events and durable state remain authoritative. Activation and restart paths use the same persisted session and Run stores, so a process restart does not require reconstructing in-memory conversation or execution state.

Testing

The branch contains extensive app, HTTP, component, executor-local/HTTP/sandbox, model catalog, spawn, tool, lifecycle, compaction, fork, restart, target, Turn, workspace, and cloud-test coverage. These tests exercise the composition and public application boundaries rather than introducing a second state machine.

@Fodesu
Fodesu added this pull request to stack #105 October 3, 2026 12:27
@Fodesu Fodesu changed the title feat/agent runtime app feat(agent): add application topology and execution services Oct 3, 2026
@Fodesu
Fodesu force-pushed the feat/agent-runtime-storage branch from d8dc29d to 555de6c Compare October 3, 2026 14:43
@Fodesu
Fodesu force-pushed the feat/agent-runtime-app branch from 9e02f30 to 295c20c Compare October 3, 2026 14:43
@Fodesu
Fodesu force-pushed the feat/agent-runtime-storage branch from 555de6c to 2e9c81e Compare October 3, 2026 14:55
@Fodesu
Fodesu force-pushed the feat/agent-runtime-app branch from 295c20c to 3ed0256 Compare October 3, 2026 14:55
@Fodesu
Fodesu force-pushed the feat/agent-runtime-storage branch from 2e9c81e to a547492 Compare October 3, 2026 15:35
@Fodesu
Fodesu force-pushed the feat/agent-runtime-app branch from 3ed0256 to 3b38372 Compare October 3, 2026 15:35
@Fodesu
Fodesu removed this pull request from stack #105 October 3, 2026 16:13
@Fodesu
Fodesu added this pull request to stack #107 October 3, 2026 16:16
@Fodesu
Fodesu removed this pull request from stack #107 October 3, 2026 16:34
@Fodesu
Fodesu deleted the branch feat/agent-runtime-storage October 3, 2026 16:34
@Fodesu Fodesu closed this Oct 3, 2026
@Fodesu
Fodesu deleted the feat/agent-runtime-app branch October 5, 2026 07:37
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

0