LapuAi
Desktop-native AI agent for every app, file & browser
35 followers
Desktop-native AI agent for every app, file & browser
35 followers
Most AI lives in a browser tab and just chats — you still do the work. Lapu AI is desktop-native: an agent that runs on your machine with direct access to every app, file, terminal & browser you already use. It plans and executes multi-step tasks across them — no plugins, no API keys, no integrations to wire up. Stop chatting, start working. You approve every risky step. Windows & macOS. Free to start.
This is the 3rd launch from LapuAi. View more
LapuAi Office
Launching today
New integration with Office! Now you can work with your files open LIVE.
We offer AI agent for data processing and files automation: extract PDF invoices into Excel -> no upload, permission-gated, with an audit trail.
Lapu can now support you with your office work for cents.
Free Options
Launch Team
LapuAi
The live-file part is the interesting bit. If I have the spreadsheet open and I'm actively editing a cell while Lapu is also writing to that file, what actually happens, does it wait for me to close it, does Excel's own file lock block the write, or can the two of us end up fighting over the same save?
LapuAi
@raffay_sajjad good question - this is exactly the live Excel path, not "two apps racing on the same .xlsx on disk".
With our Excel CLI integration we talk to Excel itself (automation), not a second process that tries to exclusive-open the file while you already have it open.
two cases:
1) you already have the workbook open in Excel
We attach to that live workbook instead of fighting Excel's file lock with another exclusive open. Lapu reads/writes through the same Excel session. we only save when the task explicitly asks (and risky writes still go through approval). on detach we leave your Excel window alone - we don't force-close it.
2) Lapu opens / creates the file itself
That's an owned session - Lapu is driving that Excel instance for the job.
so you and Lapu aren't usually "two writers on disk". Excel holds the live workbook; both of you go through that. if you and Lapu edit the same cell around the same time, it's last change in Excel that wins for that cell - same class of conflict as two humans in one sheet, not a classic OS share-violation fight.
if an exclusive open is attempted while Excel already locked the file the normal way, that open fails cleanly rather than half-writing a corrupt file - then we attach to the open workbook (or ask you to save first if it's unsaved / not listable).
happy to go deeper on attach vs owned if useful.
@xgrejid The attach-vs-owned distinction answers the exclusive-lock question well. The edge case I'd still worry about: if I'm mid-edit on a cell, typed something but haven't pressed Enter yet, and Lapu writes to that same cell in the meantime, does Excel warn either of us that something changed, or does my keystroke just land on top of whatever Lapu wrote without either side noticing?