MENLO PARK, Calif. — Remy, the AI coding agent from Corepass, does not ask developers to change where they work. It runs as a desktop app, as a command-line tool, in a web browser and on a phone, all under one account, and it can hand a long job to a cloud agent that keeps working after the laptop closes.
| Where | What it is for | Requirements |
|---|---|---|
| Desktop | Tasks, files, code changes and results in one workspace | macOS 12 or later (Apple silicon and Intel); Windows 10 and 11 (x64); Linux AppImage (x86_64) |
| Command line | Give Remy a task and review the results without leaving the terminal | Node.js 18 or later; npm install -g @corepassinc/remy |
| Web | Follow tasks and review results from any browser | Nothing to install |
| Mobile | Get notified when a task needs you, and answer Remy | iPhone, iPad and Android |
A job that outlasts the laptop
The cloud is where Remy goes when a task is long. A developer can run Remy on a GitHub repository in the cloud or move a local task there, and the result comes back as a pull request. Cloud tasks keep running when the developer’s computer is offline; in the meantime, the developer can add requests and answer Remy’s questions from a phone, then check the result in any browser.
There is one boundary the company spells out: cloud results do not sync back to local files. The pull request is the hand-off.
Cloud tasks keep running when the developer’s computer is offline. The pull request is the hand-off.
In the thread where the request lives
In Slack, mentioning @Remy in a thread hands the agent whatever the thread is asking for. Remy posts progress in the same thread and shares the pull request when the work is ready, so the people who asked see the answer where they asked.
More than writing code
The documentation also describes work around the code. Remy can review a set of changes and report findings by severity, call subagents for parts of a task — on its own or when asked — and branch a conversation to try another direction, though a branch does not undo file changes already made. It can compare sources a developer provides and make a recommendation with explicit conditions, and turn meeting notes into decisions, action items and open questions. The documentation is specific about limits there, too: Remy does not transcribe audio, send messages or create tickets from those notes.
Bringing history along
For developers switching tools, Remy can import conversation history from Claude Code, Codex, Cursor and grok-build, according to its documentation. The conversation comes across; tool results, reasoning and attachments do not. Remy also works with project rules, Skills, plugins and MCP services, the documentation says.