claude-ops Control

    1

    Always-on Claude Code sessions on Linux, one systemd service and one Telegram bot per project, plus a control bot that shows all sessions on one Telegram screen and restarts one from your phone.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    claude-ops Control

    Example session with this skill installed

    Set up claude-ops Control so all my projects run as always-on sessions and I can see and restart them from one Telegram chat.

    • Read your context and instructions
    • Compiled the claude-ops control

    Before I install anything

    I checked GUIDE.md "Supported" against this machine: Linux with systemd user services, Claude Code logged in with a claude.ai subscription, the official Telegram plugin and Python 3. All present.

    This is what will be installed and where

    WhereWhat
    ~/.local/binclaude-sessions, claude-service-template, claude-watchdog, claude-telegram-healthcheck, claude-control-bot and helpers (links into this package)
    ~/.claude/hooksprogress.md re-injection after restart or compaction, Telegram reply hooks, the irreversible-command guard
    ~/.config/systemd/userrestart and alive timers, the control bot service
    ~/.claude/claude-opsthe status line script (you add one statusLine line to settings.json; I'll show it)

    None of these names exist on your machine yet, so nothing will be replaced. Shall I run install.sh? (yes/no)

    After you said yes

    1. Ran bash install.sh.
    2. Showed you the settings.json hook changes as a preview and applied them only after you agreed (the old file is backed up).
    3. Made one service per project with claude-service-template and started them.
    4. Control bot: you created one more bot with BotFather and put its token and your Telegram user id in ~/.claude/control-bot/.env yourself. It answers only that user id.
    5. Pairing each session bot needs your phone: message the bot, approve the code in that session's terminal.
    6. Ran each test file under layers/*/tests/ one by one and showed you the output.

    Next steps

    • Open the control bot: it lists every session with its state, and a button restarts one.
    • Screen mode is switched from the same bot; sessions can't switch it themselves.
    I checked GUIDE.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Everything in claude-ops Core, plus a control bot: one Telegram chat that shows all your Claude Code sessions on one screen with buttons to restart one, and switches the screen mode from your phone. Also a status line for Claude Code. This is the setup I have used daily for five months with about ten sessions.

    What it installs

    • Everything in Core: one systemd user service and one Telegram bot per project, restart and alive timers, Telegram link check, orphan cleanup, progress.md re-injection after restart and compaction, reply hooks, a guard for common irreversible commands, a screen mode, voice messages through whisper on your machine (optional), claude-sessions commands
    • A control bot (its own bot token, answers only your Telegram user id): list sessions and their state, restart a stuck one, switch the screen mode between the virtual display and your real screen
    • A status line for Claude Code

    How the agent installs it

    The agent checks your machine against the requirements, shows what will go where and waits for your yes, checks for files it would replace, runs the installer, shows the settings.json change as a preview before applying it, and walks you through pairing the bots on your phone. Then it runs the included tests.

    Requirements

    Linux with systemd user services (tested on Ubuntu 24.04), Claude Code with a claude.ai subscription, the official Telegram plugin, Python 3.8+, one extra Telegram bot for the control bot.

    Also on Agensi: claude-ops Guide (manual steps only), claude-ops Core (without the control bot) and claude-ops Unattended (adds overnight work and long jobs).

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    Linux only. Requires systemd user services and a Telegram account. Manual pairing via phone is required during setup.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 day ago

    Linux only

    Accounts
    Telegram account (for the bots)
    Software
    GitPython 3.8+Claude Code

    Permissions

    Terminal / Shell
    Read Files
    Network Access
    Write Files
    Environment Variables

    Allowed Hosts

    api.telegram.org

    Shell and file writes: the installer links scripts into ~/.local/bin and ~/.claude/hooks and adds systemd user timers and the control bot service. Network: the Telegram bot API. Environment variables: per-project Telegram state folder. settings.json is changed only after you approve a preview.

    Listed1 day ago

    What's inside

    Frequently Asked Questions

    This skill creates a persistent systemd service layer that maintains your Claude Code sessions 24/7, even after you log out of your terminal, while providing a Telegram bot for remote status checks and restarts.

    The package is specifically optimized for Linux environments utilizing systemd; it is not compatible with Windows (without WSL2) or macOS at this time.

    Before a fresh start, the included handoff skill writes handoff.md with the current state, what failed and the next steps, and the restart refuses to run without a fresh one. The new session reads it first. It helps the new session pick up the work; it does not guarantee nothing is lost.

    The installer, the session scripts, hooks and systemd timers, the control bot and its service, a status line, the guide and tests. The Telegram plugin itself is not included: you install the official one from Claude Code's plugin marketplace.

    From one Telegram chat that answers only your user id: status of every session, start, stop, restart or hard restart one or all, a fresh start (rotate), recent log lines, machine resources, and the screen mode switch. Destructive actions ask for confirmation.

    settings.json is not changed by the installer: the hook merge shows you a diff and applies it only after you agree, backing up the old file. Files with the same names in ~/.local/bin, ~/.claude/hooks and ~/.config/systemd/user are replaced by links, so the agent lists any it finds and asks first.

    New in DevOps & Cloud