If you've been using AI tools for real work over the past two years, you've probably noticed something: AI doesn't remember anything.
Every new conversation starts from scratch. It doesn't remember which angles you ruled out last time, what your readers care about, which phrasing you hate, or what your brand voice sounds like. You're effectively retraining it every single session.
For solo developers and indie hackers, this problem cuts deeper than it does for teams.
When you work alone, there's no buffer
In a company, AI tools are supplements. Team members provide context through documents, Slack history, and established patterns. The team's process compensates for AI's limitations.
As a solo developer, you don't have that buffer. You might be writing code, drafting content, analyzing data, and building strategy — all in one day, all with AI that starts fresh every time. The ceiling of what AI can help you with is determined by how precisely you can describe the context in each conversation.
The irony: sometimes describing the context takes more time than the actual work.
The real friction isn't the lack of tools
The past year gave us no shortage of AI tools. ChatGPT for writing, Copilot for code, various AI platforms for everything else. Individually, they're impressive. But when you're actually working, the friction isn't "no AI tools available" — it's:
- How do these tools connect?
- How does context carry across tools?
- How do workflows accumulate rather than just producing one-off results?
How much time do you spend copying and pasting between tools, re-explaining context, regenerating variations of work you've already done?
What Floatboat is actually building toward
Floatboat's core idea: the AI working environment itself should remember how you work, not just execute your current instruction.
They call it the Tacit Engine. The simple version: AI learns your preferences over time through usage — your writing style, your decision-making priorities, your patterns for certain types of tasks. You shouldn't have to re-explain this every session.
The second layer is Combo Skills — chaining multiple AI operations into reusable workflows. Not "ask one question, get one answer" — but "one trigger fires a sequence of AI operations, with results automatically flowing into the next step". For solo developers running content, documentation, or ongoing product work, this is where real time savings compound.
The third layer is the workspace itself — files, browser, AI panels in one unified view, no window switching. This part is easy to dismiss until you've tried it. The cognitive overhead of context switching between tools is often underestimated. What drains you isn't AI producing content — it's switching contexts to make that happen.
Why this direction matters
If the next phase of AI tooling moves toward "integrated environments designed for individual knowledge workers", Floatboat is solving a real but underappreciated problem. Not reinventing the wheel — integrating the fragmented AI usage that's already happening into a workspace that accumulates rather than just outputs.
The open questions are real: whether the integration is solid enough, whether the learning is actually useful, what migration costs look like. Worth watching before betting on it.
For solo developers already stitching together AI tools into a workflow, this is worth understanding — not because Floatboat is definitely the answer, but because the problem it's trying to solve is definitely real.
Top comments (0)