Platform guides
Cloud guide
Start cloud tasks, move local work, and deliver through PRs.
Cloud runs tasks remotely. Start a task by selecting a repository, or move an existing local task to the cloud, then follow the work from an available client that supports Cloud.
This guide uses the desktop app as the main interface. It also includes CLI commands for moving a local task to Cloud and checking the transfer status.
View flowchart source (Mermaid)
flowchart TD
A["Check account and repository access"] --> B{"Where will you start?"}
B --> C["Select a repository and start a cloud task"]
B --> D["Open an existing local task"]
D --> E["Review conversation and uncommitted changes to transfer"]
C --> F["Cloud prepares and runs the task"]
E --> F
F --> G["Follow progress, add context, and review results"]
G --> H["Refine the work or deliver it through a PR"]
1. Before you start
1.1 Account and clients
| What you need | What to check |
|---|---|
| Remy account | • You are signed in to your Remy account. • The signed-in account and team scope match the task. |
| Desktop app | • Remy is installed and you’re signed in. • Use it to create, view, and continue cloud tasks, and open PRs. |
| CLI (optional) | • Use it to move local conversations to Cloud and check the transfer. • Follow the CLI Guide to install it and sign in separately. |
| Network | • An internet connection is needed to submit tasks, view progress, and respond. |
| GitHub | • Your connection is authorized. • You can access the target repository and have the necessary permissions for pushing changes and working with PRs. |
The examples in this guide use GitHub repositories. For installation and sign-in, see the Desktop Guide.
1.2 Choose how to start
| Your situation | How to proceed |
|---|---|
| You want to work on a repository directly in the cloud | • Select a Cloud repository and branch, then create a task. • You don’t need a local checkout first. |
| You’ve already analyzed or changed code locally and want Cloud to continue | • Open the local chat and use Move to Cloud. • Choose whether to include uncommitted changes. |
| You started the local task in the CLI | • Use remy cloud handoff to start the transfer. • Once it succeeds, follow the task in the desktop app with Cloud support. |
2. Connect your repository and check requirements
2.1 Connect GitHub
- Open the project picker in the desktop app and find Cloud.
- If Cloud is unavailable, click the settings button beside it to open the GitHub connection page.
- Follow the page’s instructions to authorize GitHub.
- Return to the project picker, open Cloud, and check that the target repository is listed.
Use Search repos to find a repository. If it’s missing, check the connected GitHub account and the repositories it is authorized to access.
2.2 Check the repository and branch
When you select a repository, Remy starts with its default branch. To use a different one, open the branch picker and choose the branch the task should start from.
| Item | What to check |
|---|---|
| Repository | • The repository is the one this task should work on. |
| Branch | • It contains the code you want to work on. • For a local transfer, also check the commit and branch shown during the transfer checks. |
| Project instructions | • The documentation explains dependencies and how to run the project and its tests. |
| Permissions | • The repository is accessible. • You have the permissions needed to push changes and work with PRs. |
2.3 How Cloud prepares the environment
After you submit a task, Cloud prepares the workspace, fetches the repository code, and starts execution as needed. This workflow does not require you to create a separately named cloud environment.
Dependencies installed on your computer, local development servers, and local credentials should not be assumed to exist in Cloud. If the task needs special dependencies, explain how to prepare and check them in the project documentation or task description.
Read the repository’s README and project instructions first.
Confirm how to install dependencies, run the project, and run its tests.
If the environment is missing something required, identify what is missing and include the relevant error.
Run the checks you can, and list any checks you cannot run separately.
3. Start a task directly in Cloud
3.1 Select a repository and send the task
- Start a new chat and open Cloud in the project picker.
- Find and select the target repository, then check the branch.
- Confirm that the execution setting shows Send to cloud.
- Choose an available model, describe the task, and send it.
- Wait for initialization and execution, then review the progress and results.
To review a plan first, enable Plan before editing in the execution menu before submitting the task. Read the plan, then confirm it or explain the changes you want in the chat.
3.2 Make the requirements clear
Adapt this example to your project:
Find and fix the pagination issue that occurs when filters change in the order list.
Requirements:
1. Read the repository documentation and relevant instructions first.
2. Change only filtering, pagination, and directly related logic.
3. Follow the project’s existing styles and test conventions.
4. Add and run relevant tests.
5. Summarize the files changed, check results, and any remaining work.
Do not merge the PR.
3.3 Text messages and local attachments
Task messages sent directly to Cloud currently accept text only. Local attachments, folder references, and local code references cannot be sent with these messages.
| What you need to provide | Suggested approach |
|---|---|
| Code or documents already in the repository | • Include the repository path and explain what to focus on in your message. |
| Short requirements or reproduction steps | • Write them directly in the task message. |
| An existing local conversation and uncommitted changes | • Use the local-to-cloud transfer workflow in section 4. |
| A draft already contains local files or references | • Remove the attachments or references before sending a text task. • Or return to local execution and use the appropriate local workflow. |
4. Move a local task to Cloud
4.1 Start the transfer in the desktop app
- Open the local chat you want to continue and check the current project and task.
- Wait for the current local execution to finish.
- Open the chat tab’s menu and choose Move to Cloud.
- If there are uncommitted files, review the file count, list, and estimated transfer size, then choose whether to include them.
- Check any repository, commit, and other confirmation details shown, and follow the prompts.
- Wait for the transfer to succeed, then follow cloud execution in the original task.
If GitHub is not authorized, complete authorization from the settings entry before trying again.
4.2 Choose whether to include uncommitted changes
When Include uncommitted changes? appears:
| Option | What it does |
|---|---|
| Include Changes | • Transfers the eligible uncommitted file changes listed in the preview. |
| Exclude Changes | • Keeps uncommitted files on your computer. • Cloud continues from the committed code confirmed by the checks. |
| Cancel | • Cancels this transfer. |
This choice determines whether uncommitted changes are included. Review the file scope shown before proceeding; do not assume that the entire local folder will be uploaded.
4.3 What changes after the transfer
| Item | How it is handled |
|---|---|
| Conversation content | • Supported conversation content is transferred so Cloud can continue the task. |
| Committed code | • Cloud prepares a checkout from the confirmed repository and commit. |
| Uncommitted files | • Included or excluded according to your choice. • Subject to path, size, file count, and content checks. |
| Ignored files, credentials, and sign-in state | • Not included in the transfer by default. |
| Working branch | • A new branch is created in the cloud for the work. |
| Local files | • Cloud results are not automatically written back to your local working directory. |
| Delivery | • Review the results and use a PR when needed. |
A successful transfer does not mean the task is complete. Once it moves to Cloud, wait for execution, review the results, and address any follow-up work.
4.4 Start a transfer from the CLI
In a terminal where you’ve signed in to the CLI, list the target project’s chats:
remy --workspace "/path/to/project" history list
Replace /path/to/project with the actual project path and CHAT_ID below with the relevant conversation ID.
Include uncommitted changes:
remy --workspace "/path/to/project" cloud handoff --chat-id "CHAT_ID" --include-workspace --message "Continue the remaining checks in the cloud and report the results."
Keep uncommitted changes local:
remy --workspace "/path/to/project" cloud handoff --chat-id "CHAT_ID" --exclude-workspace --message "Continue the task in the cloud using the committed code."
Choose the command that fits the task. If the working directory has no uncommitted changes, you can omit both --include-workspace and --exclude-workspace.
The CLI shows a transfer preview. Check the account scope, repository, branch, commit, and file scope, then type yes to confirm.
4.5 Check or cancel a transfer
If a transfer is still in progress, check its status:
remy --workspace "/path/to/project" cloud status --chat-id "CHAT_ID"
If you already have the handoff ID, you can specify it explicitly:
remy --workspace "/path/to/project" cloud status --chat-id "CHAT_ID" --handoff-id "HANDOFF_ID"
Replace HANDOFF_ID with the ID returned for that operation. If the connection drops after upload or the outcome is unknown, check that same transfer first instead of starting a new one.
To cancel a transfer before the cloud task has been activated:
remy --workspace "/path/to/project" cloud cancel --chat-id "CHAT_ID" --handoff-id "HANDOFF_ID"
This command only cancels a transfer that has not activated a cloud task. It cannot cancel a task that has already been activated. For a task already executing in Cloud, open it in the desktop app and use the task’s stop control.
The CLI’s cloud status command checks the transfer. Use the desktop task interface for full task progress, continued conversation, and PR actions.
5. Follow tasks and work across devices
5.1 Understand the current stage
| Stage | What to do |
|---|---|
| Preparing or transferring | • Wait for the workspace and task to be ready. • Read any errors and avoid duplicate submissions. |
| Running | • Follow the output and progress. • Add context or requirements as needed. |
| Waiting for input or confirmation | • Open the original task and read the question or plan. • Provide information, confirm requirements, or explain what should change. |
| Results available | • Review the changes and check results. • Decide whether to refine the work or deliver it. |
| Failed or cancelled | • Check the final status and error details first. • Address the cause before deciding whether to continue or start again. |
After requesting a stop, wait for the task status to update and confirm that cloud execution has ended.
5.2 Continue in the original task
To refine a result, open the same cloud task and explain what needs to change:
Changing the filters now returns the list to page 1, but the list does not refresh.
Fix only the refresh logic and preserve the changes already completed.
Add and run relevant tests, then summarize the results.
Do not merge the PR.
After a network interruption, reopen the original task and check its current status and latest reply before deciding whether to resend a message. If the task list fails to refresh, it may still show the last records it retrieved.
5.3 Continue from another device
- Sign in to Remy Desktop on another device with the same account and confirm the same team scope.
- Find the cloud task in the sidebar.
- Open it and wait for the latest messages and status to load.
- Review the results or add requirements in the same task.
The computer that started the task does not need to stay online. Cloud tasks can continue after you close the desktop app, go offline, or shut down your computer. Questions that need your reply will wait for your response.
Work across devices using any client that supports Cloud.
6. Review and deliver results
6.1 Check the task results
| Check | Where to look and what to verify |
|---|---|
| Task outcome | • Read the result in the conversation and check whether the original requirements were met. |
| Code changes | • Review the files and changes described by the task. • If a PR was created, inspect the actual diff on its page. |
| Tests and verification | • Confirm which checks actually ran and whether they passed. • Checks that failed or did not run should have an explanation. |
| Remaining work | • Note anything that needs more changes, environment setup, or human input. |
A task result or a generated PR does not replace checking the tests and actual behavior.
6.2 Deliver the work through a PR
If you need a PR, say so in the task. For example:
Prepare a PR for the completed changes.
Describe the problem solved, the main changes, the checks that ran, and any remaining work.
If this task already has a PR, update that PR.
Do not merge it.
When the task creates a PR, a Draft PR or PR card appears. Click its link to open the PR in your browser and review the working branch, target branch, and actual diff.
To merge from Remy, review the PR first, then choose Merge PR on the card. Check the source and target branches in the confirmation dialog before proceeding. Merging changes the remote repository; use the returned status to confirm the outcome.
6.3 Your local folder does not update automatically
Cloud results are not automatically synced back to your local working directory. After merging a PR, or when you want to resume local work, fetch and inspect the code using your project’s usual Git workflow.
The local Changes panel does not necessarily show the latest changes from the cloud task.
7. Troubleshooting and known limitations
7.1 Access, execution, and results
| Issue | What to check first |
|---|---|
| Cloud or Send to cloud is unavailable | • Check that GitHub is connected. • Complete authorization using the prompt beside the entry. |
| The target repository is missing | • Check the GitHub account. • Check that the repository is included in the authorized scope. • Search again by repository name. |
| Cloud initialization fails | • Check access to the repository and branch. • Read the failed stage and specific error. • Check the project’s run instructions and contact support if needed. |
| A local task cannot move to Cloud | • Check that local execution has finished. • Check the project, repository, and commit information. • Check the uncommitted-file choice and content checks. |
| The connection drops after transfer or the outcome is unknown | • Reopen the original task or check the same transfer record first. • Avoid creating a duplicate cloud task. |
| A Cloud message with attachments won’t send | • Direct Cloud messages accept text only. • Remove local attachments, folder references, and code references, or use the appropriate local workflow. |
| The task is missing on another device | • Check that the account and team scope match. • Check whether the task list refreshed successfully. |
| You do not have permission to access the task | • Check the account, team scope, and task owner. • Follow the prompt to sign in again or contact support. |
| A PR cannot be merged | • Check the returned details about the target branch, permissions, and conflicts. • Open the PR page to see what needs attention. |
| Cloud changes are missing from local files | • Cloud results are not written back locally. • Use the PR or your project’s usual Git workflow. |
7.2 Current boundaries
- A local-to-cloud transfer follows the preview and your selected scope. It does not copy your entire computer or local runtime environment.
- Messages that start or continue Cloud tasks currently accept text only.
- Your transfer choice determines whether local uncommitted files are included.
- Checking a transfer in the CLI is different from following the cloud task’s execution.
- Cloud results do not automatically sync back locally. Confirm delivery by checking the actual code, check results, and PR status.
8. Get help and keep exploring
8.1 Report an issue
Use Send feedback for the relevant task. For CLI feedback commands, see the CLI Guide.
Specify whether the issue occurred while starting a task, moving local work to Cloud, following a task, or delivering a PR. Include the repository and branch, any task or handoff ID, and the error message.
If you can’t open the task or use the feedback entry, contact support at support@corepass.com.
8.2 Keep exploring
| What you want to do | Where to look |
|---|---|
| Complete your first coding task | • Quick Start |
| Install and use the desktop app | • Desktop Guide |
| Use the CLI or send CLI feedback | • CLI Guide |
| Find more instructions and answers to common questions | • Docs on the Remy website |