A release should leave evidence, not just an answer
AI can move quickly through a repository. The useful version of that speed is work a team can still inspect: which project and branch were in scope, which files changed, what the run reported, and where a person must decide what happens next. Grain 1.1.85 tightens that path while making the documents around the work much more capable.
The result is a clearer contract for both code and knowledge work. A Mission can keep its conversation, return reviewable changes, stop at an approval boundary, and leave behind an editable document or presentation instead of a flattened response.
Code work stays reviewable
Grain keeps the execution scope and resulting changes attached to the Mission. Local work runs in an isolated task workspace; cloud work returns a diff when policy or credentials do not permit a push. Changed files, additions, deletions, status, and review comments stay visible so a reviewer can understand the result before it moves forward.
Approval policy remains the boundary for consequential actions. An organization can require approval before a Git push, and an unknown policy fails closed to a reviewable diff. Grain does not turn every run into a certified security audit. It makes every code result inspectable and offers a dedicated security review when the work needs an additional security-focused pass.
- Keep repository, branch, machine, model, and tool scope visible on the Mission.
- Return code changes as reviewable diffs when Grain is not allowed to push.
- Carry line-level review comments into the next run instead of separating feedback from execution.
- Require a human decision before push, publish, deploy, or another sensitive action when policy calls for it.
A requested security review now runs exactly once
The dedicated security-review offer has been hardened from purchase through dispatch. Grain checks for an existing non-terminal review before charging, refuses the offer when no compatible AI teammate can run it, and sends an accepted review through the same guarded dispatch path as other tasks.
The price is shown as $15 (1,500 Grain Models credits), computed by the server so the interface is not inventing money math. If the review run fails, the refund path remains part of the workflow. This is an on-demand review with a visible task and outcome—not a claim that every line of code has received an independent audit.
Project conversations remember—with consent
Project conversations now persist, can continue from saved code, and can show stored image results inline. Before recent project messages or selected saved code are sent to DeepInfra, Grain names the destination and asks for approval. If the context changes, the review appears again, and provider failover cannot silently change the approved destination.
Images have their own consent boundary. Approving general project or file context does not automatically approve sending a picture. This keeps a useful conversation durable without turning convenience into an invisible expansion of scope.
Documents keep their structure through export
Grain Docs now has a real editing ribbon for paragraph styles, fonts, emphasis, color, lists, quotes, alignment, spacing, tables, links, images, code, undo, redo, and zoom. The read view uses the same sanitized formatting model as the editor, while Slides adds font controls, fills, layouts, and better PowerPoint round-tripping.
Images now survive the full path into Word and PDF as pictures. Grain reads common image formats, preserves useful dimensions, fits them to the page, and carries image relationships safely into an existing Word package. If an image cannot be reached, the export still succeeds and identifies it with its alt text instead of failing without explanation.
- Styled documents remain editable and export to Word with real tables and formatted text.
- Pasted screenshots and HTTPS images can travel into Word and PDF.
- Unsafe style values and image sources are dropped by a closed formatting allowlist.
- Docs, Sheets, Slides, and Tables opened from Documents use the same real editors as task outputs.
Review, continue, export
This release brings the operating loop closer together. Context can persist without bypassing consent. Code can move quickly without hiding the diff or the decision to ship. A security-focused pass can be requested as a real task with clear pricing and failure handling. The artifact that follows can still be edited and exported in the format the team uses.
Update Grain Desktop to 1.1.85, open an existing project conversation, or start a Mission with the repository and approval policy you want Grain to use.
