# Grain 1.1.122: from conversation to verified delivery

> Start work from Slack, keep images and repositories attached, choose where the task runs, and bring progress, files, and Git proof back to the conversation.

- Canonical page: [/blog/grain-1-1-122-connected-task-delivery](https://grain.sh/blog/grain-1-1-122-connected-task-delivery)
- Agent-readable page: [/agents/blog--grain-1-1-122-connected-task-delivery.md](https://grain.sh/agents/blog--grain-1-1-122-connected-task-delivery.md)
- Section: Blog
- Category: Product
- Published: September 16, 2026
- Reading time: 5 min read

## The conversation is now a real place to start work

A request in Slack can now become a Grain task without losing the surrounding thread. Images are copied into the task, shown inline in Grain, and kept with the request so the person reviewing the work can verify exactly what the agent received.

Before the task starts, the requester can choose up to three repositories and select the primary one. Teams can also choose Grain Models for hosted work or Grain Executor for work that needs a connected computer, repository, or local tool.

- Slack connections can be pinned to a specific computer by a workspace admin or owner.
- WhatsApp and Telegram accept the same hosted-versus-local execution choice through simple commands.
- Offline computer choices stay visible instead of silently routing work somewhere else.

## Progress and results return to the same thread

Starting a task now reports what Grain actually knows: queued, picked up, waiting for approval, running, or complete. When a connected computer accepts the task, the thread can show which computer is running it and continue with useful progress updates.

When the work finishes, Grain sends the result back to the source thread. Documents, files, and images can return with the completion message, so a teammate does not have to open a second product just to see whether the requested deliverable exists.

## Git delivery is visible, not implied

Repository tasks now keep GitHub or Bitbucket links close to the work. The selected repository, branch, commit, pull request, and verified push receipt can appear with the task, making it easier to move from a completed run to review.

Grain only presents delivery states it can verify. A saved file is not described as pushed, and a queued task is not described as running. That distinction is especially important when work crosses Slack, a browser, and a connected computer.

## Approvals and answers stay attached to the right run

Slack approval actions now acknowledge quickly and resist duplicate clicks. Approving a completed task is treated as review feedback instead of starting the task again.

Answers to agent questions are bound to the exact task and question that asked for them. Grain blocks stale answers when the model, repository, computer, access, or question has changed, helping teams avoid applying an old decision to a new run.

## Available now

Grain 1.1.122 is available now for Mac, Windows, and Linux. The matching web, backend, and cloud Executor services are live. Existing iOS users receive the shared service improvements without a separate native iOS build in this release.

Download the latest desktop app, connect the channels and computers your team is allowed to use, and start the next task from the conversation where the work already lives.

## About Grain

Grain is a multi-agent work platform. A person describes an outcome as a Mission, Grain coordinates the models, tools, files, repositories, and connected computers needed to do the work, and the result returns for review.

Start with [the complete agent-readable index](https://grain.sh/agents/index.md) or read [the full site corpus](https://grain.sh/llms-full.txt).