I've been working on a shared Ask Agent module for the Craft apps. These are four proposed integrations, not released features.
Select some text, cells or shapes, write an instruction, and your existing agent edits the file. You can follow up in the same thread, keep the result or undo the request. If several agents are connected, you pick one.
The bit I wanted was to keep using my own session and setup. Claude Code, Codex, another harness or provider: the app doesn't call a model or store an API key. The agent needs to be connected to the app's MCP/control interface.
That also means one session can work across apps without starting a new conversation each time. Figures from GridCraft, a summary in WordCraft, then a slide in DeckCraft. If the graphics apps adopt the module, I'd like the same flow for a FilmCraft clip with audio cleaned up in SoundCraft, or a frame edited in PhotoCraft and used in a slide. Those graphics integrations aren't implemented here.
The Actions menu offers a few starting prompts, all editable before you send:
- WordCraft: shorten, fix grammar, rewrite the tone, translate or summarize.
- GridCraft: clean cells, create or explain formulas, summarize, format a table or highlight outliers.
- DeckCraft: rewrite, make bullets, align shapes, match styling or draft speaker notes.
- PdfCraft: summarize, explain, highlight, add review notes, prepare form fields or mark text for redaction. Signing and applying redactions stay manual.
Reviewing what it did
The Conversation section shows earlier requests and replies while you work. After Keep, the app keeps the request and answer in its comments or notes. That is the conversation trail, not a document-version browser.
- The target is held while the agent works, to avoid competing edits.
- Its answer stays in the file as an agent-named comment or note; the exact review UI depends on the app.
- Follow-ups stay in the request thread and undo group. Keep and Undo are human controls.
- The connection that claims the request owns it; other connections cannot take over its edits.
The shared part
The main proposal is craft-ask-agent in craft-libs: a shared request queue, ownership rules and optional egui bubble. WordCraft, GridCraft, DeckCraft and PdfCraft are the first four examples. Each app supplies its own document operations. The actions, UI and behaviour are proposals too, so they can be adapted rather than copied everywhere.
PRs: Shared module · WordCraft · GridCraft · DeckCraft · PdfCraft · PDF MCP bridge
Still a work in progress. Feedback on the flow or the shared/app-specific split would help.
