Dovilo

Turn your to-do list into a city. Focus. Build. Grow.
Delegate your AI tasks to your AI on your desktop.

[Dovilo @DoviloApp]

Turn your to-do list into a city you build.

Finish a task or a focus session, earn bricks. Spend them on houses, parks and roads. Nothing decays; a quiet week costs you nothing.

Free on iOS and Android. No ads. Works offline.

iOS: https://t.co/TqtQIXSTLc
Android: https://t.co/2ASre8CZ1m

https://t.co/Qjs79TIAJy

[Dovilo @DoviloApp]

Dovilo charges $2.49/month.

For that you get the desktop app, a local MCP server your coding agents work out of, signed webhooks, cloud sync, and advanced stats.

AI task top-ups start at $0.99 and never expire.

There's a 7-day free trial.

https://t.co/EMLwBJnDrn

[Dovilo @DoviloApp]

Free on iOS and Android. AI Tasks are in Pro ($2.49/mo, 7-day trial), on a monthly quota. 9 tools, no create/delete, your personal list is never exposed.

iOS: https://t.co/VTKnljGiP4

Android: https://t.co/aymV3qhiuE

Setup: https://t.co/tb4AF6zjak

[Dovilo @DoviloApp]

Before Dovilo, tasks I gave to my coding agent just vanished. Done? Stuck? No idea.

Now it works from its own task list over a local MCP server. Steps, notes and token cost land on my phone. If it needs a decision, it stops and asks.

#ClaudeCode #MCP

[Dovilo @DoviloApp]

How it works:

- Dovilo Desktop ships a local MCP server. Claude Code, Cursor, Claude Desktop, Windsurf, Codex CLI, Gemini CLI.
- 9 tools, read and update only. No create, no delete.
- The agent sees the AI tasks of one project. My personal to-do list is not on the tool surface at all.
- Local process over stdio. No Dovilo endpoint, no MCP traffic leaving the machine.
- Needs an agent decision? It sets awaiting-user and stops.

Part of Pro: $2.49/mo, $19.99/yr, $49.99 lifetime, 7-day trial. Runs on a monthly quota.

Windows: https://t.co/3nWq7krfZg
macOS: https://t.co/TZ231vDvkE

[Dovilo @DoviloApp]

People think coding agents are only for writing code.

Mine works out of a task list. I queue jobs in Dovilo's AI Tasks at night, Claude Code picks them up, marks each step, leaves notes and logs tokens and cost. I read the trail on my phone in the morning.

https://t.co/MS3Pi9cS4n

[Dovilo @DoviloApp]

Webhooks fire the moment a task changes status. HMAC-SHA256 signed. X-Dovilo-Delivery header for idempotency. Up to 5 retries over ~1 hour if your endpoint is down.

Wire it to Slack, Linear, n8n or whatever your stack already uses. The agent works; your tools stay in the loop.

1-week free trial. https://t.co/MS3Pi9dpTV

[Dovilo @DoviloApp]

Local MCP server, running on your machine.

The agent reads your task list, updates step statuses, appends notes and telemetry, and can't create or delete a thing.

Your personal to-do list? Completely invisible to it.

That separation wasn't accidental. It took a while to get right.

1-week free trial. Download now! https://t.co/Qjs79TIAJy

[Dovilo @DoviloApp]

Pomodoro timers are everywhere.

What almost none of them do: let you hear rain, a café, and a fireplace at the same time. Blended to taste.

Dovilo mixes up to 3 sound layers per session across 12 options.

The city builds. The clock runs. The room sounds exactly how you need it.

Download: https://t.co/Qjs79TIAJy

[Dovilo @DoviloApp]

The bricks in your city don't disappear if you skip a day.

No streak to protect. No penalty for a quiet week.

Every task you finish adds to what's already there. A city that only grows, never resets.

[Dovilo @DoviloApp]

The free tier has zero ads and unlimited tasks.

Not a trial. Not "limited free." Just free.

Focus sessions, offline, game, all of it. Pro adds sync, desktop and the MCP server if you run coding agents.

1-week free trial. $2.49/month when you're ready. No pressure until then.

[Dovilo @DoviloApp]

Tasks pay out in bricks. Bricks build the city. The city is the record your to-do list never keeps.

Free on iOS and Android, no ads, works offline.

iOS: https://t.co/qbHUnDJJF7
Android: https://t.co/cLHwIKZdVw

[Dovilo @DoviloApp]

Neither choice is free. Fail closed on silence and you fail steps whose work already landed but the agent shipped the change, the write of "done" is what went missing. In a harness with real side effects, that's a step marked failed on top of work that actually happened, and whatever retries next does it twice.

Failing open has the opposite cost: stale status reads as progress. Both are wrong in a different direction, so the answer isn't which one to pick. It's making the silence legible, and idempotent writes so a retry after the bridge comes back lands once.

For Dovilo the blast radius is small: the tools are read and update only, no create, no delete. The worst case is a step trail missing its last line, not a payment run twice. Pick the failure you can see.

[Dovilo @DoviloApp]

Coding agents don't take breaks.

They run a step, update a status, append a note, then wait for the next task.

Dovilo's MCP tools (update_status, append_note, add_step) run locally over stdio. Nothing routes through a Dovilo server. Your agent talks to its model; that's the only outbound traffic.

$2.49/month. Desktop: Windows & macOS.

https://t.co/MS3Pi9cS4n

[Dovilo @DoviloApp]

Agreed on the principle. The disagreement is about where the stop lives.
An MCP server can't halt a model. The client decides whether a tool error is fatal, so "fail the step" is a harness call, not something the bridge can enforce. And this isn't really an agent-harness problem. It's actually the old problem of networked software: the caller can't tell a slow server from a dead one, and every layer has to decide what to do with silence.
The narrow part is that there's only one way update_status errors here: the local server isn't there. Dovilo Desktop closed, app crashed, bridge died. No network in the path, no Dovilo server to be down, no partial failure mode. So a stall means one thing, and the fix is to make it legible: no step trail moving on the phone, no telemetry landing, no status change. That's the desktop app being down, not the agent thinking hard.
Today the apps just show the last good status, which reads as normal. Surfacing "bridge not connected" on the task is the piece worth building. Will think about it.

[Dovilo @DoviloApp]

Fails open today. The bridge is a tool server, not the harness: a failed update_status comes back as a tool error telling the agent to retry, and if retries keep failing the status stays where it was last written while the model carries on. The only stop primitive on the surface is awaiting-user, and the agent has to choose it; the user's kill switch is MCP off in Desktop, which drops the connection. The phone/desktop apps show the old status; nothing flags the stall yet.

One fix on the bridge side: refuse every other write on a task still in queued, so a transition that never landed fails every later call instead of logging against stale state. Would you fail it harder than that?

[Dovilo @DoviloApp]

Habitica, Forest, Finch: each one rewards either tasks or time.

Dovilo uses both as separate earn triggers.

Finish a task: bricks.
Finish a focus session: bricks.

Two inputs, one city growing on your screen.

[Dovilo @DoviloApp]

Turn your to-do list into a city you build.

Finish a task or a focus session, earn bricks. Spend them on houses, parks and roads. Nothing decays; a quiet week costs you nothing.

Free on iOS and Android. No ads. Works offline.

iOS: https://t.co/TqtQIXSTLc
Android: https://t.co/2ASre8CZ1m

https://t.co/Qjs79TIAJy

[Dovilo @DoviloApp]

@wtf_nakul7 Take control of your schedule and make time to eat away from your desk.

Try https://t.co/EMLwBJnDrn

[Dovilo @DoviloApp]

@astrohound Looks great!

If you ever need a hand with the planning side, we've got you covered 👍

https://t.co/EMLwBJnDrn

[Dovilo @DoviloApp]

@xoaanya If you need a proper to-do list while doing it, we are here to help 💪 We also offer a dedicated to-do list for your AI.

In case you need it:

https://t.co/EMLwBJnDrn