500nits

Botify

A self-hosted way to work with Codex through Telegram.

How it works

I started Botify in October 2025 to connect Telegram to Codex. The agent runs on your own machine, with access to a project's files, instructions, tools, and working directory.

A deployment can be tied to a particular repository or business environment. Each authorised chat keeps its own conversation, so you can return to the work without starting from scratch.

The runtime separates incoming messages, command routing, conversations, prompt execution, and AI-provider communication. Memory, attachments, transcription, and message delivery have their own components.

Features

  • Telegram private chats and groups.
  • Separate, persistent conversations for each authorised chat.
  • Document, image, audio, and voice-note attachments.
  • Local voice transcription with Whisper.
  • Shared, searchable memory stored in PostgreSQL.
  • Access to the files and repository for a specific project.
  • Diagnostics, authentication checks, model controls, and deployment commands.
  • Automatic startup and recovery on macOS and Debian.
  • Extensible interfaces for transports, services, and AI providers.
  • Starter configurations for project-specific workflows.

Development

  1. Oct 2025

    First version

    A TypeScript bridge that passes Telegram messages to Codex through MCP.

  2. Nov–Dec 2025

    Chats and startup

    Status and lifecycle tools, startup scripts, Telegram groups, attachment saving, authentication checks, a helper server, and richer message formatting.

  3. Jan 2026

    Persistent memory

    PostgreSQL-backed shared memory, persistent conversation IDs for each chat, sender details in prompts, diagnostics, and text-to-speech tools.

  4. Feb–Mar 2026

    Audio and attachments

    Audio and voice-note capture, Whisper transcription, model controls, attachment-path awareness, and shared-memory queries.

  5. Apr 2026

    Separate components

    The Telegram bridge was split into providers, services, command routing, conversations, transcription, memory, and helper-server components.

  6. May–Jun 2026

    Provider support and reliability

    Work on a multi-provider design, compatibility, paths, and startup behaviour.

Next steps

I'm working toward using Botify to run dedicated AI agents around existing software, data, and workflows. Each deployment would keep the project context it needs, with a chat interface for working with it.

To ask about the project, email apps@500nits.com.