Open source · MIT · PHP 8.4+

Workspace Assistant

A Telegram bot that runs Claude Code in your git repository, records every decision in its history and drives epics of tasks from design to merged pull requests.

Install GitHub

An illustrated team at a long table passing documents along: the path of a task from design to final check
An epic from start to finish: design → issues → pull requests → review → merge → final check.

A knowledge base you edit from your phone

The bot works in a git repository of documents, the managed repository: notes, decisions, plans, task texts. You write to the bot in Telegram; the message goes to claude -p in the context of that repository, the changes are committed and pushed right away, and the reply links to the commit.

Telegram ↔ bot ↔ claude -p ↔ git push

Every decision is recorded the moment it is made, so the history of the repository shows how your decisions evolved. It is meant for documents, not for a code base: code lives in separate repositories, and changes there go through pull requests.

A Telegram forum group with Workspace Assistant: one topic per task, the bot is replying in the i18n topic
Each forum topic is a separate Claude session.

Features

A forum topic: the user asks for a pipeline diagram, the bot replies with a PNG image, its Mermaid source file and an explanation
Files Claude puts into the outbox arrive in the chat: here a diagram and its Mermaid source.

Epics: from an idea to merged pull requests

Besides chatting with a repository, the bot can carry a set of tasks to completion. Claude handles the steps that need judgement, the bot's Orchestrator handles the deterministic ones, an external executor writes the code, and the author keeps the decisions that must stay human.

  1. ArchitectClaude in the pm mode designs the change, runs it through cold critique, verification, editing and a scope check, and opens the issues.
  2. Authorre-reads the tasks and sends /epic start.
  3. Implementeropenronin writes the code and opens pull requests; independent tasks run in parallel.
  4. Reviewan optional cold CI review, then a hot review against the intent of the task and the epic plan.
  5. Mergethe Orchestrator merges, labels and releases, and stops a stuck epic.
  6. Final checkverifies the whole epic and writes the report for the author.

Epics rely on openronin as the external executor. Regular chat with the bot does not need it.

The epic card in a forum topic: eight tasks with their state — merged, in review, CI is running, waiting for other tasks — and the last journal entry
The epic card: each task's state, what it waits for, and the last journal entry.
A pull request timeline on GitHub: the cold CI reviewer leaves a recommendation, openronin answers it and pushes a fix, then the hot review with the epic's context requests changes
Cold review recommendation → openronin's fix → hot review with the epic's context.

13 interface languages

Languages in README →

GitHub and GitLab

GitHub is the default. With FORGE=gitlab the bot works with gitlab.com or, with FORGE_HOST, a self-hosted instance, through the GitLab CLI glab. Minimum versions: GitLab 16.0 and glab 1.40.

FeatureGitHubGitLab
Chat modesupportedsupported
PM modesupportedsupported
Review modesupportedsupportedverdict note with a marker; cold reviewer findings are not collected
Epics (/epic)supportednot supported

Setting up GitLab →

Get started

You need PHP 8.4+, the Claude Code CLI, git with access to the repository's remote, and gh (or glab for GitLab).