Expand description
§teksilo-automation
GUI-free runtime-introspection & automation toolkit for Teksilo apps.
A Teksilo app exposes a rich semantic surface — the AccessKit
accessibility tree — plus an AT-action dispatch path, both of which are
queryable and drivable in-process, without the OS accessibility
layer. This crate turns that latent capability into a small set of
serde DTOs plus one core function, execute, that an MCP server (or
any other harness) marshals operations to.
execute(tree: &mut WidgetTree, ops: &mut dyn WindowOps,
op: &AutomationOp, settle: &SettleSpec) -> AutomationReplyThe wire protocol is serde DTOs, never closures or !Send handles
(dto). WidgetTree is !Send, so it
lives on exactly one thread; async / socket layers marshal Send DTOs
to it. Two operations need context execute doesn’t hold —
list_windows (the window manager) and screenshot (a GPU / platform
window) — and return dto::codes::HOST_REQUIRED; the headless server
and the live bridge serve those themselves. live_image_stats is half
the host’s: execute reports the source and the attachment, and the
host adds its window’s textures and wakes with with_window_stats; a
screenshot’s live pictures come from live_image_shots.
This crate has no GUI, render, platform, or async dependency. It mirrors
teksilo-data’s “core-only peer” design so a CI harness, a headless
test, or the live in-app bridge can all share it.
§Modules
client— finding the MCP client binary, and the install command to name when it is absent.dto— the serde wire protocol.executor—executeand the settle model.recording_ops— a non-panickingWindowOpsfor the headless server.mcp_schema— the canonical tool catalog.wire— the live-bridge framing, token handshake and endpoint discovery, shared verbatim by the in-app bridge and the MCP client.
Re-exports§
pub use client::CLIENT_BIN;pub use client::CLIENT_VERSION;pub use client::find_client;pub use client::install_command;pub use dto::AnnouncementDto;pub use dto::Assertion;pub use dto::AssertionResult;pub use dto::AutomationOp;pub use dto::AutomationReply;pub use dto::AutomationRequest;pub use dto::DensityDto;pub use dto::LayoutNode;pub use dto::LiveImageAttachmentStatsDto;pub use dto::LiveImageMapReply;pub use dto::LiveImageShot;pub use dto::LiveImageSourceStatsDto;pub use dto::LiveImageStatsReply;pub use dto::LiveTextureStatsDto;pub use dto::LiveWakeStatsDto;pub use dto::NodeBounds;pub use dto::NodeRef;pub use dto::PointerAction;pub use dto::PointerButtonDto;pub use dto::PointerKindDto;pub use dto::PointerReport;pub use dto::ScreenshotMeta;pub use dto::SemanticNode;pub use dto::SequenceMemberDto;pub use dto::SettleSpec;pub use dto::ShortcutInfo;pub use dto::TouchPhaseDto;pub use dto::TouchSequenceReport;pub use dto::TouchStep;pub use dto::TouchStepReport;pub use dto::WaitCondition;pub use dto::WindowInfo;pub use dto::codes;pub use executor::execute;pub use executor::live_image_shots;pub use executor::run_settle;pub use executor::with_window_stats;pub use mcp_schema::TOOL_CATALOG;pub use mcp_schema::TOOL_COUNT;pub use mcp_schema::ToolDescriptor;pub use recording_ops::RecordedWindow;pub use recording_ops::RecordingWindowOps;pub use wire::Endpoint;pub use wire::EndpointFile;pub use wire::Transport;
Modules§
- client
- Finding the MCP client, and saying how to get it when it is missing.
- dto
- Serde data-transfer objects — the entire automation wire protocol.
- executor
- The single core function that performs every automation operation
against a live
WidgetTree. - mcp_
schema - The canonical catalog of automation tools — one entry per MCP tool.
- recording_
ops - A
WindowOpsimplementation for the headless server. - wire
- The live-bridge wire protocol, and how a client finds a bridge to talk to.