Desktop installation and usage

Learn how to install Remy, sign in, set up a project, run tasks, review results, and keep the app up to date. For a complete walkthrough of your first coding task, see Quick Start.

flowchart LR
    A["Download and install"] --> B["Sign in"]
    B --> C["Add a project"]
    C --> D["Start a task"]
    D --> E["Review results"]
    E --> F["Refine or deliver"]

1. Before you start

1.1 Choose the right installer

On a Mac, open Apple menu → About This Mac to check your chip or processor. On Windows, go to Settings → System → About → System type to check your architecture.

1.2 Prepare your account and project

Your project has its own runtime requirements. The desktop app includes the runtime Remy needs, so you don’t need to install Python or Node.js to use Remy. If your project requires those tools, set them up according to its documentation.

2. Download and install

Get the installer from the Remy download page. Choose the version for your operating system and chip, as listed above.

2.1 macOS

1. Download the DMG for your Mac’s chip.
2. Double-click the DMG and follow the installation window’s instructions to move Remy into Applications.
3. Open Remy from your Applications folder.

Check the installation: Remy opens to the sign-in screen, or to your workspace if you’re already signed in.

2.2 Windows

1. Download the Windows x64 EXE installer.
2. Double-click it and follow the setup wizard.
3. Choose an installation folder and complete setup.
4. Open Remy from the Start menu.

Check the installation: Remy opens to the sign-in screen or your workspace.

2.3 Check that you’re ready

• The installer matches your computer’s operating system and chip.
• The app opens successfully.
• Clicking Get started opens the sign-in page in your default browser.

If the installer won’t open or the app won’t start, see the relevant issue in section 7.

3. Sign in and find your way around

3.1 Sign in

1. Open Remy and click Get started.
2. Complete sign-in in your default browser.
3. Return to Remy to enter your workspace.

While it waits for browser sign-in, the app displays Continue signing in with your browser.

To start over, click Cancel sign-in, then Get started. If sign-in fails, use the message shown to check your connection or try signing in again.

3.2 Find the main controls

Open settings: Click your account at the bottom of the sidebar and choose Settings. To sign out, choose Log out from the account menu.

4. Work with projects and chats

4.1 Add an existing project

1. Open the project picker and click New project.
2. Enter a Project name in the Create project dialog.
3. Under Source folders, click Add folders the agent can read and edit and select the local folder that contains your code.
4. Check the name and folder, then click Create project.
5. Click New chat in that project to start working.

In most cases, choose the project’s root folder: the one containing its documentation, source code, and build configuration. For example:

example-project/       ← Add this folder
├── README.md
├── package.json       ← Project environment and dependencies (example)
├── src/
└── tests/

This is an example folder structure. The actual filenames depend on your project.

Source folders are the project folders Remy can read and edit. Check that you’ve selected the intended project before creating it, then describe the scope of each task in your prompt.

4.2 Use more than one folder

If your frontend and backend live in separate folders, for example, click Add folder under Source folders to include both.

When you add requirements, name the folders involved so Remy doesn’t have to infer them from their names.

This project has separate frontend and backend folders.
Check whether the parameters sent by the frontend match the backend’s validation rules.
List the relevant files and any differences.
Analyze only. Do not edit files.

4.3 Start a new chat or continue one

Check the current project name and folder before starting a task. In a new chat, describe the goal and constraints again.

5. Run tasks and review results

5.1 Choose a model and describe the task

Choose an available model beside the message box and adjust reasoning settings where offered. You can also select Dynamic to let Remy choose a model and move to a stronger one if the task gets stuck. The automatically selected model is not shown to you.

Users cannot currently switch models manually while a task is running. Refer to the options shown in the app for available models and reasoning settings.

Give Remy a task that is clear to carry out and easy to check:

5.2 Try a task template

Adapt the features and behaviors in these examples to your own project.

Find and fix a bug

When I change the status filter on page 3 of the order list, the list appears empty.
Results appear only after I return to page 1.

Find the cause and reset the page number when the filter changes.
Add and run relevant tests.
Change only the related logic, then summarize the files changed, check results, and any checks you could not complete.
Do not commit or push code yet.

Review existing changes without editing

Review the current uncommitted changes.
Focus on interactions between filtering, pagination, and sorting, and any missing edge cases.

List issues by severity, with file locations, triggering conditions, and suggested fixes.
Do not edit files, commit, or push code yet.

For a complete first coding task, see Quick Start.

5.3 Add context as you work

If Remy asks for more information or confirmation, read the request before responding. When requirements change, explain the new scope in the same chat.

One more constraint: keep this change on the frontend. Do not change the API.
If your approach requires an API change, explain why and describe the impact, then wait for my confirmation.

5.4 Review files and changes

• Use Explorer to browse project files and open what you want to inspect.
• Use Changes to review changes in the Git working tree. Select a file to see what was added, removed, or edited.
• If these panels aren’t open, choose Explorer or Changes from the panel add menu.

Changes shows the current Git working tree. It may include uncommitted work that was already there before the task started. Separate those changes from the work done for this task. A folder outside a Git repository has no diff against HEAD; inspect its files and the task summary directly.

5.5 Check whether the task is complete

If the result needs more work, describe the specific issue in the original chat. For example:

After I change a filter, the page number resets to 1, but the list does not refresh.
It should request fresh data as soon as the filter changes.

Fix only this issue, add and run relevant tests,
and summarize the change and check results. Do not commit or push code yet.

6. Update Remy

6.1 Check your version

On macOS, open Remy → About Remy to see the app version.

In the feedback dialog, you can also hover over Information included automatically to see Remy version and other information included with your report.

6.2 Check for updates

You may see one of these messages:

6.3 Install an update

1. Save your work and check whether any tasks are still running.
2. Once the update has downloaded, choose Install Update in the update prompt, or click Relaunch to update in the sidebar.
3. Follow the prompts to finish installation and reopen the app.

If Remy says a task is still running, finish that work before restarting to update.

7. Troubleshooting and known limitations

7.1 Installation, sign-in, and task issues

7.2 Known limitations

• Users cannot switch models manually while a task is running; Dynamic can move to a stronger model automatically.
• Branch creates a new chat branch; it does not undo file changes.
• Browser Use and Computer Use currently support macOS only.
• When working on a local project, keep your computer, Remy, and the task’s required environment available. See the Cloud guide for cloud tasks.

8. Get help and explore further

8.1 Report an issue

1. Open the relevant chat’s menu and choose Send feedback.
2. In Submit feedback to Remy, choose a feedback type and impact level, then describe the issue.
3. Add screenshots or attachments as needed, then click Submit feedback.

You can also right-click a chat in the sidebar and choose Send feedback.

Describe how to reproduce the issue, what you expected, and what happened. Include any error messages or relevant screenshots.

8.2 Rate a response

Use the thumbs-up or thumbs-down button below a response and explain what helped or what didn’t meet your expectations. The task’s goal, the problem you encountered, and the result you expected help us understand what to improve.

If you can’t find the feedback option or can’t open the app, contact support at support@corepass.com.

8.3 Keep exploring