olosegres

Charness — Development skill for Claude Code

Development community

OpenCode and Claude Code coding agents in Telegram: run on your own machine or VPS, drive by voice or text from your phone.

How to install Charness

This entry records only its repository, not the path inside it, so there is no exact command to give. Open olosegres/charness and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Charness does

OpenCode and Claude Code coding agents in Telegram: run on your own machine or VPS, drive by voice or text from your phone. One topic per project, like terminal tabs. Self-hosted, no open ports.

Alternatives in Development

  • Nexting — Remote control for Claude Code, Codex, Grok, and Cursor on Mac or PC 1.3k ★
  • Pairfob — Your Herdr agents on your phone in one QR scan 165 ★
  • Handmux — A mobile vibe-coding cockpit — built on tmux: drive your live session, Claude Code / Codex — anything a termin 162 ★

README

Charness

formerly TelegramCode

Telegram bot/group as a terminal for OpenCode, Claude Code — every thread like a terminal tab + scheduling, voice control

Charness — all your agents in Telegram; chat, code, ship; powerful slash commands

Charness turns Telegram into a terminal for running agentic CLIs. Open as many tabs as you need — even two on the same project for parallel work — and drive the agents from your phone or tablet, voice messages included.

Think **OpenClaw for vibe coding**, driven entirely from Telegram: no complex setup, no extra dashboards — direct access to your own **OpenCode** / **Claude Code** running on your machine or server.

Features

  • Simple setup & management — install the CLI, put your bot token in one .env, bind a topic to a folder, and run; everything after is managed from Telegram — no dashboards
  • Multi-thread / topic — one topic per directory with your agent; two topics can share one folder for parallel work — run almost unlimited agents in parallel
  • Two chat surfaces — forum-group topics and the owner's bot DM, both served at once by default, with tabs on either
  • Agent backends — OpenCode (native server API over HTTP+SSE) and Claude Code (three backends — json-stream, per-turn and tmux)
  • Sleeping agents — a Claude json-stream topic's process is stopped when idle (or after every turn in per-turn mode) and the next message resumes the same conversation by itself, prompt cache still warm
  • Raw terminal — /terminal binds a topic to a real $SHELL in the project folder
  • Notifications — when the agent asks a question, the bot pins that message so even a muted topic notifies you: the pin pierces mute, giving exactly one notification per question (unpinned once you answer)
  • Scheduled & self-driving runs — /schedule arms cron / one-s