Skip to main content
Knowledge is currently in beta. We’re eager to hear from you - please reach out with feedback or questions.
Clark stores and retrieves memories across conversations. Admins can add memory, and Clark will automatically learn with every builder prompt. This enables Clark to navigate scaled databases, complex SaaS instances, and undocumented APIs as they evolve. You can define knowledge at four levels so Clark always has the right context without you repeating yourself:
  1. Organization — org-wide standards like design systems, coding conventions, and domain terminology
  2. Integration — data source details like schema quirks, query patterns, and API behavior
  3. User — personal preferences for how Clark works with you
  4. App — app-specific architecture, business logic, and UI conventions

​
Platform knowledge vs. app knowledge

Knowledge is split into two categories: Platform knowledge — Organization, Integration, and User knowledge are defined and managed outside of any individual app. They apply across your entire Superblocks environment and are configured by admins (org and integration) or individual users (personal preferences). See Organization Knowledge and Integration Knowledge for setup details. App knowledge — defined within a specific application and scoped to Clark conversations in that app. Builders configure this directly in the app settings. See App Knowledge for details.

​
How knowledge is applied

Clark looks up relevant knowledge on the fly using progressive disclosure — pulling in only the entries that are relevant to what you’re currently working on. You don’t need to reference knowledge in your prompts.
  1. Organization knowledge — always included
  2. Integration knowledge — included when the relevant integration is used
  3. User knowledge — always included for the current user
  4. App knowledge — included when working within the relevant app
Enabling too many knowledge entries at once can reduce Clark’s effectiveness. Keep entries focused and disable any that aren’t actively needed.