Overview
How Floating Keys works
Floating Keys is a workspace where you direct AI agents across your projects. Every piece of work records who asked for it, what it was allowed to touch, what actually happened and whether a person accepted the result.
- Live
- Available to the public on floatingkeys.com today.
- Local
- Implemented in the local desktop app and Core; setup and provider prerequisites apply.
- Partial
- Some pieces exist, often only for invited accounts; the full experience is still being built or verified.
- Planned
- A design target. Not available yet.
One product, three names#
You will see three names in these docs. They describe layers of the same system, not separate products you need to buy or configure.
- Floating Keys
- The product you use: the web and desktop interface for projects, threads, runs, approvals, connectors and Keys.
- OpenSaddle Core
- The control plane underneath. Core is the authority for projects, conversations, runs, policy, approvals and receipts. Some technical identifiers still carry the OpenSaddle name for compatibility.
- KRAIL
- Repository-backed project knowledge. Floating Keys can read a project’s KRAIL layout so agents start from reviewed, sourced context instead of guesses.
Surfaces
OpenSaddle Core
Work and knowledge
What is available today#
Floating Keys is early. Anyone can read these docs and join the waitlist. The hosted workspace is an invite-only beta: sign in with Google or an emailed link, and the server separately checks that your account has been invited. Invited accounts can chat with free models and keep private Projects with saved files. The desktop app and Core run locally for one person and have no public download yet. Hosted agents, schedules and Project Keys remain planned. See Getting started for the exact steps.
- Public site and waitlistLive
Docs, sign-in page and an email-confirmed waitlist. Joining does not create an account.
- Account sign-inLive
Google and emailed sign-in links. Signing in does not grant beta access by itself.
- Hosted workspacePartial
Invited accounts only: free-model chat, private Projects and saved Project files.
- Project file searchPartial
Invited accounts: search a Project’s saved text files from its Overview and open the exact matching passage.
- Connect an AI tool (MCP)Partial
Discovery is public. The full account connection has not been verified end to end.
- Desktop app and CoreLocal
Single-user Projects, threads and governed runs on your own Mac. No public download.
- Coding agentsPartial
Codex task execution and result review are verified locally. Other agents are at earlier stages.
- Hosted agents and KeysPlanned
Long-running agents on isolated workers, with per-project, revocable Keys.
Design principles#
- Confirmed state only. The interface shows an effect as done only when the system that owns it has confirmed it. A pending action looks pending.
- Authority is explicit. Agents are their own principals with their own grants. They never silently inherit everything the person who started them can do.
- Evidence over judgment. Agents can report what they did. Decisions that settle something for other people — merging, closing, publishing — stay with a person.
- Finished is not the same as accepted. A run can complete, pass checks and still wait for a human to accept it. Floating Keys keeps those states separate.
- Honest status. Capabilities are labelled as live, local, partial or planned. A catalog entry is not proof that something works.
Where to go next#
- Getting started — the waitlist, sign-in, your first Project and what each step needs.
- Connect an AI tool — let Claude, ChatGPT or Cursor reach your Projects with permissions you choose.
- Projects and threads — how work is organized and who can see it.
- Runs and review — how a request becomes durable, reviewable work.
- Agents, models and environments — what actually does the work, and where.
- Keys and connectors — how outside services will be reached safely.
- Memory and context — KRAIL, imported history and what agents are shown.
- Architecture — the layers, and how web and desktop differ.
Status reflects November 2026. Planned items are design targets, not commitments to a date.