Tool steps appear above edits waiting for your review
Tools
How edits are placed
Text-only suggestions target paragraphs or bullets by the IDs returned by the read tool. Resume fields, entries and sections use their own visible targets. A set involving structural changes is reviewed and accepted together as one step you can undo; text-only edits can be accepted individually. See Using the assistant. Hidden summary, sections and entries are excluded from the assistant’s document view and cannot be targeted by its proposals. Full application snapshots stay in your owned document/conversation storage for review, stale checks and Undo; they are not sent to your AI provider. The model receives the visible read view and a preparation/status acknowledgement. Earlier user/assistant text and facts you already shared remain conversation context. Create or open a cover letter through Documents, then use its letter assistant. A cover letter is a separate document; the resume assistant cannot create it as a resume section. If you or another change edits a passage after the assistant read it, the edit can no longer be placed. The card then says, for example, “1 change couldn’t be prepared. Save your latest changes and ask again, or open Write to edit it directly.” Accepted edits stay Applied when you refine their wording. Out of date: the text has changed since. applies to a proposal whose original passage can no longer be placed. The assistant is instructed to rewrite only what your document already says: it doesn’t add employers, titles, dates, numbers, skills or achievements that aren’t in the document or the conversation. When a job posting asks for something your document doesn’t mention, it usesask_user_question first, and only drafts it from your answer.
What the assistant also sees
Besides what the tools return, each message can include:- The job posting: the role, the company, the job description (or its requirements list) and your notes from the linked application. A resume uses the application it was made for, or else the most recently updated application it’s linked to. A letter uses only the application it was made for. Removing the posting chip leaves it out.
- Attachments: images, PDFs and MP3 or WAV audio are passed to the model directly, when the provider supports them. Other types are only listed by name.
- The conversation so far: earlier messages, tool results and your answers.
Web search support
Search throughsearch_web comes from the server’s SearXNG when the operator set one up, otherwise from a selected Web access connection, regardless of which AI provider you use. Only one search mechanism is offered per reply. Reading a supplied link uses read_page; built-in reading needs no commercial web account.
After explicit sharing approval, search_web can retry an authentication or quota failure through the selected direct OpenAI, Anthropic or Google Gemini connection’s native search. The same approved query and country are used, with no additional document or Knowledge context. Only retrieved URL sources become results; generated prose links do not. Models can refuse native search, and custom endpoints or compatible gateways are excluded. AI fallback requests are included in AI usage. Other failures and cancellation do not trigger it.
Without a web connection, the assistant can choose read_page to fetch a supplied public URL with the built-in reader. If the page cannot be read, paste the relevant text. The AI model does not fetch page content from a URL alone.
The source list combines successful search/read results, deduplicates links, and survives reopening the conversation. Links invented in the reply text are not added as retrieved sources. Failed or interrupted web tools show that outcome; they do not show a successful search. Existing conversations retain source evidence from historical native searches.
Limits
Stopping a reply cancels outstanding search and reading as well as the model request.