Extensions and integrations

Scope: Primarily the current desktop app. Custom MCP configuration also includes a CLI method. Browser and computer-use examples use the macOS desktop app.

Use project rules, Skills, plugins, and MCP services to adapt Remy to your work and connect the tools you need. After installation, check that the capability is enabled, any required authorization is complete, and it works in an actual task.

1. Choose the right extension

MCP is a way to connect tools and services. What Remy can read or do through a connection depends on the service's capabilities, the signed-in account, and the access granted.

2. Install and manage plugins

2.1 Install from the directory

1. Open Settings → Plugins.
2. Click Browse and find the plugin in the directory.
3. Open its details to review its purpose, source, and included capabilities.
4. Click the install button and wait for the result.
5. If sign-in or other setup is required, follow the instructions in the details.
6. When Try now is available, click it to start a task and explain what you want to do.

For example, when trying a source service for the first time, start with a focused reading task:

Use the service I just connected to find project onboarding documents I am allowed to access.
List their titles, sources, and a brief description. Read only; do not create, edit, or delete content.

Check the returned sources to confirm the account and material are correct before moving on to more complex tasks.

2.2 Check whether a capability is enabled

In Settings → Plugins, filter by type, source, or status. Open an item's details to review its enabled state and any messages.

A plugin, the Skills it provides, and its MCP services may have separate switches. A child item may still be unavailable if its parent plugin is disabled, even when the child's own switch is on. Follow the item's effective status and explanation rather than checking only one switch.

Organization policies may restrict capabilities managed by a team. If an action is unavailable, read the reason and contact the team's administrator.

2.3 Disable uninstall or disconnect

Disabling, uninstalling, and disconnecting are different actions. To end an external service's authorization, also check that service's own access controls. Turning off a capability does not mean every authorization has been revoked.

3. Install and use a Skill

3.1 Install an existing Skill

1. Open Settings → Plugins and filter by Skill.
2. Click Install Skill….
3. Select the Skill folder or .skill file you were given and wait for installation.
4. Open the Skill's details and read its purpose and requirements.
5. Check that it is available, click Try now, and enter a real task.

For a Skill supplied by a plugin, use that plugin's installation and management controls. If Uninstall is unavailable, check the Skill's source and management information.

3.2 Create your own Skill

If Create Skill is available under the Skill filter, click it and explain in the new chat:

• Which task you repeat.
• The steps or reference material it should follow.
• The required output structure and completion criteria.

For example:

Help me create a Skill for preparing weekly reports.
The input is work notes I provide. The output should include completed work, current issues, and plans for next week.
Do not invent progress, owners, or dates. Mark missing information as needing confirmation.
Ask me about any necessary requirements first, then create the Skill and explain how to try it.

Try it with a small set of real material and check whether it works as intended. Successful installation or creation does not mean it will be used automatically for every task. You can explicitly name the Skill in your request.

4. Connect an MCP service

4.1 Use a service supplied by a plugin

1. Install the plugin and open its MCP service entry in the plugin details.
2. If account authorization is required, click Not connected, or continue the sign-in flow that opened after installation.
3. Check the account and permissions on the authorization page. Complete sign-in and return to Remy.
4. Wait for Connected, then run a small task to check that the service can read or act as expected.

A service that does not require account sign-in may not show an authorization button. If it needs additional configuration, follow the service's setup instructions.

4.2 Add a custom service through the CLI

Follow the CLI Guide to install the CLI and sign in. Obtain the JSON configuration object for a single MCP service from its provider and save it as a local file, such as my-mcp-server.json.

Replace the project path, service ID, and configuration-file path below with your own values:

remy --workspace "/path/to/project" config mcp list
remy --workspace "/path/to/project" config mcp set my-server --file "./my-mcp-server.json"
remy --workspace "/path/to/project" config mcp show my-server

set creates or replaces a custom service with that ID. Check for an existing configuration before running it. Do not use it to overwrite a service owned by a plugin.

To enable or disable the service:

remy --workspace "/path/to/project" config mcp enable my-server
remy --workspace "/path/to/project" config mcp disable my-server

These commands enable and disable the service respectively; choose the one you need. Review the command's result and the scope it reports. The configuration needs to be read by a new runtime session. Reload the runtime or restart an existing Desktop or CLI session before checking the change.

Configuration files may contain credentials. Do not put real secrets directly in command arguments or chat messages. Saving the configuration does not confirm that the remote service is connected. Check its runtime requirements, authorization, and an actual tool call.

5. Use project rules

If your project has instructions such as AGENTS.md or CLAUDE.md, ask Remy to read the applicable guidance before starting work. Rules should explain the project structure, scope of changes, checks, and delivery requirements.

Read the applicable AGENTS.md, CLAUDE.md, and README in this project first.
Summarize the conventions and checks relevant to this task before working on the requirement.
If instructions conflict or evidence is missing, explain the issue first.

Project rules describe how work should be done. File access, command execution, and external actions remain subject to actual permission controls. Editing an instruction file does not replace granting access.

6. Use browsers and desktop apps

6.1 Work with a web page

Specify the page and browser in your task. Remy's built-in browser and Chrome connected through the extension are separate entry points. Do not assume they share the same sign-in state.

Open the URL I provide in the built-in browser, read the help page, and list the installation steps.
Read only. Do not submit forms or change account settings.

If you need your local Chrome browser, say so in the task. When Remy in Chrome — not installed appears, click Get the extension, finish installation, then return and ask again. If the extension is installed but cannot be reached, first check that Chrome is running and read the connection message. Installed does not mean connected. Sign in to a website in the corresponding browser when required.

6.2 Grant operating-system permissions for computer use

1. In Settings → Plugins, open the computer-use capability's details.
2. Find Permissions and check Accessibility and Screen Recording.
3. If access is needed, click Open System Settings and grant it to the corresponding app or component in macOS settings.
4. Return to Remy, click Recheck, and review the status.
5. If the system asks you to reopen the app, follow that instruction before trying the task again.

You grant these permissions in System Settings. Remy cannot turn them on for you. If Helper missing appears, the app's missing component must be addressed; granting permissions repeatedly will not fix it.

For a first task, ask Remy to read specific content in an open app. Check the result before allowing changes. Stopping execution or disabling a capability does not automatically undo external actions already taken.

7. Use GitHub and Slack

GitHub repository tasks: Authorize GitHub through the Cloud connection entry, choose a repository and branch, then start a task. Follow the Cloud Guide for the complete steps.

Access Slack from Remy: Use the corresponding plugin or MCP connection, authorize your account, and give the task in a Remy chat. Read and write access is limited by the Slack account's permissions and the connection's scope.

Call Remy from Slack: In a Slack environment where Remy Tag is already enabled, mention @Remy to start cloud tasks and review their results. This works in the other direction from connecting Slack within Remy. Installing a Slack plugin does not enable Remy Tag.

8. Common questions

If the issue persists, record the capability name, the step that failed, the error message, and your Remy version. Follow the Desktop Guide to send feedback. Do not include real secrets in the report.