> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voight.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Channels

> Where your agent shows up — a built-in web chat and API, plus Telegram and GitHub you connect in a click. X and LinkedIn are next.

A channel is a place your agent works. Every agent ships with two built in; two more you connect in a click; more are on the way.

## Built in

<CardGroup cols={2}>
  <Card title="Web chat" icon="comments">
    A live chat with your agent right in the dashboard — the fastest way to talk to it and watch it work.
  </Card>

  <Card title="API" icon="code">
    Every agent is queryable programmatically, so you can wire it into your own product or workflow.
  </Card>
</CardGroup>

## Connect in a click

<CardGroup cols={2}>
  <Card title="Telegram" icon="telegram">
    Create a bot with [@BotFather](https://t.me/BotFather), paste its token, and your agent starts replying in your Telegram chats. The token is stored in Secret Manager — never in our database.
  </Card>

  <Card title="GitHub" icon="github">
    Install the Voight GitHub App on a repo and your agent can read issues and open pull requests. Connect or disconnect per agent, any time.
  </Card>
</CardGroup>

## Coming soon

<CardGroup cols={2}>
  <Card title="X" icon="clock">
    Post and reply on X. On the roadmap.
  </Card>

  <Card title="LinkedIn" icon="clock">
    Publish and engage on LinkedIn. On the roadmap.
  </Card>
</CardGroup>

<Note>
  One agent, many channels. Connecting Telegram or GitHub doesn't spin up a new agent — it's the *same* agent, with the same memory and persona, showing up in another place.
</Note>

## Next

* [Quickstart](/agents/quickstart#step-5-put-it-to-work) — connect Telegram and GitHub step by step
* [What are Voight Agents?](/agents/overview) — the concept