Technical Spec & Support Boundaries

  1. This page describes what Klawforge supports at launch, what is optional, and which areas are planned for expansion.
  2. The short version: memory capture and recall are vendor-neutral, backups are upward-compatible, and every boundary is designed to expand without invalidating existing memory.

Supported AI models

  • Supported now: Claude-first workflows (Claude Code dogfood verified at launch).
  • In active dogfood: Gemini (Antigravity, Gemini CLI) and GPT (Codex CLI) adapters — beta hardening as the integration layer stabilizes.
  • Planned: additional model families as adapters and retrieval contracts stabilize.
  • Boundary: unsupported models may still work through generic integrations, but they are not part of the launch support guarantee until listed here.

Supported memory backup paths

  • Supported now: upward-compatible local memory backups.
  • Optional now: Google Drive preservation for users who want cloud-drive continuity.
  • Planned: additional cloud-drive targets after the local backup format and restore flow remain stable.
  • Compatibility promise: older backups should remain readable and upgradeable by newer Klawforge versions.

Supported devices and operating systems

  • Device count: unlimited personal devices.
  • Primary launch OS: macOS.
  • Planned OS expansion: Windows and Linux after launch hardening.
  • Boundary: platform-specific installers, signing, and auto-update behavior may differ until each OS is marked launch-ready.

Data and privacy boundary

  • Default storage: local-first memory graph on the user machine.
  • Cloud storage: only when the user chooses a backup/preservation target such as Google Drive.
  • Not part of launch: Klawforge-hosted conversation cloud sync.
  • User control: backups should be exportable, restorable, and forward-compatible across versions.

Integration boundary

  • Supported form factors: native desktop app, CLI/adapter flows, and IDE companion flows where adapters are available.
  • Memory retrieval: graph-first recall using the local memory graph.
  • Roadmap: more hosts, more models, and more backup targets without changing the user-facing memory contract.