> ## Documentation Index > Fetch the complete documentation index at: https://cogno.studio/docs/llms.txt > Use this file to discover all available pages before exploring further. # Continue your Task on your machine > Bring the run of your Task from a teammate's machine to your own, to work on it yourself. Your Tasks may run on any free machine in the Workspace, including a teammate's. They stay your Tasks wherever they run. When you want to work on one yourself, or the work needs something only your machine has, continue it on your machine. Only the Task's assignee can do this, and the run only ever moves to the assignee's machine. ## Prerequisites * You are the Task's assignee. * The Task runs on a teammate's machine, or, for a Cloud Project, in the Cloud environment. * Your machine has a ready folder for the Task's Project. See [Machines](/docs/machines.md). * The Task is not **Done**, **Archived**, or **Rejected**. ## Continue a Task on your machine When your Task runs on a teammate's machine or in the Cloud environment, the line above the message box says **Sending moves this run to your machine and stops it on {teammate}'s {machine}** (or **…stops it in the Cloud environment**). If you can't take the run over yet, that line says why instead, for example when your machine has no folder for the Project. When a question addressed to you is open, the message box sends your answer to that question and keeps the run on its current machine. Choosing an option or the question's × button also keeps the run there. See [Answer a question in the conversation](/docs/task-sessions.md#answer-a-question-in-the-conversation). ![Line above the message box saying that sending moves the run to your machine and stops it on the teammate's machine](https://mintcdn.com/genaxis/gC4sypYtPv6IjbOd/images/task-handoff-notice.png?fit=max\&auto=format\&n=gC4sypYtPv6IjbOd\&q=85\&s=7f8de5a57330ace8040a7d4a446aad42) Your Task running on a teammate's machine **1. Open the Task** Open the Task in the desktop app or on the web. **2. Send a message** Type what to do next and send it. Cogno moves the run to your folder for the Project and starts a new run on your machine from the description and your message. The run on the previous machine stops. In the desktop app, the Task description transitions into the workspace as soon as you send, with your message shown while the run moves to your machine. If the move is refused, you return to the description with your message back in the box and the reason above it. The transition respects your system's reduced-motion preference; it does not change when the run starts. ## What moves with the run | Moves | Stays on the previous machine | | - | - | | The Task description | The conversation of the previous run | | Messages sent to the Task that the previous run had not received yet | Changes from a turn that never finished, when the previous machine stopped mid-turn | | The branch the previous run worked on, and its commits, pushed or not | Files the checkpoint leaves out (see below) | | Changes and new files that were not committed, as of the end of the previous run's last turn | Everything in a folder set to **Run directly** | The new run starts on the same branch, with the uncommitted changes still uncommitted. The run on the previous machine stops within about a minute. The new run starts from the description. ## When the machine running your Task stops responding When the machine running a Task Cogno is working on stops responding for 10 minutes while the Task has work waiting, Cogno moves the run to another machine so the Task does not stall: * Your machine comes first, when it is online and has a ready folder for the Project. * Otherwise, the run moves to a teammate's machine that is online and has a ready folder for the Project. * When no such machine is online, the Task waits where it is. The new run is told that the previous machine stopped responding, that the previous run may have stopped partway through a turn, and to check whether it already sent a message or comment before sending it again. Cogno moves a Task this way at most 3 times a day. You receive the **moved this task's run to your machine** notification only when the run lands on your machine. ## What Cogno keeps on your repository's remote To carry work that was not pushed, Cogno saves a checkpoint of the Task's work at the end of every turn and pushes it to your repository's remote as `refs/cogno/checkpoints/task-`. Only folders that **Run in a Worktree** are checkpointed; a folder set to **Run directly** is never touched. | Topic | What happens | | - | - | | What it holds | The branch, its commits, and changed or new files in the Task's worktree | | What it leaves out | Files your `.gitignore` ignores; `.env`, `.env.*`, `*.pem`, `*.key`, `*.p12`, `*.pfx`, `id_rsa*`, `id_ecdsa*`, `id_ed25519*`, and `.netrc` files anywhere in the folder; and changed files over 5 MB | | Who can read it | Anyone who can read the repository, like any pushed branch. It is not a branch, so it does not appear in the branch list or in pull requests. | | How long it stays | Until the Task is **Done**, **Archived**, **Rejected**, or deleted; the machine holding the Task's folder then deletes it. A reopened Task saves a new checkpoint on its next turn. | | Whose credentials push it | The Git credentials on the machine running the Task | > [!WARNING] > > A checkpoint can contain files you have not committed. Keep credentials and > other files that must not leave your machine in `.gitignore`. ## When Cogno moves the run to you A run may need something that exists only on your machine, such as local files, credentials, or a signed-in tool. Cogno then writes what it found into the description, pushes the work worth keeping, and moves the run to your machine. The new run starts there right away, and you receive a **moved this task's run to your machine** notification in the [Inbox](/docs/inbox.md). ## Troubleshooting | Symptom | Fix | | - | - | | **Continue on my machine** does not appear | Check that you are the Task's assignee and that your machine has a folder for the Task's Project. | | **Could not move this task to your machine** | The Task closed, moved, or your folder is not ready. Reopen the Task and check its folder in **Settings → Machines**. | | The new run starts without the previous run's changes | The previous machine stopped in the middle of a turn, the change is a file the checkpoint leaves out, or the folder is set to **Run directly**. Ask the previous machine's owner to push the changes, then send the branch name to the Task. | ## Related docs * [Take over a Task in your terminal](/docs/task-sessions.md) * [Machines](/docs/machines.md) * [Inbox](/docs/inbox.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.