AgentSky
Log in

Docker Agent + Telegram

Telegram is the conversation entry point; Docker Agent is the agent that runs the work. Test Docker Agent with DeepSeek V4 Pro below, then connect Telegram and choose this agent in channel settings.

Repo

Review option pricing before running.

Runs started with multiple options stay blind until you vote.

A task starts here in your browser. To receive messages through Telegram, choose the agent, then connect the channel in its Channels panel. Channel setup opens separately; it does not automatically bind this new task.

How the combination works

Docker Agent does the work. Telegram carries the conversation.

Runs the task through its ACP harness in a persistent cloud workspace while the selected AgentSky model supplies reasoning and generation.

Connect Telegram from the selected agent’s settings. Open the returned bot link and start the conversation; choose which agent answers in the dashboard.

  • Docker Agent

    Owns the work loop, model calls, files, cloud computer, enabled tools, and the result returned to the conversation.

  • Telegram

    Lets people reach the selected AgentSky agent from Telegram. It does not grant access to repositories or other applications mentioned in a message.

  • AgentSky

    Owns the selected responder, channel binding, task state, model and runtime usage, and the separate permissions for tools and connectors.

Setup and first task

Connect Docker Agent to the Telegram conversation you intend to use.

The Composer tests the exact agent in the browser. Channel setup remains a separate account or workspace authorization, so neither step can silently stand in for the other.

01

Test Docker Agent in the Composer

The Composer above selects Docker Agent and its current recommended model, DeepSeek V4 Pro. Use a small task with an answer you can inspect before connecting a shared channel.

02

Connect Telegram and choose Docker Agent

Open an agent in the developer console and select Connect Telegram in its channel controls. Follow the setup link into Telegram and press Start when prompted. Keep the account-binding link private.

03

Verify the real channel path

Ask the agent to turn notes you paste into a prioritized checklist. Confirm the reply in that bot chat before sending more work. Check that the reply arrives in the intended Telegram conversation and that the dashboard still names Docker Agent as the responder.

Access, cost and limits

What Docker Agent + Telegram establishes

Tasks supported by this ACP harness through AgentSky's verified platform-model path.

Configure and verify

  • Docker Agent and DeepSeek V4 Pro are preselected for the browser evaluation.
  • Telegram is connected or paired to the intended account, workspace, server, device or conversation.
  • The first real message reaches the selected agent and returns a useful reply through the same channel.

Do not assume

  • A browser task does not automatically bind Telegram; finish the channel setup separately.
  • Telegram membership does not authorize repositories, email, documents or other application data.
  • Model tokens and active computer time are billed separately from any channel or provider plan.

Common questions

Related resources

Docker Agent

Review Docker Agent's supported models, capabilities and browser Composer.

Telegram channel

Review the channel-specific authorization, pairing and troubleshooting guide.

Docker Agent + DeepSeek V4 Pro

Review the current default agent and model combination.

Pricing

Review model, active-computer, tool and connector charges.

Test Docker Agent, then connect Telegram.

Open the Composer