Terok executor
terok_executor
¶
terok-executor: single-agent task runner for hardened Podman containers.
Builds agent images, launches instrumented containers, and manages the
lifecycle of one AI coding agent at a time. Designed for standalone use
(terok-executor run claude .) and as a library for terok orchestration.
The public surface is __all__ below. Key entry points:
AgentRunner— launch agents in containersAuthenticator— credential flowImageBuilder— image constructionAgentRoster.shared— YAML agent registry (process-wide cache)
Every public name is served lazily (PEP 562 __getattr__): the
submodule that defines a symbol is imported only when that symbol is
first accessed, so a bare import terok_executor pays for neither the
acp protocol stack nor terok_sandbox until something actually
reaches for a symbol that needs them. The three ACP names
(ACPEndpointStatus,
acp_socket_is_live,
list_authenticated_agents)
are deliberately kept off the roster-bootstrap path so the host-side
acp list probe stays cheap.
Implementation-detail types (raw config schema fragments, ACP error
classes, internal result types, sidecar image / inject helpers) stay
in their submodules; reach into terok_executor.<sub> when you
need them.
__version__ = _meta_version('terok-executor')
module-attribute
¶
__all__ = ['__version__', *_LAZY]
module-attribute
¶
__getattr__(name)
¶
Resolve a public name to its defining submodule on first access (PEP 562).
A "module:attr" target renames on the way through — the sole
aliased export is AGENT_COMMANDS, which is COMMANDS in
.commands (COMMANDS at the package
root is the composed tree from ._tree).