Agents
3 posts
I Gave an AI My Whole Life for a Month. Hark Gets a 10/10.
Rating: 10/10 Not an ad: nobody paid me, sponsored this, or asked me to write it. Full disclosure: I signed up early as an interested user, and Hark gave me their $100-a-month plan free for a month. That's how I got to push it this hard. Everything below is my honest take. I've used every AI chatbot you can name. You type a question, you get a nicely formatted paragraph, you copy it somewhere, and then you do the actual work yourself. Hark is the first one that broke that loop for me, and after a month I'm convinced it's what the next generation of AI looks like. The short version: it doesn't just answer. It does. It actually uses a computer Hark runs real browsers on its own machines. It signs in to sites, fills in forms, clicks through dashboards, and comes back with the result. Things I used to put off for weeks because they meant forty tabs and three logins just quietly get done while I'm at work. When something needs me (a code, an approval, a yes or no), it asks, and only then. It remembers me There's no "new chat" button, and that turns out to be the whole point. It's one long conversation with something that keeps track of my preferences, my projects, my routines and the things I said I'd do. I never re-explain context. It knows what I'm working toward and quietly gets the details right. It lives in my accounts, carefully With my mail, calendar, code and notes connected, it can triage an inbox, reshape a week, review a pull request, or file research straight into my notes. And it asks before anything that matters: spending money, sending something in my name, or anything public. I've never had it go rogue on me. It works in parallel This is the absurd part. Ask it for a big piece of research and it spins up several browsers at once, each chasing a different angle, then hands back one clean comparison. Deep market research, legal precedent digs, competitor teardowns, product audits: work that would eat my weekend comes back in the time it takes to make dinner. It builds things It writes and ships code, builds web pages, makes documents, slides and study guides, and has even put live panels on my home screen that keep themselves updated. I've had it test software by playing through thousands of rounds and report back what broke. It's proactive without being annoying Morning rundowns, reminders that land at the right time, watches on things I care about, and the occasional nudge about something I forgot. It feels less like an app and more like a sharp friend who has my back. The ADHD angle I have ADHD, and the hardest part of my day is never the work itself. It's starting, switching and remembering. Hark takes the switching and remembering off my plate. That alone has changed how much I get done. Anything I'd change? Honestly, not much. It's early, sometimes a website fights back, and big jobs take a few minutes. But it tells you straight when something's blocked, and it tries another way before giving up. Verdict Chatbots gave us answers. Hark gives you time back. This is the next generation of AI use: not a smarter search box, but something that actually takes things off your plate. 10/10, and again, this isn't sponsored. I'm just not going back. Try it at hark.com.
My Own AI Assistant on Telegram: OpenClaw + Ollama on Omarchy
I message a Telegram bot from my phone, and an agent running on my Omarchy laptop answers, using a model served locally by Ollama. No cloud model, no open ports, and the agent can use tools on the machine I gave it. The piece in the middle is OpenClaw, an open-source assistant that connects chat apps to AI agents through a local gateway. Here's the exact setup, with real terminal output from each step. What you need - Ollama running with a model that supports tool calling (ollama show <model lists tools under capabilities). - Node 24.16+ (OpenClaw won't install on Node 22). On Omarchy: mise use -g node@24. - A Telegram account. 1. Install OpenClaw bash npm install -g openclaw@latest --allow-scripts=openclaw openclaw --version There's also a one-line installer (curl -fsSL https://openclaw.ai/install.sh | bash) and, if Ollama is already set up, ollama launch openclaw does the install, model pick and onboarding in one go. 2. Onboard it with Ollama as the model bash openclaw onboard --install-daemon The wizard asks for a model provider (choose Ollama), detects your local models, writes ~/.openclaw/openclaw.json, and installs the gateway as a systemd user service so it starts on login. The scriptable version of the same thing: The relevant part of the config it writes: json { "agents": { "defaults": { "model": { "primary": "ollama/qwen3:0.6b" } } }, "models": { "providers": { "ollama": { "baseUrl": "http://127.0.0.1:11434", "api": "ollama" } } }, "gateway": { "mode": "local", "port": 18789, "bind": "loopback" } } Keep bind on loopback. The gateway can run tools on your machine, so only local clients should reach it. 3. Check the gateway is up bash openclaw gateway status openclaw status 4. Create the Telegram bot 1. In Telegram, open a chat with @BotFather (check the handle exactly). 2. Send /newbot, pick a display name and a username ending in bot. 3. Copy the token it gives you. Treat it like a password. 5. Connect the bot to OpenClaw bash openclaw channels add --channel telegram --token <your-bot-token openclaw channels status --probe Or put it in ~/.openclaw/openclaw.json yourself: json { "channels": { "telegram": { "enabled": true, "botToken": "123456:ABC...", "dmPolicy": "pairing", "groups": { "": { "requireMention": true } } } } } The running gateway hot-reloads the change. dmPolicy: "pairing" is the important line: strangers who find your bot can't talk to your agent until you approve them. 6. Pair your own account Send your bot any message from your phone. That creates a pairing request. Approve it on the laptop: bash openclaw pairing list telegram openclaw pairing approve telegram <CODE Codes expire after an hour. Once approved, every message you send the bot goes to the agent, and its reply comes back in the chat. 7. Make the local model good enough This is where most local setups fall over: - Context window. OpenClaw's system prompt, tools and memory need room. Ollama's docs recommend at least 64k tokens for local models. Set OLLAMACONTEXTLENGTH=65536 on the Ollama service (how). - But context costs RAM. On an 8 GB test box, a 32k context got the model killed mid-load, and the agent just reported provider internal error, HTTP 500. If you see that, check journalctl -u ollama for a killed runner and lower the context or use a smaller model. - Model size. Tiny models can call tools but make poor decisions. Use the biggest tool-capable model your GPU runs comfortably, and keep a small one for quick tests. - Keep it warm. OLLAMAKEEPALIVE=30m stops the first message after a break from waiting for a model load. 8. Day-to-day commands | Command | Use | | --- | --- | | openclaw status | Health, sessions, channels at a glance | | openclaw logs --follow | Watch messages and tool calls live | | openclaw models list | Which model the agent uses | | openclaw doctor | Find and fix config problems | | openclaw gateway stop | Stop the gateway | | openclaw security audit | Check what the agent is allowed to do | Guardrails I'd keep - Pairing on, and only your Telegram user ID allowed. - Gateway on loopback, no port forwarding. - Run openclaw security audit after changing tools or skills, and keep risky tools behind approvals. - Keep the bot token and gateway token out of screenshots and git. None of the ones here show either. The agent loop running behind all this is the one from my AI agents guide, just with a phone on the other end.
AI Agents Without the Hype: Tools, Loops and Guardrails
An agent is an LLM running in a loop that can call tools. Instead of answering in one shot, it decides on an action, sees the result, and decides again until the task is done or it gives up. That's all it is. The engineering is in the tools, the loop's limits and what happens when it goes wrong. The loop python messages = [systemprompt, usertask] for step in range(MAXSTEPS): always cap it reply = llm(messages, tools=TOOLS) if reply.toolcall is None: return reply.text done result = runtool(reply.toolcall) validated, sandboxed messages += [reply, toolresult(result)] raise RuntimeError("step limit reached") Model providers support tool calling (also called function calling): you describe each tool with a name, a description and a JSON schema, and the model returns a structured call instead of prose. Design tools like an API for a junior engineer - Few, clear tools beat many vague ones. getpolicy(policyid) is better than runsql(query). - Write the description for the model. Say when to use the tool, what it returns and what it can't do. - Return compact, useful results. Twenty relevant rows, not a 10,000-row dump that fills the context window. - Return errors as text the model can act on: "policyid must look like POL-123456", not a stack trace. Start with a workflow, not an agent If the steps are known in advance (extract, then validate, then load), write them as a fixed pipeline with an LLM call in one or two steps. It's cheaper, faster and easier to test. Reach for a free-running agent only when the path genuinely depends on what it finds along the way. Guardrails that matter 1. Step and cost limits on every run. 2. Least privilege. Read-only tools by default; separate, narrow tools for writes. 3. A human approves anything irreversible: sending an email, paying, deleting, deploying. 4. Treat tool output as untrusted data. A web page or document can contain text that tries to give the agent instructions (prompt injection). Never let retrieved content grant new permissions. 5. Validate tool arguments against the schema before running anything. Make it observable Log every step: the prompt, the tool call, its arguments, the result, tokens used and time taken. When an agent fails, the trace is the only way to tell whether the model chose the wrong tool, the tool returned something confusing or the task was underspecified. Evaluate on tasks, not vibes Keep a set of realistic tasks with a known correct outcome and run the agent against them after every change to the prompt, tools or model. Track success rate, steps and cost per task. An agent that's 5% more accurate but three times as expensive may not be an improvement. Try it: a tool-calling agent in 25 lines This runs the loop above against a local model through Ollama's tool calling. One tool, an allowlist of paths, and a four-step budget: bash curl -O https://www.yashank.site/files/demos/ollamaclient.py curl -O https://www.yashank.site/files/demos/agentdemo.py python agentdemo.py Try asking it about /etc and watch the allowlist return an error the model has to deal with. That's the guardrail doing its job. For a full agent with memory, skills and a chat front end, see how I run OpenClaw over Telegram.