searchDocs
Search Extentos conceptual docs by topic or keyword to understand how SDK primitives compose into real flows and how features are meant to be used.
Instructions
Search Extentos documentation by topic or keyword. The conceptual / narrative layer that complements the action-oriented tools — read these to understand how the SDK is meant to be used, not just what calls exist. Canonical post-pivot topics: getting_started (full topic index — read first), custom_handlers (the central composition doc — how to write a Handler class that subscribes to capability primitives), assistant_runtime (the canonical voice-assistant surface; read first if you're building a voice assistant), voice_integration (lower-level primitives — glasses.voice.onPhrase + audio.recordDiscrete + customer-side LLM; for fine-grained control), connection_ui_placement, host_app_scaffold, auto_bind_session_lifecycle, local_bridge_discovery, device_code_flow, connection_state_model, permissions, production_checklist, concurrency_modes, multi_platform_projects, library_api, toggles, audio_video_coexistence, simulator_browser_mode, simulator_session_lifecycle (mint once, reuse, delete deliberately — read before minting a second sim for a project), event_log_schema, file_actions, agent_e2e_testing (how an AI coding agent verifies its own generated handler end-to-end — sim event log + adb-mediated emulator DB read + screencap, the dual-layer pattern that closes the agent loop without a human). Topic IDs are stable. At least one of topic or query is required (enforced by the handler — calling with neither returns an invalid_arguments error). Pass topic alone to fetch the full topic content (most common); pass query alone for keyword search across all topics; pass both to narrow keyword search inside a topic. mode: "snippets" returns only the matching paragraphs instead of full topic bodies — pair with a query when keyword-searching across topics so a single search doesn't dump ~20KB of unrelated content into context. USE to learn how primitives compose into a real flow, or to read up on a specific feature (permissions, toggles, connection lifecycle). DON'T USE for the platform capability list (use getPlatformInfo), call-shape per feature (use getCapabilityGuide), or project-installed state (use inspectIntegration).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Response shape. 'full' (default) returns each matching topic's full body — the original behavior, best for reading a single named topic. 'snippets' returns only the paragraphs containing the query terms (up to 3 per topic, ~600 chars each) — best when querying across topics so you don't pay for unrelated content in the agent's context window. Snippets mode requires a query; pure topic fetches always return full content. | |
| query | No | Optional keyword(s). When omitted, the response is the full content of the topic named in `topic`. When both supplied, query narrows within the topic. At least one of `query` or `topic` must be supplied. | |
| topic | No | Optional topic id. Omit and pass `query` for cross-topic keyword search; pass topic alone to fetch the topic's full content (most common usage). At least one of `query` or `topic` must be supplied. |