mskangg contributor

Remote Claude Code

Add the remote-claude-code marketplace so you can drive the same local or cloud agent session from Slack slash commands on desktop or phone without starting a new IDE.

Overview

remote-claude-code is a plugin marketplace for the Operate phase that lets you control ongoing Claude Code, Codex, and Gemini CLI sessions from Slack without migrating to a new remote IDE.

What is this marketplace?

  • Slack-first remote UI for existing agent sessions—no new agent platform or mandatory remote IDE
  • Slash commands `/cc` (Claude Code), `/cx` (Codex), `/gm` (Gemini CLI) on one self-hosted stack
  • Free, unlimited sessions, self-hosted; built with Rust per project badges
  • Preserves the environment you already work in; phone or Slack continues the same session
  • Setup plugin path: `remote-claude-code-setup@remote-claude-code` after marketplace add
  • Marketplace lists 1 plugin focused on remote setup (remote-claude-code-setup)
  • Documents 3 Slack slash commands: `/cc`, `/cx`, `/gm`
  • Project positions free unlimited sessions with Rust-based self-hosted transport

Compatible agents: Claude Code, Codex, any compatible agent

Community signal: 2 GitHub stars.

What problem does it solve?

When you step away from your desk, your in-progress agent session is trapped on the original machine unless you adopt another platform or IDE.

Who is it for?

Self-hosting indie builders who live in Claude Code or Codex and want Slack—or mobile Slack—as a zero-extra-subscription remote control for active sessions.

Skip if: Teams that want a fully managed cloud IDE, cannot run self-hosted bridges, or do not use Slack as an operational channel.

What do I get? / Deliverables

After marketplace and setup plugin install, you steer the same agent session from Slack slash commands on any device while the original environment keeps running.

  • Configured remote-claude-code-setup plugin and Slack slash routing
  • Ongoing remote control of `/cc`, `/cx`, and `/gm` mapped agent sessions
  • Validated environment via documented Doctor and Quickstart checks

Plugins in this marketplace

1 plugin — install individually after you add the marketplace.

Recommended Marketplaces

Journey fit

Remote session control matters most when you are operating an in-flight dev environment—continuing, steering, and unblocking work without sitting at the original machine. iterate fits ongoing operation: same Claude Code, Codex, or Gemini session extended through Slack rather than replatforming the agent.

How it compares

Self-hosted Slack transport for existing agent sessions—not a new coding agent marketplace or hosted remote development product.

Common Questions / FAQ

Who is Remote Claude Code for?

It is for builders already using Claude Code, Codex, or Gemini locally or in the cloud who want Slack slash commands to continue the same session from anywhere.

When should I use Remote Claude Code?

Use it during Operate when you need to iterate, approve, or nudge an active agent run from mobile or chat without cloning the workspace into a new remote IDE.

How do I add Remote Claude Code to my agent?

Clone the repo, run Claude Code, execute `/plugin marketplace add mskangg/Remote Claude Code`, install `Remote Claude Code-setup@Remote Claude Code`, complete Slack and Doctor setup, then use `/cc`, `/cx`, or `/gm` in Slack.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.