The World Get Started

Describe the job.
Meet the bot.

One sentence scaffolds a working agent on your machine, with a scope written into code. Name a world, and its words become the commands you type.

Get StartedSee it workView source
#
Message #

Your words become the commands.

Name a world and the bots take its language. A pack /adopts and /trains. A party /summons and /crafts. Real slash commands, inside your harness.

Characters you love, at work.

Your favorite characters talk in your Slack, hand work to each other, and argue it out in the open, where your team can read along.

Learn the harness by building it.

Every bot you add teaches one piece: a tool, a scope, a hook that holds the line. You end up understanding the system you run.

Name a world.
The bots take its words.

The world is not a skin. It renames every bot, and it renames the two commands you type to grow the team. Try one on.

add a bot give it a tool you get

Only the tools
you hand it.

A bot's abilities are one kind of thing: a scoped tool, bound to one project, one account, or one host when it is built. No borrowed shell, no second path in.

Party-Rangerwatcher
sentry_issues_readread only · one project
Pack-Beaglewatcher
ads_report_readread only · one ad account
Post-Archivistexecutor
records_writeone archive · only after you approve

Every world is
somebody's favorite.

An isekai door. A projector beam. A neon castle, a lone rider, a robot in the rain. Whatever you love, the kit speaks it, and the harness carries those words wherever you clone it.

An isekai door opening onto floating islandsA projector beam with a giant silhouette and fighter planesA neon city with a castle under a magic circleA doorway pouring light from a floating islandA lone rider inside a projector beamA giant robot outside a rainy window

Scoped in code.
Not in a prompt.

Every bot and every tool declares its reach, and the harness enforces it before a single turn runs.

Write-blocked by default

A bot with no write_scope cannot write anywhere. A PreToolUse hook refuses it.

One way in

A capability is a single ToolSpec, bound to its boundary at construction. There is no second path.

One approver

Bots relay a signed human decision. They never originate an outward action on their own.

A promise written in a prompt is not enforcement.

Ready to meet yours?

Pick your app. Use the plugin or npx skills, not both, in the same app.