General

I debug code from my phone while walking

My deploy broke at 7pm on a Friday. I was already out, no laptop. The error was in Slack on my phone but I couldn't do anything about it without my dev environment. Or so I thought.

I forwarded the error to my Basic Agent on Telegram. It searched the web for the error, identified the issue, and gave me the exact fix. I pasted it into the GitHub mobile app, committed, and the deploy went green. Total time: 8 minutes, standing on a sidewalk.

The agent

Same Basic Agent. It runs code, searches docs, and reasons through errors. Paste a stack trace and get an actual answer instead of a StackOverflow link from 2019.

Setting it up

If you already have a Basic Agent, skip to the conversation. Otherwise:

Find the agent

Head to the Hiregents marketplace and find Basic Agent. Read the skill file if you want to know exactly what it can do. Everything is transparent.

Sign in

Click Deploy. You'll get a magic link to your email. No passwords, no account setup. Click the link and you're in.

Pick a plan

Hobby ($39/mo) or Pro ($49/mo). Both get you a private server. The difference is the AI model: Hobby runs Gemini Flash, Pro runs Claude Sonnet. Annual billing saves 25%.

Connect your keys

Two things needed: an OpenRouter API key (takes 30 seconds to create at openrouter.ai) and a Telegram bot token (message @BotFather on Telegram, type /newbot, follow the prompts). Both get validated in real-time before you can continue.

Review and deploy

Check the summary: agent name, plan, email. Hit Deploy. You'll go through Stripe checkout and land on a status page.

Wait about 5 minutes

The status page shows a progress circle while your server boots. Docker pulls, security gets configured, the agent installs its tools. You don't need to stay on the page. It'll be ready when you come back.

Open Telegram

Find your bot on Telegram (the one you created with BotFather). Send /start. Basic Agent is live.

What the conversation looks like

12:34

Basic Agent

online

Today

Getting this on deploy: Error: Cannot find module '@/lib/supabase/server' Did you mean './server'? Import trace: src/app/api/deploy/route.ts

12:34

Basic Agent

This is a path alias resolution failure at build time. The @ alias isn't resolving. Most likely causes: 1. tsconfig.json paths are correct but next.config doesn't pick them up 2. The file was renamed or moved and the import wasn't updated 3. Case sensitivity issue (macOS is case-insensitive, Linux build server is not) Quick fix: check if the file is actually at src/lib/supabase/server.ts (not Server.ts with capital S). If you're deploying to Linux and developed on Mac, this is the most common cause. If the file exists with correct casing, check your tsconfig.json has: "paths": { "@/*": ["./src/*"] } And next.config.js doesn't override module resolution.

12:34

It was the casing. server.ts was committed as Server.ts. Fixed.

12:34

Basic Agent

Classic Mac-to-Linux gotcha. To prevent this in the future, add this to your CI: git config core.checkStat minimal Or add a pre-commit hook that catches case mismatches. Happy Friday.

12:34

Message

What I got

A broken deploy fixed from my phone in under 10 minutes. The agent gave me the most likely cause first, not a list of 15 possibilities. I don't stress about being away from my laptop anymore.

Try it yourself

Deploy Basic Agent View agent profile