Google, Dropbox, GitHub, and Microsoft foundations
Choose a supported storage connection and explicitly map the knowledge you want to make available.
Connect sources and tools through server-owned credentials, narrow scopes, and preview-first external writes.
Start with one useful connection. You choose what it can access; plan and client requirements apply.
Two source updates affect the review date. The existing rationale remains supported by three cited notes.
Choose a supported storage connection and explicitly map the knowledge you want to make available.
Let compatible AI tools retrieve authorized records, or build a scoped integration with the documented API.
Connect an account without exposing its service credentials in your browser.
Markdown remains the canonical knowledge format. Export and local readability do not depend on continuing a paid vertical.
Telemetry records coarse milestones only—never titles, note text, prompts, paths, or learner identifiers.
Connected providers, hosted intelligence, collaboration, APIs, and domain execution depend on plan, configuration, and explicit consent.