Get started with Farstax: Claude Code from Telegram

Farstax gives your coding agent a workspace that stays available when you close your laptop. Telegram is where you direct the work; your repository and tools live in the workspace. The first setup is straightforward once you follow the order the product actually uses: create a workspace, connect Telegram while it comes online, then sign in to Claude Code.

This walkthrough uses managed Farstax. If you would rather operate Agent Bridge on your own machine, there is a separate route at the end.

1. Get beta access and sign in

Farstax is an access-controlled beta. Start at farstax.com and choose Apply for beta. If you are offered access, sign in with GitHub and open farstax.com/app. Applying does not itself create a workspace or grant beta access.

GitHub sign-in establishes your identity and lets Farstax request repository access through the authorised GitHub App. Review the permissions you grant. You will tell your agent which repository to work in later; you do not need to choose a default repository as a separate onboarding step.

2. Create your workspace

From the signed-in Farstax page, select Create workspace. The available hosting plan is Starter; Standard and Growth are marked as coming soon. Farstax starts provisioning the workspace and installing Agent Bridge.

You do not need to set up a VPS or open an SSH session. And you do not have to sit on the provisioning screen: the next part can be done while the workspace is coming online.

Farstax looks after the workspace infrastructure and Agent Bridge appliance lifecycle. The resident agent looks after the code, tools and services you ask it to run inside that workspace.

3. Connect Telegram while the workspace is provisioning

The onboarding screen opens Connect your chat surface. Select Telegram if it is not already selected.

Open BotFather in Telegram, send /newbot, and follow its prompts to give the bot a name and username. BotFather returns a token. Back in Farstax, enter it in BotFather token, enter your own numeric Telegram account ID in Your Telegram user ID, then select Save Telegram setup.

Use the Farstax form, not a chat message, for the token. The Telegram user ID is the allowlist: only authorised accounts should be able to instruct an agent with access to your workspace and GitHub credentials.

If the workspace is still provisioning, Farstax reports that the setup has been saved and will connect automatically when the workspace is live. That means the configuration has been accepted, not that the bot is already running. If provisioning finishes first, you can complete the same chat setup on the now-online workspace page.

4. Check that the workspace and chat are online

When provisioning completes, the workspace shows Online. Confirm that Telegram is connected as well, rather than relying on the earlier “setup saved” message. Use the workspace page to revisit chat setup if it needs attention.

The bot may send a message beginning “Farstax workspace is online.” It contains a link back to the workspace and asks you to connect an AI subscription. That is the expected next step, not a sign that Claude Code is already authenticated.

5. Connect Claude Code

Back in Farstax, open Connect your AI subscriptions. Select Claude Code, then choose Next: Sign in. Sign-in becomes available when the workspace is ready.

Choose Start sign in for Claude Code, then Open sign-in page. Authorise the connection with your own Claude account. If the provider shows an authorisation code and Farstax asks you to paste it back, use the code field in Farstax and submit it there. Otherwise the page checks for completion automatically. Do not paste authentication codes or credentials into Telegram.

Wait for Claude Code to show Connected, then choose Finish. A Telegram bot that is online but has no authenticated coding provider cannot yet carry out a coding task. Farstax manages the workspace; you remain responsible for the subscription and permissions of the coding agent you connect.

6. Give Claude Code its first useful task

Open your connected bot from Farstax and send a message from the Telegram account whose user ID you authorised. You do not need a separate Default working repository → Load repositories → Save repository setup flow. Name an accessible repository directly in the conversation.

For example, replace owner/repo with a repository you can access through your connected GitHub account:

Work in owner/repo. Find the project's documented test command, identify a small existing test that is safe to run, and run it if the environment supports it. Tell me which files you checked, the exact command you used and whether it passed. If you cannot run the test, explain why. Do not edit files, open a PR or deploy anything.

This gives you something to verify without assuming the repository has a failing test or asking a new agent to change code before you know the connection works.

The repository named in the request is a working target, not a new GitHub permission boundary. Agent Bridge can request access to other repositories visible to your authorised GitHub account through the Farstax GitHub App, subject to effective permissions and GitHub rules. The agent should report a permission failure rather than claiming it inspected a repository it could not access.

Compare the response with the repository and any reported test output. A chat reply alone is not proof that a command ran. When you are ready to make a change, the engineering workflow guide takes you from requirements to a reviewed, merge-ready PR.

7. Continue from somewhere else

Use the same Telegram conversation to ask a follow-up or review the result while away from your desk. Your laptop is not hosting the agent. Agent Bridge retains the workstream, but that is not a promise that every interrupted provider process will resume after a host failure.

The Telegram commands guide explains provider switching, stopping and resetting work, and keeping separate projects in Telegram forum topics.

Prefer to self-host?

Agent Bridge OSS runs the underlying workflow without requiring Farstax. You supply the server, authenticated coding-agent CLI, messaging credentials and ongoing infrastructure maintenance.

The Telegram setup guide covers the source-based path, which requires Node.js 24+. That setup wizard is not the production service installer. For a continuously managed host, follow the separate initial production installation and security and hardening guidance.

Self-hosting means taking responsibility for the host and its credentials, upgrades and recovery. In either route, you still decide what your coding agent is authorised to change.