Memory and context

KRAIL project knowledge#

KRAIL keeps a project’s knowledge in its repository, next to the work. When a Project already has a KRAIL layout, Floating Keys can read its identity, knowledge folders and capabilities. Reading it does not initialize, repair or run anything; actions that change knowledge remain explicit and follow the Project’s policy.

Knowledge carried into the product is meant to stay reviewable: each record points back to a specific source version and keeps that source’s access rules.

Project snapshots#

A Project intelligence snapshot is a fixed, structural map of a repository at one exact commit, built without checking it out. It records what it could not see — uncommitted changes, shallow history, truncation — and is not a claim of full understanding of the code or the business.

Imported agent history#

You can keep read-only copies of past Codex, Claude Code and Cursor conversations under a Project, so they can be searched and referenced. The original agent still owns its sessions; Floating Keys owns only the copy and who in the Project can see it.

Project discovery works the same way: finding existing agent projects reads only folder, session count and timestamp information, not prompts or replies.

Carrying a conversation into a run#

When you dispatch a message, you can opt in to including the thread’s earlier messages and completed results. It is off by default, because including a private conversation copies it into a run that other Project members may see.

• Earlier results are included with their origin and are marked unverified.
• Failed or cancelled work contributes only its status. Work still in progress blocks the dispatch until it settles.
• Context is bounded. If a conversation is too long, dispatch fails clearly rather than silently dropping messages.
• The agent starts a fresh session with this context. It is not a continuation of the provider’s earlier session.