Agent Plugins Marketplace
← All plugins

subroutine-remote

v0.8.19

Agent-native task management for complex projects, where the decisions live beside the work. Connects this session to a Subroutine instance somebody else runs — an address and a token, and nothing to install. It is a Claude Code plugin, so it runs wherever those run — but the two fields it needs are filled in with '/plugin', which the VS Code extension does not offer, so setting it up wants a terminal once even if you never use one again. A hosted surface that adds servers as connectors instead — claude.ai, and the apps that offer an 'Add custom connector' dialog — cannot use it: a connector authenticates with OAuth, which Subroutine does not offer yet, so there is nowhere to put the token you were given. Use 'subroutine' instead if your work lives on this machine.

Claude Code1 Skill

By Simon Holliday5 GitHub starsUpdated last week

Directory evidence

Runtimes
Claude Code
Parsed components
1 skill or MCP entry
Source updated
Sep 16, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install subroutine-remote for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install subroutine-remote@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/simonholliday/subroutine

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/subroutine-remote/.

Plugin files

plugins/subroutine-remote/
├── .claude-plugin/plugin.json
└── skills/subroutine/SKILL.md

Included Skills1

subroutineskills/subroutine/SKILL.md

Track work in Subroutine — file tasks, find what can actually be started, record what happened, and write down conclusions the next session will need. **Read this before the first subroutine_* call of a session, including a read-only one.** It carries conventions the tool descriptions do not — how to open so you are not answering from a stale snapshot, how to ask for work that can actually be started, what a title has to say, and which end of a blocks link is the blocker. Also when the user asks what to work on, reports a problem, asks you to log or file something, finishes a piece of work, wonders where something was left, asks whether Subroutine is connected or what is in it, or says this project uses Subroutine — and for adopting Subroutine in a project that does not use it yet.

Plugin manifests1

plugins/subroutine-remote/.claude-plugin/plugin.json
{
  "name": "subroutine-remote",
  "version": "0.8.19",
  "description": "Agent-native task management for complex projects, where the decisions live beside the work. Connects this session to a Subroutine instance somebody else runs — an address and a token, and nothing to install. It is a Claude Code plugin, so it runs wherever those run — but the two fields it needs are filled in with '/plugin', which the VS Code extension does not offer, so setting it up wants a terminal once even if you never use one again. A hosted surface that adds servers as connectors instead — claude.ai, and the apps that offer an 'Add custom connector' dialog — cannot use it: a connector authenticates with OAuth, which Subroutine does not offer yet, so there is nowhere to put the token you were given. Use 'subroutine' instead if your work lives on this machine.",
  "author": {
    "name": "Simon Holliday",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/simonholliday/subroutine",
  "keywords": [
    "tasks",
    "project-management",
    "todo",
    "self-hosted",
    "planning"
  ],
  "userConfig": {
    "url": {
      "type": "string",
      "title": "The instance address",
      "description": "The address of the Subroutine instance you are working against, ending in /mcp — for example https://subroutine.example.com/mcp. Whoever runs the instance gives you this. If it holds more than one workspace, the address they give you should name the one your work belongs in: https://subroutine.example.com/mcp?workspace=projects. Leave this empty until you have it: nothing is broken while it is blank, and this session simply has no Subroutine tools. Your editor connects from this machine, so a server on your own network or behind a VPN works as well as a public one.",
      "default": ""
    },
    "token": {
      "type": "string",
      "title": "Your token",
      "description": "The credential you were given for that instance, starting 'sr_'. Paste the token on its own — not the word 'Bearer' in front of it. It says who you are, so what you file is attributed to you rather than to whoever set the server up, and it decides what you are allowed to do. Your editor stores this, not Subroutine, and where it puts it depends on the editor and the machine — on Windows it is a file under your home directory. Treat it as you would any password there. If a call comes back saying the token was rejected, ask for a new one rather than editing this: they expire and they can be revoked.",
      "sensitive": true,
      "default": ""
    }
  }
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[subroutine-remote on Agent Plugins Marketplace](https://pluginsmp.com/plugins/subroutine-remote)