Frequently asked questions

Answers to common questions about access, models, tasks, teams, permissions, and support. New to Remy? Follow the Quick Start to complete your first small task.

• Accounts and getting started
• Model selection and automatic routing
• Local tasks and Cloud
• Team and member plans
• Files, permissions, and data
• Feedback and support

1. Accounts and getting started

1.1 How do I get access?

Remy is opening to teams in waves. Request early access on the Remy page, and we’ll email you when your spot is ready. Then sign in with your Corepass account the first time you open Remy; the app takes you through sign-in in your browser.

If you are joining an existing Team, a team invitation is sufficient. You do not need anything else to sign in.

1.2 Do I need a model-provider account or API key?

No. Across Remy clients, you access models through your Remy account. The standard workflow does not require a separate model-provider account or your own model API key. Available models depend on your plan and the options shown in the product.

1.3 Where can I use Remy today?

The current release includes Desktop, CLI, and Cloud.

For installation instructions, see the Desktop Guide and CLI Guide.

1.4 Do I need Python or Node.js to install Remy?

The desktop app includes its runtime. You do not need to install Python or Node.js separately to install Remy.

The CLI is installed through npm and requires Node.js 18 or later and npm. The standard installation does not require a separate Python or Rust installation.

Your own projects and tests still need their required tools and dependencies, whichever Remy client you use.

1.5 I’m signed in on desktop. Do I need to sign in to the CLI too?

Yes. Desktop and CLI use the same Remy account, but require separate sign-ins. When you first use the CLI, run:

remy login

After signing in, use remy whoami to check the current account and team scope. See the CLI Guide for the full sign-in flow.

1.6 What should I try first?

Start with a small, well-defined change in an existing project—something you can check easily, such as fixing a known issue or adding a button to an existing page.

Ask Remy to understand the relevant code first, then describe the change and review the files and test results. The Quick Start includes prompts you can adapt to your project.

2. Model selection and automatic routing

2.1 Which models does Remy support?

Remy supports open-source and proprietary models, including models from OpenAI and Anthropic, along with the Kimi, GLM, DeepSeek, Grok, and Qwen families.

The selection changes over time. Check the model list in your account for the options currently available to you. Models and reasoning settings may vary by plan and the options offered in the product.

2.2 How is choosing a model different from automatic routing?

• Choose a model: Select an available model for the task. Where reasoning settings are offered, adjust them to fit the work.
• Use automatic routing: Select Dynamic to let Remy choose a model and move to a stronger one if the task gets stuck. The selected model is not shown to you.

With either option, review the result against your task’s requirements.

2.3 Can I switch models while a task is running?

You cannot currently switch models manually during execution. Choose a model or Dynamic before starting the task. Dynamic can move to a stronger model automatically during execution.

3. Local tasks and Cloud

3.1 When should I work locally, and when should I use Cloud?

See the Desktop Guide, CLI Guide, and Cloud Guide for instructions.

3.2 Do I need to clone a repository locally before starting a Cloud task?

No. Once you have connected and authorized GitHub, you can select an accessible repository and branch in the desktop app and create a cloud task directly.

To continue an existing local conversation and its changes, use the local-to-cloud handoff instead. For either path, check the repository, branch, and permissions needed for the task.

3.3 Will a Cloud task keep running if I close the app or turn off my computer?

Yes. Once the task is running in the cloud, it does not depend on your computer staying online. Closing the desktop app, disconnecting, or shutting down your computer does not stop the task because of that local disconnection.

You need a connection to submit tasks, check progress, or respond to requests for input. If a task is waiting for information or approval, it needs your response to continue. A completed upload or handoff does not mean the task itself is complete.

3.4 What transfers when I move a local task to Cloud?

Remy transfers supported conversation content and lets you choose whether to include eligible uncommitted files:

Cloud creates a new branch to continue the task. Ignored files, credentials, and sign-in state are not uploaded by default. Transfers are also subject to path, file size, file count, and content checks.

Dependencies installed on your computer and services running locally are not automatically available in the cloud. See the Cloud Guide for the transfer scope and checks.

3.5 Do Cloud changes sync back to my local files automatically?

No. Cloud task results do not automatically write back to your local files.

Review the cloud results, choose whether to deliver the changes through a pull request, and bring them into your local project through your usual Git workflow. Creating a PR, pushing, and merging require the appropriate repository access and authorization.

3.6 Can I attach a local file or screenshot directly to a Cloud message?

Cloud messages currently support text only. You cannot send local attachments, folder references, or code references directly in a Cloud message.

If the task needs local uncommitted changes, use the local-to-cloud handoff to review and select eligible files. That transfer is separate from adding an attachment to a Cloud message.

3.7 Can I pick up a Cloud task on another device?

Yes. Sign in on the other device with the corresponding account and team scope. You can follow the cloud task, add instructions, and review the results.

The CLI can start a handoff and check its progress. remy cloud status reports the transfer state. Use a desktop client with Cloud support to follow the full task, continue the conversation, and review results.

3.8 Does Remy automatically verify every task?

Verification is a tool for checking whether a task meets its requirements. You can ask Remy to use it, and the model may also decide to call it based on the task. It does not mean every task automatically runs the same set of checks.

Make your acceptance criteria explicit. For example:

When the work is ready, use Verification to check it against the original requirements.
Explain which requirements are met, what is still missing, and which checks actually ran with their results.
List any checks you could not complete and explain why.

Review the actual changes, test output, and working result when deciding whether the task is complete.

3.9 Does Changes show only the edits Remy made in this task?

Not necessarily. Changes in the desktop app shows uncommitted changes in the current Git working tree relative to HEAD. It may include work that was already there before the task started.

Use the task summary and file diffs to distinguish existing work from the task’s changes. For a directory that is not a Git repository, inspect the files and result summary directly.

3.10 Can I start a Remy task from Slack?

Yes. Once the connection, account linking, and permissions are configured, use Remy Tag to mention @Remy in Slack and start a task. You can follow its feedback and results there.

Remy Tag is a Cloud feature: tasks run in the cloud. The information it can read and the actions it can take depend on the connection setup and permissions granted.

4. Team and member plans

4.1 How do I get my team started?

You can select Create a team from the account menu, enter a team name, choose seats, and complete any required purchase steps before inviting members. Those members do not need a separate Remy account. Joining the team and receiving a product seat are separate steps.

Team provides invitations, role and seat assignment, centralized billing, and additional usage controls. Available management actions depend on the active account's permissions.

4.2 What is the difference between Team Standard and Team Premium?

The two seat types differ in usage allowances and available models. Check the product for current allowances, models, prices, and benefits. Team charges are managed through centralized billing.

4.3 Can team members pool allowances or have separate action permissions?

Members use the allowance included with their own seats. A team can also purchase and enable additional Usage credits for eligible members to use beyond that allowance. This does not automatically pool members' included allowances.

Team supports member roles and administration permissions, along with organization, seat-tier, and member spend limits. Administration roles do not replace authorization for agent actions in a chat, operating system, or connected service.

4.4 What happens when a seat is unassigned or a member is removed?

For team access or usage issues, ask an administrator to check roles, seats, balances, and limits.

5. Files, permissions, and data

5.1 How do I specify what Remy can access or change?

For local work, add the project directory under Source folders in the desktop app. In the CLI, enter the project directory or specify a working directory. Then describe the actions you want Remy to take. For example:

Analyze only the code related to the sign-in failure in this project. Explain the cause and recommend a fix.
Do not edit files, install dependencies, commit, or push changes yet.

Your instructions describe the intended scope. Actual access and execution also depend on current permission settings, approvals, and operating-system permissions. In the CLI, use /permissions to view the current conversation’s permissions and follow the options shown.

Browser actions, computer actions, and connected services also need their required configuration and authorization.

5.2 Are Browser Use and Computer Use available on Windows?

Not currently. Both capabilities support macOS only. The apps, browsers, and pages Remy can work with depend on your setup and permissions.

5.3 Can I add my own Skills, plugins, or MCP services?

Yes. You can install, enable, and manage Skills and plugins, and add and configure MCP services.

For an external service, complete its connection and authorization flow. Accessible content and available actions depend on the connected account and permissions granted.

5.4 Does importing another agent’s history change the original records?

No. Remy reads local history and creates a copy so you can continue the work in Remy. The original records remain read-only.

Supported sources are Claude Code, Codex, Cursor, and grok-build. Tool results, reasoning, and attachments are not copied. To continue working on the original project, you also need access to its directory.

5.5 Does branching a conversation undo file changes?

No. Branch creates a conversation branch. It does not undo file edits that have already happened. Check the project’s current files and uncommitted changes before trying a different approach.

5.6 How does Remy upload, store, and use my code, conversations, and files?

It depends on your plan and settings. The Trust Center explains, plan by plan, whether your sessions help improve Remy, and the Privacy Policy covers how your data is stored and protected.

6. Feedback and support

6.1 The result isn’t what I expected. Should I continue the chat or report an issue?

To refine the result, continue in the same chat. Explain what happened, what you expected, and what you want changed so Remy can keep working.

Send feedback if you encounter an app error, a feature does not work, or you want to report an issue to the product team. For installation, sign-in, or connection problems, start with the troubleshooting section of the Desktop, CLI, or Cloud guide.

6.2 How do I send feedback or rate a response?

If you cannot open the app or use its feedback entry, contact support at support@corepass.com.

Check the submission result. In the CLI, a report is submitted only when the command confirms success and returns a feedback ID. If it shows Result unknown, check with support before submitting again to avoid a duplicate report.

6.3 What information should I include in a report?

The following details help us investigate:

• The client, Remy version, and operating system.
• Steps to reproduce the issue.
• What you expected and what actually happened.
• Error messages or screenshots.
• Anything you have already tried.

For the description file used by CLI submissions, see the CLI Guide.