my personal 🛟 in the overwhelming crowd of AI tools that all want my data and want to lock me in
See the code
A local-first AI assistant that floats on top of your desktop.
Floaty lives in your tray / menubar and as a draggable swimming-ring overlay that stays on top of your other windows. Through the ring you can capture what's on your screen - a screenshot plus the actual text content read via accessibility APIs - and everything you capture is embedded into a local memory that the assistant can search when you chat with it.
Everything stays on your machine: memory, conversations, skills, settings, and speech-to-text all live in ~/.floaty. The only thing that leaves your computer is what you send to the LLM provider you configure - and with on-device embeddings plus a local model in Ollama, nothing has to.
~/.floaty/sounds.search_captures tool so the assistant can recall what you've seen.~/.floaty/floaty.md.~/.floaty/skills (also picks up ~/.claude/skills and ~/.agents/skills) and invoke them with /name in chat./server slash command.Grab the latest Windows installer from the Releases page. The app checks for updates itself after that.
On first run, open Settings > Model Provider and add a provider. OpenAI, Anthropic, Google Gemini, Azure OpenAI, OpenRouter, Groq, Mistral, DeepSeek and xAI have one-click presets; Ollama, LM Studio, llama.cpp's server or any other OpenAI-compatible endpoint work through the Ollama and Custom entries.
Platform support: Windows is the primary platform with the full feature set. A Mac Catalyst target exists with the overlay working and other native features (screen capture, screen history, voice input, autostart) stubbed out for now.
Everything Floaty knows lives under ~/.floaty:
| Path | Purpose |
|---|---|
config.json | Settings and preferences |
floaty.md | User-editable system prompt for the assistant |
floaty.db | Local memory - capture embeddings + vector search (SQLite) |
captures/ | Screen history: one markdown file per day plus per-capture blocks (and screenshots, in screenshot mode). An AGENTS.md in there explains the format |
conversations/ | Saved chat threads, one JSON file each |
generated/ | Images made by the chat's image tools |
skills/ | Agent skills, each a folder with a SKILL.md |
models/ | Downloaded speech-to-text models (models/embed/ for on-device embedding models) |
native/ | Downloaded native runtimes (transcribe.cpp) |
ring/ | Custom ring images for the overlay |
sounds/ | Custom sound effects for capture / reply-finished |
Prerequisites:
app/global.json pins 10.0.301, rolling forward on feature bands)No workloads to install.
cd app
dotnet build
dotnet run
Floaty currently builds for Windows only. macOS support is planned but not wired up: see the "macOS" note in AGENTS.md for what it needs.
The solution file is app/Floaty.slnx if you prefer Visual Studio.
app/ Avalonia application (Floaty.slnx, Floaty.csproj)
website/ Landing page deployed to GitHub Pages
.github/ CI: Windows release packaging + Pages deployment
See AGENTS.md for a deeper architectural guide (aimed at coding agents, useful for humans too).
my personal 🛟 in the overwhelming crowd of AI tools that all want my data and want to lock me in
See the code
A local-first AI assistant that floats on top of your desktop.
Floaty lives in your tray / menubar and as a draggable swimming-ring overlay that stays on top of your other windows. Through the ring you can capture what's on your screen - a screenshot plus the actual text content read via accessibility APIs - and everything you capture is embedded into a local memory that the assistant can search when you chat with it.
Everything stays on your machine: memory, conversations, skills, settings, and speech-to-text all live in ~/.floaty. The only thing that leaves your computer is what you send to the LLM provider you configure - and with on-device embeddings plus a local model in Ollama, nothing has to.
~/.floaty/sounds.search_captures tool so the assistant can recall what you've seen.~/.floaty/floaty.md.~/.floaty/skills (also picks up ~/.claude/skills and ~/.agents/skills) and invoke them with /name in chat./server slash command.Grab the latest Windows installer from the Releases page. The app checks for updates itself after that.
On first run, open Settings > Model Provider and add a provider. OpenAI, Anthropic, Google Gemini, Azure OpenAI, OpenRouter, Groq, Mistral, DeepSeek and xAI have one-click presets; Ollama, LM Studio, llama.cpp's server or any other OpenAI-compatible endpoint work through the Ollama and Custom entries.
Platform support: Windows is the primary platform with the full feature set. A Mac Catalyst target exists with the overlay working and other native features (screen capture, screen history, voice input, autostart) stubbed out for now.
Everything Floaty knows lives under ~/.floaty:
| Path | Purpose |
|---|---|
config.json | Settings and preferences |
floaty.md | User-editable system prompt for the assistant |
floaty.db | Local memory - capture embeddings + vector search (SQLite) |
captures/ | Screen history: one markdown file per day plus per-capture blocks (and screenshots, in screenshot mode). An AGENTS.md in there explains the format |
conversations/ | Saved chat threads, one JSON file each |
generated/ | Images made by the chat's image tools |
skills/ | Agent skills, each a folder with a SKILL.md |
models/ | Downloaded speech-to-text models (models/embed/ for on-device embedding models) |
native/ | Downloaded native runtimes (transcribe.cpp) |
ring/ | Custom ring images for the overlay |
sounds/ | Custom sound effects for capture / reply-finished |
Prerequisites:
app/global.json pins 10.0.301, rolling forward on feature bands)No workloads to install.
cd app
dotnet build
dotnet run
Floaty currently builds for Windows only. macOS support is planned but not wired up: see the "macOS" note in AGENTS.md for what it needs.
The solution file is app/Floaty.slnx if you prefer Visual Studio.
app/ Avalonia application (Floaty.slnx, Floaty.csproj)
website/ Landing page deployed to GitHub Pages
.github/ CI: Windows release packaging + Pages deployment
See AGENTS.md for a deeper architectural guide (aimed at coding agents, useful for humans too).