Every agent you run, one page each
The install line, the directory the skill lands in, the prompt to paste and the command it asks with - for the harnesses people actually search for. The installer supports 79 agents; these are the ones with a page.
Hooks and skills, so every Bash command can wait for you.
A skill in the shared directory. Nothing to configure.
Ask before the agent touches the repo.
Approval for every shell step it runs.
The same approval page, from an editor.
Open source agent, open source approval.
One channel, every agent in the editor.
Long-running work that can still stop to ask.
The terminal asks, your phone answers.
Approval that works in a sandbox with no browser.
Not listed?
The skill is a folder of shell scripts, so anything with a terminal can use it. Run the same line
and check with psh status:
npx skills add passy-ai/psh-now-skill -g -y
What every page has in common
- One channel answers every agent, and many people can answer one channel.
- Ask-only keys for agents: they can request an approval and never grant one.
- Blocks until answered - no polling loop to write, no webhook to host.
- Open source, MIT: the same code runs self-hosted, and the hooks are readable.