Kaelio/ktx (YC X25)
Built and integrated a Google Drive context-source adapter for ktx so Google Docs from a configured Drive folder could be ingested into the platform's context pipeline.
Overview
Implemented end-to-end Google Drive support for ktx by adding a new `gdrive` adapter, wiring service-account-based authentication, integrating setup and ingest flows, adding connection testing, and documenting the feature for users.
01
Context
ktx did not support Google Drive as a context source, so teams could not ingest Google Docs into the platform's context pipeline even when operational knowledge already lived there.
The requested feature needed more than an API connector because it also required authentication handling, config/schema support, CLI integration, tests, and user-facing documentation to fit the repository's existing ingestion model.
02
Implementation
Built a new `gdrive` context-source adapter that ingests native Google Docs from a configured Drive folder and converts them into Markdown while preserving structure such as headings and lists.
Integrated Google Drive API and Google Docs API access using service-account authentication, with support for `service_account_key_ref` via `file:/path/to/key.json`.
Wired `gdrive` into connection schema validation, CLI setup, connection testing, and ingest flows so the source could be configured and used end to end within the project.
Added tests and integration docs covering setup, required API scopes, and expected behavior, and fixed cross-platform path handling needed for Windows ingest reliability.
03
Impact
Extended the platform with a real document-ingestion surface by making Google Docs usable as context input inside the broader ktx workflow.
Delivered a production-style open-source feature across adapter logic, auth, config, CLI UX, docs, tests, and Windows reliability instead of limiting the contribution to a narrow connector implementation.