Clanker CloudMany useful tasks take more than one sitting. You draft a proposal, wait for a clarification, and return to update the recommendation. Workspace keeps the Project files and saved Sessions available so the second visit can begin with the work already done.
The first step is to identify what changed. A saved conversation provides history; the next request should explain which source is current and what result you want now.
Reopen the conversation or start a focused one
Use Sessions to reopen the conversation behind the deliverable. Pin conversations you return to often. Projects and their groups help you find related work when there are several clients or planning cycles.
On desktop, opening a Session adds it to the chat tab bar. Closing its tab leaves the saved Session and messages in place; you can reopen it from Sessions. Closing a chat tab also does not stop any running work, so use the relevant stop control when that is your intention.
Continue the existing Session when you want to revise its result or use its discussion. Start a fresh Session in the same Project when the next job has a different outcome. For example, a proposal-review conversation and a negotiation-question conversation can share sources while retaining their own progress.
Bring the changed input into view
Suppose a fictional supplier sends a revised proposal after your first comparison. Add the new file to the Project and identify it explicitly. Keep the earlier proposal if it explains the change.
A small source note can make the next request clearer:
| File | Role in this fictional update |
|---|---|
| supplier-proposal-2026-10-06.pdf | Earlier offer used in the first comparison. |
| supplier-proposal-2026-10-13.pdf | Revised offer to evaluate now. |
| supplier-comparison-reviewed.md | Previous reviewed result to update. |
Ask the Agent to list the intended inputs before revising the conclusion. If it names a different proposal, resolve that selection first. A copy saved from Google files needs an explicit refresh when you want newer content; earlier Project copies do not automatically stay synchronized.
Request an update with a clear boundary
Try this handoff:
Use the revised 13 October proposal to update supplier-comparison-reviewed.md. Compare it with the 6 October offer and list the material changes with source locations. Preserve unchanged findings. Keep any unstated cancellation term unresolved. Save a new comparison named supplier-comparison-2026-10-13.md so I can inspect both results.
Open the new file from Project Files or Space. Check the rows that changed and one that should have stayed the same. This makes it easier to see whether the revision followed your requested scope.
If the updated conclusion depends on a new assumption, ask for that assumption to be stated. Keep the handoff record with the output so the next visit begins with an understandable baseline.
Branch when you want to explore another direction
Workspace can branch a conversation from a reply. Branching copies the conversation through that reply without starting a model run. You can then send a request in the branch to explore an alternative while keeping the original discussion available.
For the supplier example, branch from the reviewed comparison to investigate a different evaluation priority. Name the alternative clearly and avoid treating its speculative conclusion as the accepted decision.
A conversation branch does not create an independent copy of every Project file. If you want separate artifacts, request distinct output filenames and verify them before editing shared inputs. Branching helps organize discussion; file choices keep the resulting work distinguishable.
Leave a useful starting point
Finish by opening the reviewed result and recording any questions awaiting evidence. Bookmark a useful explanation or save a sourced finding in Wiki when you expect to reuse it.
Update Project instructions if the source-selection rule changed. Keep temporary requests in the Session. The next visit becomes easier when you can identify the current file, the reason it changed, and the decision still to make.
Sources
Give your assistant one useful job
Make current inputs and reviewed outputs clear before the next Session begins.