Docs

Getting started

1. Download and install the desktop app from the download page. Windows and Linux are supported today.
2. Sign in. The app opens your browser at this site, you approve the request, and you're signed in automatically — nothing to copy or paste.
3. Open a folder. Point it at any repository on your machine. The agent is confined to that folder for the whole session — it cannot read or write anything outside it.
4. Describe the outcome, not the steps. "Add rate limiting to the login route" works better than a list of instructions — it plans its own steps, and re-plans when something doesn't go as expected.

How the agent works

Most coding assistants generate a suggestion and hand it back to you. This one keeps a loop running: plan, edit, run, check the result, fix what's wrong, repeat — until the thing you asked for is actually built and verified, not just described.

The completion gate

Before a turn is allowed to end, a check runs over what actually happened: is anything on the todo list still open? Were files edited without ever being run or tested? Does the reply defer work back to you ("next, you should…") instead of doing it? Any of those push the agent to keep going instead of stopping. This is the main thing that separates it from a chat-only assistant — it isn't allowed to call something done that it hasn't verified.

Real tools, not a sandboxed toy

It reads and edits files directly, greps and globs your actual repo, and runs commands in a persistent shell — the same primitives a human engineer uses, with the same working directory and environment carrying over between commands.

Skills

Skills are reusable playbooks the agent can pull into context for a specific kind of task — the same idea behind this tool's own skill system. Instead of improvising an approach every time, it loads a written-out, better approach for tasks that match one.

The desktop app ships with a few built in:

• code-review — reviews a diff for correctness bugs and unnecessary complexity before calling a change done.
• debug-build-error — a systematic process for tracking down a failing build or test instead of guessing at fixes.
• add-auth — a session-based email/password auth implementation, end to end.
• deploy-checklist — pre-deploy checks: env vars actually set on the host, database migrations, persistent-storage traps on serverless platforms.

Writing your own

Any project can add its own by creating .htvag/skills/<name>/SKILL.md inside the repo — a short frontmatter header with a name and one-line description, followed by the instructions in the body:

---
name: my-skill
description: When the agent should reach for this.
---

The actual instructions go here — as specific and concrete
as you'd write for a colleague joining the project.

A project's own skill overrides a built-in one of the same name, so you can also use this to sharpen a default for how your codebase specifically wants something done.

Daily credits

Every signed-in account gets 1 credit to start, reset at 00:00 UTC — nothing to configure, no key to find. Credits only count genuinely new work per turn: the parts of a session that repeat (system instructions, tool definitions, earlier turns) are served from cache and don't eat into your balance the way resending the whole conversation would.

Beyond that, credits accumulate while you work. Ad slots sit beside the workspace and refresh as you go; each one that loads pays back half of what it actually earned, converted to tokens — up to 15 a day. The grant follows real ad rates rather than a number we picked, so there is nothing to claim and nothing to watch on purpose.

Creator program

If you have an Instagram following, you can link your account from the desktop app and get a referral link. Anyone who signs up through it and watches reward videos earns you 30% of that ad revenue, calculated monthly and paid by direct UPI transfer. Set it up from the creator page — no minimum follower count.

Troubleshooting

Windows warns the installer is untrusted

"Windows protected your PC" is Microsoft SmartScreen flagging any app it hasn't seen many downloads of yet — it isn't specific to this app. Click More info, then Run anyway.

Sign-in doesn't come back to the app

Make sure the browser window that opened actually finished the approval step — if it's stuck on a blank tab, close it and click Sign in again from the app.

"Daily limit reached"

Leave the app open — the ad slots keep earning credits as they refresh — or wait for the reset at 00:00 UTC.

Something else? Get in touch.