Vibe coding without the kaboom factor.
- Install slave:
npm i -g @calamity-inc/slave - Create a profile, e.g.:
slave --create-profile luna openai gpt-6-luna --set-defaultslave --create-profile haiku anthropic claude-haiku-5-5 --set-default
In any directory:
slave [options] [--] How do I use the 'slave' command?
You can also pipe text in:
cat yap.txt | slave Summarize this text
Options:
--long/--multiline— write a multiline prompt (mutually exclusive with piping text in)-c/--cont/--continue— add your previous invocation to the context of this one-a/--amend— retry the previous invocation, using the context from before it-w/--web— allow the model to search the web-n/--no-fs/--nofs— disable filesystem access-r/--readonly— disable filesystem write access-s/--sandbox— allow the model to use a docker container-p/--profile<name>— use the specified profile
Single-character flags can be combined, so slave -cw prompt is equivalent to slave -c -w prompt.
Subcommands:
--create-profile<name><provider><model>[--set-default]— create a profileprovidercan beopenai,anthropic, or an OpenAI-compatible base URL likehttp://127.0.0.1:1234/v1for LM Studio.
--update-profile<name><provider><model>[--set-default]— update a profile--set-default<profile name>— set default profile--list-profiles— list all profiles--delete-profile<name>— delete a profile--update-api-key<provider>— update an API Key--set-system/--set-system-prompt[prompt][--long|--multiline]— set or clear the system prompt--get-system/--get-system-prompt— get the system prompt--skills— get info about skills--logs— get info about logs
The model can't run commands on your system; it only gets limited access to your filesystem:
- Restricted to the working directory and its subdirectories.
- Can't read the
.gitfolder,.envfiles, or any files excluded by.slaveignore. Although the model will still be able to know of their existence. - Files that are
.gitignored can't be written to.
However, these restrictions are only as good as your practices; you should:
- Only run
slavein Git-tracked folders and be sure that anything you don't want to lose is committed or at least staged so you can always revert any changes made by the model. - Review changes to your code before running anything, including tests.