docs/adapters/archive/design
adapters archive: design guide
These documents capture design proposals and exploratory specifications that are not part of the current normative reference set.
Pages in this section
Start with the section hub, then move sideways into adjacent pages when you need more detail.
Extend adapters to support multiple adapter types beyond subprocess-based execution. This enables integration with sophisticated tools that provide HTTP APIs, WebSocket interfaces, or direct SDK access.
wiki/docs/adapters/archive/design/18-multi-adapter-architecture.md
This design proposal covers adding kanban and workspaces views to packages/adapters/tui as a thin presentation and command layer over existing packages/kanban and packages/adapters/core seams.
wiki/docs/adapters/archive/design/20-tui-kanban-workspaces.md
adapters launch is a CLI command that launches (or resumes) an interactive or non-interactive coding agent session with full stdin/stdout passthrough. Unlike adapters run, which parses and normalizes agent output into the AgentEvent stream, adapters launch acts as a transparent proxy — the user interacts directly with the harness as if they invoked it natively.
wiki/docs/adapters/archive/design/launcher.md
adapters-proxy is a lightweight Python package that bridges between LLM transport protocols. Each instance serves a single purpose: accept requests in one protocol format (the exposed transport) and forward them to a target provider in its native format, translating between the two using LiteLLM(https://github.com/BerriAI/litellm) as the translation engine.
wiki/docs/adapters/archive/design/provider-adapter.md
adapters archive: design
These documents capture design proposals and exploratory specifications that are not part of the current normative reference set.
Use them for historical context, not as the source of truth for current behavior.