Run Megaplan plans persistently in a provider-managed cloud container.
npx skills add https://github.com/peteromallet/arnold --skill megaplan-cloud
Please help me install this Agent Skill. Skill: megaplan-cloud Source: https://github.com/peteromallet/arnold/tree/main/megaplan/data/_codex_skills/megaplan-cloud Command: npx skills add https://github.com/peteromallet/arnold --skill megaplan-cloud
Megaplan Cloud solves the problem of keeping long-running, multi-repo intelligence pipelines running reliably even after your local terminal session ends.
It runs a Megaplan plan inside a provider-managed container with a persistent workspace volume, supports multi-repo planning via extra repositories, and manages multi-tenant concurrent chain runs using dedicated tmux sessions and log isolation. Use it when you need a long-lived dev box, a chain that must outlast local downtime, or an isolated sandbox that can be shared across concurrent runs.
Run the command "megaplan cloud init" to scaffold a cloud.yaml at your project root.
High-intent search queries and answers about installing and using this skill.
To keep multi-repo pipelines running after your local terminal session ends, you need a cloud execution environment with a persistent workspace volume. This setup maintains long-running operations reliably inside a provider-managed container, ensuring your workflows survive local downtime.
The best way to run concurrent chain execution with isolated tmux sessions is using a multi-tenant cloud execution environment. It manages concurrent chain runs by establishing dedicated tmux sessions with strict log isolation for each specific chain_session.
To scaffold a cloud configuration file for persistent cloud execution, run the initialization command at your project root. This generates a cloud.yaml file where you define extra_repos for multi-repo workspaces and configure secrets-driven deploy-time settings.
Railway supports long-lived dev boxes with persistent volume-backed workspaces when configured as a provider-managed container runtime. You must correctly handle cloud.yaml fields and secrets-driven deploy-time configuration to ensure persistent cloud execution.
You can run multi-repo workspaces in a provider-managed container runtime by defining extra repositories in your cloud.yaml file. This allows your persistent workspace to manage multi-repo planning and execute intelligence pipelines concurrently.
modu-aiAutomate Railway deployment of containerized applications with Docker/Nixpacks and multi-service support.
alangebManage asynchronous background processes and tmux sessions for concurrent task execution.
DITEKmaxConfigure Angular v20+ dependency injection with inject() and token-driven providers.
ai-enhanced-engineerAutomate CI/CD pipeline design on Google Cloud Platform with Cloud Build and Cloud Deploy.
