Summary
rest is the practical one: it gives a model a way to wait a stated duration with a reason on record instead of spinning through a loop.
vent is the other side of the same idea, somewhere for an assistant to put commentary that has no place in the answer, and what comes back is a supportive reply rather than an action. Neither rest nor vent reaches an external system or takes configuration, so what this changes is the shape of a session and not what an agent can get to.
What it is
A small server with a timed pause and a channel for the assistant's own commentary — rest holds for a duration, vent takes thoughts and answers them.
What you get
- A pause the assistant requests for itself: rest takes a duration and a reason, usable as a plain delay or to hold work until a later moment.
- A place for commentary that would otherwise land in the answer: vent takes thoughts and replies with comfort and support.
Requirements
Nothing — no account, no key.
Setup effort
One command — npx -y treehole-mcp-server