About Dulus
One human. A flock of agents.
Dulus is made in Santo Domingo by one developer directing a flock of AI agents. It is named after a Dominican bird that lives in flocks and builds one nest for the whole colony. The product works that way. So does the company.
- Made in
- Santo Domingo, Dominican Republic
- Named after
- The palmchat, Dulus dominicus
- Backed by
- Ten startup programs
01 · The bird
Named after the bird, not the rocket.
Dulus is the genus of the palmchat — the cigua palmera, national bird of the Dominican Republic. Look closely at how it lives and you will find the product.
The palmchat lives on Hispaniola and nowhere else on Earth. It is the only species in its family; on its branch of the tree of life, there is no other bird.
It is also a builder. A flock weaves twigs into one great nest high in a royal palm, and inside that single structure every pair has a chamber of its own. One roof, many rooms. The colony shares the work; every pair keeps its own door.
We have never read a better description of Dulus, and a bird wrote it. You talk to one agent. Behind it is a flock that shares the nest — your project — while each member keeps a room of its own.
Read the nest as software
-
One nest for the colony
Your project is the nest. Dulus works in it, and so does every sub-agent it sends out: up to three at once, in the background.
-
A chamber for every pair
Each seat at the round table is a full agent with its own model, history and mailbox. A sub-agent can work in its own git worktree.
-
A flock that talks
Seats talk to each other mid-turn while Dulus chairs. It never takes a seat; it is woken when every seat has answered.
-
One bird, from afar
You see one agent. On the desktop, the pet crew shows a small mascot for every sub-agent at work.
One agent. Made of many.
02 · Made in Santo Domingo
Built the way it works.
Dulus is made by Kevin Rojo — KevRojo on GitHub — a solo developer in Santo Domingo, Dominican Republic. One human, directing a flock of AI agents.
The company runs on the same idea as the product. The human sets the direction, makes the calls and approves anything that can’t be undone. The agents do the work and leave proof of it: code, a file, a log, a URL, a commit.
The island shows in the product, too. Dulus answers in Dominican Spanish by default; /lang switches it to any of 34 languages, or to something free-form like “formal British English”. And while it thinks, its spinner says things like “Sharpening talons on the AST…”
- Founder
- Kevin Rojo (KevRojo)
- Based in
- Santo Domingo, Dominican Republic
- Team
- One human and a flock of agents
- The app
- Free, for Windows 10 or later
- Open-source edition
- github.com/KevRojo/Dulus
- Backed by
- Ten startup programs
The org chart
18.5° N · 69.9° W
03 · The doctrine
Remove the friction between a human intention and its complete execution.
That is the mission, from the doctrine: the canonical document every agent, model and bot that works under Dulus must read before it acts. Each of them is meant to ask, every turn: what friction can I remove right now?
Advance the goal. Tell the truth. Leave artifacts. Don’t wait for permission on what’s reversible; ask for what isn’t.
The ten principles
Written for the agents. They hold up for people, too.
-
Truth over hype.
Report what really happened, failures included — hype without truth is a debt someone else pays later.
In Dulus LiveFeed figures arrive with their source URL.
-
Verify before claiming.
“It works” is an empirical claim, not a hope: run it, read the output, and say exactly what you couldn’t verify.
In Dulus
/verifychecks a number against its source. -
Leave artifacts, not promises.
Every turn should leave something you can hold — code, a file, a log, a URL, a commit — because work that leaves no trace didn’t happen.
In Dulus An audit trail of Write, Edit, Bash and ScreenClick.
-
Reversible: act. Irreversible: ask.
Don’t ask permission to breathe, but confirm before you delete data, publish, move money or push to production — and an approval in one context never carries over to another.
In Dulus
automode runs what’s safe and asks before anything that changes things. -
Autonomy with clear limits.
Own your domain and don’t invent scope beyond it; when adjacent work matters, write it down and raise it instead of ignoring it or quietly absorbing it.
In Dulus
/budgetcaps tokens and tool calls per session. -
Collaborate, don’t compete.
Pass context, not egos: if another agent does it better, delegate, and if a teammate is about to break something, say so.
In Dulus Round-table seats talk to each other mid-turn.
-
Fail loud, recover gracefully.
A silent error is the worst kind, so catch it, report it with context, degrade gracefully and never leave the system in a corrupt state.
In Dulus Files are snapshotted before every Write and Edit;
/checkpointrestores them. -
Security and ethics are not negotiable.
No leaking secrets, no shortcuts that put people’s data at risk, no skipping guardrails because it’s faster: the end never justifies breaking trust.
In Dulus A security review is offered before every MCP install.
-
Improve the system, not just the task.
After every fix, ask how to keep it from needing a human again, so each bug leaves the system harder to break than before.
In Dulus
/memory consolidateextracts long-term insights. -
The human is direction, not operator.
Ask the human for decisions, judgment and approvals, not work — every time you hand over something you could have done yourself, you failed a little.
In Dulus Steer mid-turn in the desktop app: type while it works, and it reads you before its next step.
04 · How we build
We’d rather show you.
-
Build in public.
An open-source edition lives on GitHub, and every improvement and every milestone is the content. No campaign required.
-
The product speaks.
No testimonials, no customer logos, no borrowed superlatives. An agent that finishes the job is more persuasive than any ad.
-
Zero spam.
Quality over volume, and the same honesty rule as the code: never promise what doesn’t exist. Trust is the one thing you can’t automate.
05 · Say hello
The nest is open.
Questions, bugs, ideas, or the story of something you built with the flock. Write to us.
