LapuAi
Desktop-native AI agent for every app, file & browser
Start new thread

LapuAi Office - Desktop connected agent for Excel, Word, PPTX

by•
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.

Add a comment

Replies

Best
Maker
📌
Hey Product Hunt Shipping a focused update: native Excel, Word, and PowerPoint in Lapu on the desktop - not an another Python scripting. What that means in practice: - In chat or an automation task, you describe what to find and read on the machine - Lapu can open real files on your PC, not only a browser tab - Then it creates or edits .xlsx, .docx, or .pptx with that context - You can work on your open files We kept hitting the same pain: the agent could talk about a spreadsheet, but the actual Office file still sat on disk waiting for a human. This closes that loop on macOS and Windows. You still approve risky steps. If you try it, tell us which Office workflow is still awkward - invoices, reports, decks, whatever you actually use.

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?

Maker

 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.

 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?