Get started
Quick start
Complete and review your first coding task.
Use the Remy desktop app to make a small change in an existing project and review the results.
1. Before you start
- A Remy account: Request early access on the Remy page. Once you’re in, sign in with your Corepass account.
- An internet connection: Your Remy account provides access to models. You don’t need a separate model-provider account or API key.
- A local project: Choose a project you can access and run, and a small, clearly scoped change.
The Remy desktop app includes its own runtime, so you don’t need to install Python or Node.js to use Remy. Your project and its tests still need their own environment and dependencies.
2. Download and sign in
- Go to the Remy download page and choose the installer for your computer:
- macOS: Choose the Apple silicon or Intel version (DMG) for your Mac.
- Windows: Choose the x64 version (EXE).
- Install and open Remy, then click Get started.
- Sign in with your browser, then return to the Remy app.
You’re ready to: Create a project and start a chat.
3. Add your project and start a chat
- Create a project and add your local project folder under Source folders.
- In that project, click New chat.
- Choose an available model beside the input. If reasoning settings are available, adjust them as needed.
Add the folder that contains your code. In the prompts below, “this project” refers to the files in that folder.
With Dynamic, Remy chooses a model for each task and can move to a stronger model if it gets stuck. Available models and reasoning settings are shown in the app. Users cannot currently switch models manually while a task is running.
You’re ready to: Work on your code in a chat with access to the project.
4. Complete your first coding task
Pick a small change with a result you can check, such as fixing a bug or adding a button to a page.
The example below adds a “Clear filters” button to an order list. Adapt the feature, fields, and requirements to your own project.
4.1 Understand the relevant code
Send this in your new chat:
I’m going to update the order list in this project.
First, read the project documentation and relevant instructions. Explain how to run the project and its relevant tests.
Identify the key files for the order list and explain how filtering, pagination, and sorting currently work.
Do not edit files, install dependencies, commit, or push code yet.
Check that Remy has found the right part of the project, that the files it lists exist, and that its run and test instructions are supported by the project documentation or code. If anything is off, provide more context about the folders, files, or requirements before continuing.
4.2 Make the change
Continue in the same chat:
Add a “Clear filters” button to the order list.
Requirements:
1. Clear the keyword and status filters.
2. Reset to page 1 and refresh the list.
3. Preserve the current sort order.
4. Follow the project’s existing styles and only change what this task requires.
Add and run relevant tests. When finished, summarize the files changed, the checks you ran, and their results.
If you cannot complete a check, explain why.
Do not commit or push code yet.
If Remy asks for more information or confirmation during the task, review the request before continuing.
What to expect: Code changes you can review, a task summary, and the results of any tests or other checks.
5. Review the results and refine
Review the work in this order:
- Review the changes: Check which files changed and whether the changes stay within the task’s scope.
- Review the checks: Confirm which tests or checks actually ran and whether they passed. If a check did not run or failed, address the cause before verifying again.
- Try the feature: Run the project, set filters, and move to another page of results. Click “Clear filters.” Confirm that the keyword and status filters are cleared, the list returns to page 1 and refreshes, and the sort order stays the same.
If you chose a different task, check the result against the requirements in your prompt.
If the result needs work, continue in the same chat. Describe what happened, what you expected, and what should change. For example:
After I click “Clear filters,” the keyword and status filters are cleared, but the list stays on page 3.
It should return to page 1 and refresh.
Fix only this issue, add and run relevant tests, and summarize the change and verification results.
Do not commit or push code yet.
Branching a chat does not undo file changes. When you continue a task, work from the files as they currently exist in your project.
6. Get help and share feedback
App or feature issues
Open ··· → Send feedback at the top right of the chat and include:
- The steps you took.
- What happened.
- What you expected to happen.
- Your Remy version, with screenshots if helpful.
Can’t find the feedback option? Contact support at support@corepass.com.
Responses and task results
Use the thumbs-up or thumbs-down button below a response and add details. For example, tell us whether Remy understood the task, whether the changes met your requirements, and whether the check results were clear.
7. Learn more
For more ways to use Remy, guides, and answers to common questions, visit Docs on the Remy website.