PLANS & EXECUTION
Workflows
Saved workflows, execution runs and plans from every Relay channel.
History is available here for inspection. Continue linked workflows and make production output decisions in their original Relay channel. Create and review a new desktop draft below.
REUSABLE OPERATIONS
Automations & tools
Registered operations with detected availability and execution limits.
From repeated work to a reusable tool
Relay does not yet extract automations from project history or schedule recurring jobs. Existing workflows are saved executions; they do not automatically become reusable tools.
For reels, candidate steps include checking source files, applying a known caption format, and validating exports. First review the repeated step, its inputs, outputs and failure cases. A tested script can then become a versioned registered operation for future plans.
This fills a request you can edit. Generate draft uses your planning provider; it does not install tools or start production.
What you can do
Agents & browser execution
Registered operations
LOCAL RECORDS
Usage & storage
Recorded tokens, disk space and reviewed cleanup.
RELAY ON THIS COMPUTER
System
Service, diagnostics, optional tools and updates.
YOUR WORK, CONNECTED
One place to get everything moving.
Task Relay connects a project, your chosen AI provider, and a Telegram inbox. Download it, install it, then finish setup in the local page that opens.
The download contains public Task Relay source. Your local credentials, job history and project files stay on this computer.
Setup.command inside its folder. It finds that folder, installs Relay’s required Python packages, and opens the live setup page. Python 3.11+ must already be installed.INSTALL TASK RELAY
From download to first job
A browser cannot run a shell command from an HTML file. The macOS setup file starts the installer when you open it from Finder.
MACOS · PRIMARY PATH
Install without typing commands
- Use Download source files above, then open the ZIP to extract its folder.
- If Python 3.11+ is missing, install Python for macOS ↗.
- Open the extracted job-relay folder in Finder and double-click
Setup.command. macOS may ask you to confirm opening a downloaded script. - Wait for the local setup page to open. Choose a project, connect a provider and Telegram bot, then follow its start instructions.
Keep the installation folder: it contains Relay’s dedicated Python environment. Reopen setup later by double-clicking Setup.command again.
BEFORE YOU START
What you need
- Python 3.11+ on the computer. The installer cannot run before Python exists.
- A project folder and an API provider key for new provider jobs, or existing Codex jobs.
- A dedicated Telegram bot from BotFather ↗ if you want Telegram delivery.
The installer installs Relay and its required Python packages. Git is only needed to clone, not for the ZIP. Claude, browser automation, Blender and FFmpeg are optional. Linux uses sh install.sh from the extracted folder; Windows execution is not yet supported.
GET STARTED
Set up in a few steps
Only the actions you choose below contact a provider or Telegram. No job or message is sent during setup.
01Choose a projectUse an existing folder on this computer.Waiting
Relay saves this folder for new jobs; choosing it does not grant a worker access.
02Connect a providerUse an API provider, or choose Later for existing Codex jobs.Waiting
Connecting checks the model catalog without generating content.
An already configured provider is retained. Use Telegram /providers or the CLI for deliberate changes.
03Connect TelegramConnect a dedicated bot for replies and pairing.Waiting
Create a dedicated bot with BotFather. Relay checks its identity and webhook status, then gives you a pairing link.
If a bot is already configured, leave the token blank to keep it and renew an expired unpaired link.
04Start and verifyRun Relay, pair in Telegram, then verify a real reply.Manual check
job-relay telegram runChoose a project and provider to get your first-job command, or use /tasks for existing Codex jobs.
After stopping the foreground process, use job-relay telegram install for a supported background service. Sending an instruction authorizes provider work and may incur charges.
LOCAL STATUS
What’s ready
Checking local configuration…
These checks do not contact a provider, test delivery or prove service health.
OPTIONAL TOOLS & UPDATES
On this computer
These tools are for selected workflows. Missing ones do not block the core Relay setup; the source installer does not install external applications.
Checking tools…
Checking contacts GitHub. Installing an update remains a separate explicit CLI action.
YOUR WORK
Jobs
Choose a saved job to see its activity or continue work. Sending an instruction may use a paid provider.
Usage
Usage is read from local records. Storage excludes the installed app and unrelated project folders.
What uses this space? How can I clear it?
Open to inspect local folders.
Workspaces, artifacts, unique backups and the live database may contain job history or recovery evidence. Build output can be regenerated but may be in use. These are excluded from automatic cleanup.
Only listed caches and verified duplicate retired databases are eligible. Changed files are skipped; a receipt is saved.
New job
Leave the folder empty for a new Relay workspace. A working folder sets relative-file context; it does not limit Relay’s computer-wide access. Creating a job does not start provider work.
Plan a workflow
Describe one bounded outcome. Relay will save a draft with steps, outputs, checks and limits for your review. Generating a draft uses your configured planning API provider; workers do not start.
Saved plan
Background service
Checking service…
Jobs
Checking job history…
Choose a job
Saved job details and recent activity appear here.