
Desktop agent workstation from AOE Tech...
Instead of uploading the same files into a chat box, the agent works inside the folders already on the computer. The file manager can search globally, preview in a split view, and take a dragged file into chat to produce a new file. Its own browser researches without taking over the window you are using, can carry Chrome sign-in, and saves the result locally. One task can be handed across models or sites, with the artifact returned to your folder. A workspace remembers files, browser, chat, and layout when you leave and come back. After a calendar sync, an event can prepare work ahead of time and drop a bundle of files. It fits individuals and one-person teams running long tasks across local files and the web.
Floatboat is a desktop agent workstation from AOE Tech Labs for Mac and Windows. It keeps models, files, a browser, tools, and memory in one workspace: you state a goal, and it can find, edit, and save files on your computer. The built-in file manager offers global search, split view, and multi-format preview. Its own browser can research on the web without taking over yours, and it can inherit Chrome sign-in, bookmarks, and history. Different models can hand a task along, and each workspace remembers files, chat, and layout. Web apps and calendar events can also become repeating workflows.
Difficulty: Intermediate
Work on local files
Search, split, and preview in the file manager, drag a file into chat, and keep the new file on the machine.
A separate research browser
The built-in browser can run web tasks on its own and inherit Chrome sign-in, bookmarks, and history.
Hand off across models
One task can move across models and sites, with the result saved locally. The page cites Claude, GPT, Gemini, and DeepSeek examples.
Workspaces that keep state
Each workspace remembers its files, browser, chat, and layout, so leaving and returning continues the same state.
Calendar-driven repeats
After a calendar sync, events can prepare work and produce files, and a chat or calendar item can become a repeating flow.
Drafts from local files
A person searches their own folders and has the workstation read files and write a new document without uploading first.
Research while signed in
For pages that require sign-in, the built-in browser inherits Chrome state, then saves the findings as a local file.
Recurring briefings
Put a daily check on the calendar so materials are prepared on time and saved into a chosen folder.
The page stresses that files do not have to be uploaded over and over. The file manager searches, splits, and previews, and the agent reads local files and saves new ones back. Its browser can go online on its own and carry Chrome sign-in. Models can change while files, pages, and the workspace stay put.
Yes. The page says you can switch models per task, with Claude, GPT, Gemini, and DeepSeek examples, while files, pages, chat history, and the current workspace stay where they are. Switching models changes the worker, not the account that holds the files. The live client list is the source for which models you can pick.
Yes. After a calendar sync, an event can prepare work ahead of time and produce a file bundle in a folder you choose, rather than only reminding you. A chat line or a calendar item can also become a repeating scheduled flow, such as a daily review list. This runs in the desktop app; the page does not say a closed computer continues the job in the cloud.
Real reviews and feedback from users