always-on-claude

skill
Guvenlik Denetimi
Basarisiz
Health Uyari
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Basarisiz
  • rm -rf — Recursive force deletion command in .claude/settings.json
  • rm -rf — Recursive force deletion command in .github/workflows/build-ami.yml
  • rm -rf — Recursive force deletion command in .github/workflows/pr-fix.lock.yml
  • process.env — Environment variable access in .github/workflows/pr-fix.lock.yml
Permissions Gecti
  • Permissions — No dangerous permissions requested
Purpose
This tool provisions an always-on, remote development environment on AWS EC2 using Docker, allowing you to run Claude Code persistently and connect via SSH from any device.

Security Assessment
The overall risk is High. The tool is designed to execute shell commands, access your local and remote environments, and make network requests via SSH and AWS provisioning. While no hardcoded secrets were detected, the codebase contains multiple recursive force deletion commands (`rm -rf`) inside configuration files and GitHub workflows. Although likely intended for cleanup and teardown routines, these commands pose a significant risk of accidental data loss if triggered improperly. Additionally, environment variables are accessed in workflows, which warrants caution. You are also required to provide your own AWS credentials and Anthropic API keys, which means sensitive authentication tokens will be present in your environment.

Quality Assessment
The project is very new and has extremely low visibility, currently sitting at only 5 GitHub stars. However, it is actively maintained, as indicated by very recent repository pushes. It uses the permissive MIT license and includes a clear, detailed description and documentation. The low community adoption means it has not been widely peer-reviewed for security or stability.

Verdict
Use with caution — while the setup is actively maintained and properly licensed, the low community visibility and presence of destructive shell commands mean you should thoroughly review the code and workflows before trusting it with your AWS account and sensitive credentials.
SUMMARY

Always-on Claude Code dev environment on EC2 + Docker Compose (~$22/mo)

README.md

Always-On Claude Code

Your own persistent Claude Code workspace on AWS. SSH in from any device, reconnect where you left off.

~$14/mo on AWS. One slash command to set up.


The Problem

Running Claude Code locally... Always-On Claude Code
Dies when your laptop closes Runs 24/7 on a server or Mac
Tied to one machine SSH from laptop, phone, tablet
Session lost on disconnect Reconnect and pick up where you left off
No background tasks Claude keeps working while you sleep

Two Options

Hosted Cloud (AWS EC2)
Best for Zero setup, no AWS needed Dedicated remote server
Cost $39/mo ~$14/mo (EC2 + EBS)
Setup Pay and connect /provision
Teardown Cancel subscription /destroy
Networking Public IP Public IP or Tailscale
You manage Nothing AWS account + instance

Hosted

Don't want to manage infrastructure? Always-On Claude Hosted gives you a fully managed workspace — no AWS account, no Docker, no setup. Pay, get an SSH key, connect.


Quick Start

Prerequisites

  • Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
  • Claude auth — either a subscription (Pro/Max) or an API key (ANTHROPIC_API_KEY)
  • AWS account with CLI configured (brew install awscli && aws configure)

1. Clone and provision

git clone https://github.com/verkyyi/always-on-claude.git
cd always-on-claude
claude

Inside the Claude Code session:

/provision

Claude walks you through the entire AWS setup — SSH keys, security groups, instance launch — and connects you in ~40 seconds.

2. Connect

ssh claude-dev

On first login, Claude walks you through setup — git config, GitHub auth, and cloning your first repo. After that, you'll see a workspace picker to launch Claude Code in any repo.

3. Tear down when done

Back in your local Claude Code session:

/destroy

Slash Commands

All lifecycle operations run from inside a Claude Code session in this repo:

Command What it does
/provision Launch a new workspace on AWS (~40s)
/destroy Tear down all AWS resources
/update Apply updates to a running workspace
/tailscale Set up Tailscale for private SSH
/workspace Manage repos and git worktrees

What You Get

Your Mac / Phone / Tablet
    │
    └── SSH
         └── Ubuntu 24.04 (EC2 t4g.small, 20GB)
              ├── Docker container (claude-dev)
              │    ├── Claude Code
              │    ├── Node.js 22, Bun, npm
              │    ├── Git, GitHub CLI, AWS CLI
              │    └── Your project repos
              ├── tmux (session persistence)
              └── Workspace picker on SSH connect

Everything persists — auth, settings, repos, tmux sessions, Claude history — all survive container restarts and reconnects.


How It Works

Component Purpose
Pre-built AMI Docker + Claude Code pre-installed, arm64 + x86_64 (~40s boot)
Docker container Isolated workspace with dev tools, bind-mounted for persistence
tmux Sessions survive SSH disconnects
Login menu SSH in → choose Claude Code, bash, or host shell

Cost

What Cost
EC2 t4g.small (on-demand) ~$12/mo
20GB gp3 EBS ~$1.60/mo
Total ~$14/mo

Stop the instance when not in use to save money. No additional fees — you bring your own Claude subscription.


Script Fallbacks

Destroy has a script fallback for automation:

bash <(curl -fsSL https://raw.githubusercontent.com/verkyyi/always-on-claude/main/scripts/deploy/destroy.sh)

For details, see Deployment.


Further Reading

  • Architecture — Docker, networking, sessions, resource limits, update pipeline
  • Deployment — provisioning, install, config, AMI, portable mode, Tailscale
  • Operations — onboarding, sessions, worktrees, updates, mobile, slash commands
  • CI/CD — all GitHub Actions workflows

License

MIT

Yorumlar (0)

Sonuc bulunamadi