Practical overview
When it fits
Use Flock when a repository team wants a self-hosted chat interface around a structured Claude Code development workflow, with branch, testing, review and pull-request stages.
Who it is for
- Repository teams that want chat-driven feature development
- Developers operating a self-hosted coding-agent workflow
- Teams that review AI-generated changes through branches and pull requests
- Operators building Telegram, VK or LO interfaces for software maintenance
Documented uses
- Describe a feature request in chat
- Plan and implement repository changes on a branch
- Run repository checks and review proposed changes
- Open a pull request for human or team review
- Keep concurrent chat tasks in separate workspaces
Requirements & limits
The repository documents prebuilt Docker images. The Telegram setup requires a bot token, bot username, an allow-list and Claude subscription or Anthropic API authentication. Hosting must be in an Anthropic-supported region for Claude calls.
- The documented coding workflow is built around Claude Code and Anthropic authentication.
- Telegram, VK and LO are the named chat adapters; another messaging integration requires modification.
- Each chat has its own workspace, while the Telegram Secretary Mode documentation states that this separation is not a security boundary for an agent with shell tools.
- The project is self-hosted and distributed under the MIT license.
- The Telegram quick start uses a prebuilt image and does not require a build step.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up Flock with the Telegram adapter
Prepare the documented Docker deployment so an allow-listed Telegram user can message the Flock bot.
Before you start
- A server able to run Docker Compose
- A cloned copy of the Flock repository
- A Telegram bot created through @BotFather
- A Claude Code setup token from a subscription or an Anthropic API key
- Telegram user IDs for the allow-list
Steps
Clone the Flock repository and change to the
flock/adapters/telegramdirectory.Copy
.env.exampleto.env.Fill in
TELEGRAM_BOT_TOKEN,TELEGRAM_BOT_USERNAME,ALLOWED_USERS, and eitherCLAUDE_CODE_OAUTH_TOKENorANTHROPIC_API_KEY.Run the command below to pull the prebuilt Telegram image.
docker compose up -dMessage the configured bot from an allow-listed Telegram account.
Expected outcome
The Telegram adapter is started from a prebuilt Docker image and accepts messages from the configured allow-list.
Guide limitations
- This guide documents setup and message entry, not a verification of a successful repository task.
- Claude calls can fail when the host is outside an Anthropic-supported region.
- The documented Telegram deployment uses the Claude backend for the supplied authentication flow.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 4 October 2026
- Original website title
- duckbugio/flock · Official homepage title · retained in its source language

