You've already forked zblade.dev
docs: add blog post about Telegram remote control and screenshot editor
This commit is contained in:
@@ -0,0 +1,115 @@
|
||||
---
|
||||
title: "New in Zaguán Blade: Telegram Remote Control and the Screenshot Editor"
|
||||
description: "A quick look at two new Zaguán Blade features: controlling Blade from Telegram and capturing, annotating, and sharing screenshots directly from the chat composer."
|
||||
pubDate: 2026-05-28
|
||||
tags: ["telegram", "screenshots", "remote-control", "ai-coding"]
|
||||
categories: ["Product"]
|
||||
draft: false
|
||||
---
|
||||
|
||||
Zaguán Blade keeps getting closer to the way developers actually work: sometimes you are at your desk, deep in a codebase; sometimes you are away from the keyboard but still want to keep an eye on what the assistant is doing; and sometimes the fastest way to explain a problem is not another paragraph of text, but a marked-up screenshot.
|
||||
|
||||
This release adds two brand new features built around those moments:
|
||||
|
||||
- **Telegram Remote Control**: send instructions to Blade from your phone and follow command output remotely.
|
||||
- **Screenshot Editor**: capture, annotate, and attach screenshots directly inside the AI chat flow.
|
||||
|
||||
Neither feature is about adding complexity. They are about reducing friction.
|
||||
|
||||
## Telegram Remote Control
|
||||
|
||||
The new Telegram integration lets you pair Zaguán Blade with your own Telegram bot, then use that bot as a lightweight remote control channel.
|
||||
|
||||
Once connected, you can send messages to Blade from Telegram, and Blade will treat them like chat instructions. That means you can ask it to continue a task, run a command, check a result, or help with a project while you are away from the main window.
|
||||
|
||||
It is especially useful for longer-running work. If Blade is building, testing, installing, or waiting for approval, Telegram gives you a simple way to stay in the loop from your phone.
|
||||
|
||||
## What you can do from Telegram
|
||||
|
||||
The first version focuses on practical remote control:
|
||||
|
||||
- **Send commands or instructions** to Zaguán Blade from Telegram.
|
||||
- **Approve or reject AI command execution** without returning to your desktop immediately.
|
||||
- **View command output and exit codes** as work progresses.
|
||||
- **Keep an eye on long-running tasks** while Blade remains open on your computer.
|
||||
|
||||
This is not meant to replace the desktop interface. The editor is still where the full experience lives. Telegram is the quick remote companion: useful when you want to nudge, approve, or monitor work from somewhere else.
|
||||
|
||||
## How to connect Telegram
|
||||
|
||||
Telegram setup uses your own bot token. That keeps the connection under your control, rather than routing through a shared public bot.
|
||||
|
||||
To connect it:
|
||||
|
||||
1. Open **Settings** in Zaguán Blade.
|
||||
2. Go to the **Remote** section.
|
||||
3. In Telegram, open a chat with [@BotFather](https://t.me/BotFather).
|
||||
4. Send `/newbot` and follow BotFather's prompts.
|
||||
5. Copy the HTTP API token BotFather gives you.
|
||||
6. Paste the token into Blade's **Bot Token** field.
|
||||
7. Click **Connect**.
|
||||
8. Open the generated Telegram bot link or scan the QR code shown in Blade.
|
||||
9. Send `/start` to the bot to pair your Telegram chat with Blade.
|
||||
|
||||
After that, the bot is ready to receive commands.
|
||||
|
||||
A few important notes:
|
||||
|
||||
- **Blade must be running** on your computer for remote control to work.
|
||||
- **The bot pairs with your private chat** so another Telegram user cannot casually take over the same bot connection.
|
||||
- **You can disconnect** from the same Remote settings panel when you no longer want Telegram control enabled.
|
||||
|
||||
## Screenshot Editor
|
||||
|
||||
The second new feature is a built-in Screenshot Editor for the AI chat composer.
|
||||
|
||||
When you capture or attach a screenshot, you can now edit it before sending it to the assistant. This is designed for the kinds of visual context that come up constantly while building software: a broken layout, a confusing UI state, a terminal error, a tiny detail in a modal, or a specific region of the app you want the model to look at.
|
||||
|
||||
Instead of writing "look at the button in the top right, not the other one," you can draw an arrow and send the image.
|
||||
|
||||
## What the Screenshot Editor can do
|
||||
|
||||
The editor includes the everyday annotation tools you need for fast communication:
|
||||
|
||||
- **Arrows** for pointing at the exact part of the image that matters.
|
||||
- **Text labels** for short notes and callouts.
|
||||
- **Boxes and filled boxes** for highlighting UI regions.
|
||||
- **Circles and ellipses** for marking details without covering them completely.
|
||||
- **Freehand pencil drawing** for quick sketches or underlines.
|
||||
- **Color selection** for making annotations stand out.
|
||||
- **Stroke and text size controls** for adjusting emphasis.
|
||||
- **Undo, redo, and clear** for quick correction.
|
||||
|
||||
It also supports editing after you place something:
|
||||
|
||||
- **Select annotations** and move them around.
|
||||
- **Resize arrows, shapes, pen strokes, and text** using handles.
|
||||
- **Recolor selected annotations** without redrawing them.
|
||||
- **Edit text annotations in place** if a label needs changing.
|
||||
- **Delete selected items** with the toolbar or keyboard.
|
||||
|
||||
Once you are done, you can attach the edited image to the chat. The assistant receives the screenshot with your annotations included, so the visual context is clear immediately.
|
||||
|
||||
## Why this matters for AI coding
|
||||
|
||||
AI coding conversations are often limited by context. Text is great for describing intent, but many development problems are visual:
|
||||
|
||||
- A component is misaligned.
|
||||
- A button is too subtle.
|
||||
- A terminal panel is showing an unexpected state.
|
||||
- A chart, PDF, image, or markdown preview looks wrong.
|
||||
- A specific region of the app needs attention.
|
||||
|
||||
The Screenshot Editor makes those moments faster. You can show the problem, mark the important part, and send it to the assistant in one flow.
|
||||
|
||||
Combined with Telegram, this also makes Blade more flexible. You can explain problems visually when you are at the desktop, then keep monitoring or approving work from your phone when you step away.
|
||||
|
||||
## Small features, big workflow improvement
|
||||
|
||||
Telegram Remote Control and the Screenshot Editor are different features, but they share the same goal: keep the development loop moving.
|
||||
|
||||
Telegram helps when you are away from the keyboard.
|
||||
|
||||
The Screenshot Editor helps when text is not enough.
|
||||
|
||||
Together, they make Zaguán Blade feel less like a static editor window and more like an AI coding workspace that follows the shape of real work: visual, asynchronous, and occasionally mobile.
|
||||
Reference in New Issue
Block a user