К основному содержанию
плагин CX Codex

vibestretch — плагин для Claude Code: перерывы и установка

Плагин vibestretch напоминает размяться или отдохнуть от экрана, пока агент выполняет долгую задачу. Сигнал зависит от времени ожидания, а не от расписания.

MIT ★ 1 596 обновлён 2026-10-29

Установить в Claude Code · Через маркетплейс плагинов Все способы и платформы ↓
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install vibestretch@awesome-codex-plugins
Открыть на GitHub

Что делает vibestretch

vibestretch считает, сколько времени длится работа агента и сколько набралось с предыдущего напоминания. Когда условия срабатывают, он выводит строку в сессию и проигрывает тихий звуковой сигнал. Напоминания включают растяжку, короткие упражнения и отдых для глаз; один и тот же вариант не повторяется два раза подряд.

В Claude Code плагин также может показывать баннер уведомления и строку статуса. В Codex доступны строка в сессии и звук, но нет баннера и сегмента строки статуса. Для установки в Codex нужно открыть /hooks и подтвердить три хука; без этого плагин останется беззвучным. Пороговые значения можно менять через переменные окружения, среди них VIBESTRETCH_SOUND=0 для отключения звука.

Какие задачи решает

  • напомнить размяться во время долгой работы агента
  • отвлечься от экрана с помощью упражнения для глаз
  • получить звуковой сигнал, не следя за терминалом
  • показывать напоминание в строке статуса Claude Code

Примеры запросов агенту

  • Напомни мне размяться, когда я долго жду завершения задачи.
  • Покажи строку статуса vibestretch в Claude Code.
  • Отключи звуковой сигнал vibestretch через переменную окружения.

Как установить vibestretch

Через маркетплейс плагинов

/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install vibestretch@awesome-codex-plugins

По шагам, с командами для каждой платформы: Плагины Claude Code: маркетплейсы, установка и как собрать свой

Вопросы о vibestretch

Как установить vibestretch в Claude Code?

Выполните команды по порядку: /plugin marketplace add hashgraph-online/awesome-codex-plugins, затем /plugin install vibestretch@awesome-codex-plugins.

Что делает vibestretch?

Плагин отслеживает время ожидания агента и при достижении условий напоминает о растяжке или отдыхе для глаз. Он выводит сообщение в сессию и проигрывает звуковой сигнал.

Как включить vibestretch в Codex?

После установки откройте /hooks и подтвердите три хука плагина. До подтверждения он не выдаёт напоминаний.

Исходный текст

vibestretch · MIT
# 🧘 vibestretch

Stretch nudges in your terminal while your coding agent works.

[![HOL Guard](https://img.shields.io/endpoint?url=https%3A%2F%2Fhol.org%2Fapi%2Fregistry%2Fbadges%2Fplugin%3Fslug%3Djunit%252Fvibestretch%26metric%3Dtrust)](https://hol.org/registry/plugins/junit%2Fvibestretch)

![vibestretch nudges you to stretch while Claude Code works](assets/demo.gif)

Your agent grinds for minutes at a time. You sit there, slouched, not blinking.
That window is what ad-supported dev tools sell. vibestretch gives it back to your spine:

```
🧘 Slow neck rolls — 5 each direction. · vibestretch · 7 min of agent time
```

**It isn't a break timer.** A timer runs on a schedule and lands whenever it
lands — usually mid-thought, which is why most people end up turning them off.
vibestretch has no schedule. It counts exactly one thing: the minutes an agent
turn kept you waiting at the machine. It speaks inside that wait and nowhere
else, so a day of quick turns says nothing at all, and there is nothing to
snooze because it never interrupts you in the first place.

The nudge reaches you several ways, because you're rarely looking at the right
spot when it fires:

- a line in the session — for when you're watching the agent work
- a soft chime of its own (bundled, nothing system-sounding) — for when you're
  not looking at any screen at all
- a notification banner (Warp, Ghostty, iTerm2, WezTerm, kitty; in VS Code only
  if you add a notifier extension) — for the moment it fires; what your terminal
  does with it varies, see [How it works](#how-it-works)
- your status line, if you run [`/vibestretch:statusline`](#show-it-in-your-status-line)
  — the one channel that's still there when you come back from another app

All out of the box, nothing to configure. `VIBESTRETCH_SOUND=0` mutes the
sound, `VIBESTRETCH_NOTIFY=0` drops the banner.

Twelve exercises ship with it — stretches, micro-workouts, and eye breaks
(20-20-20 and friends) — rotating so you never get the same one twice in a row.
Swap them for [your own list](#your-own-exercises) if you'd rather.

## Install (Claude Code)

```
/plugin marketplace add Eliasjunit/vibestretch
/plugin install vibestretch@vibestretch
```

That's it. No dependencies, no daemon, no telemetry, no ads, no links in your terminal —
a few small POSIX shell scripts (plus one chime.wav) wired into Claude Code hooks.
Nothing ever leaves your machine.

## Install (Codex CLI)

```
codex plugin marketplace add Eliasjunit/vibestretch
codex plugin add vibestretch@vibestretch
```

Codex doesn't run a plugin's hooks until you have reviewed them: open
`/hooks` and trust the three vibestretch entries. Until then the plugin is
installed but silent.

Rather not use the plugin system? A clone and a config file do the same job:

```
git clone https://github.com/Eliasjunit/vibestretch ~/.codex/vibestretch
cp ~/.codex/vibestretch/hooks/codex-hooks.json ~/.codex/hooks.json
```

Already have a `~/.codex/hooks.json`? Merge the three entries from ours into it
rather than overwriting yours. Codex asks you to trust a new hook config the
first time it runs — that prompt is expected. Pick one of the two ways, not
both: with the plugin and the hand-made entries in place, every hook runs
twice. If you installed by hand before 0.8.0, remove our entries from
`~/.codex/hooks.json` when you switch to the plugin.

What differs from Claude Code: you get the line in the session and the chime,
but no notification banner. Codex parses hook output strictly and drops the
whole object if it contains a field it doesn't know, and it has no field for a
terminal sequence — so sending one would cost you the nudge itself. There's no
status line segment either; that bar isn't scriptable in Codex.

The debt is shared across CLIs, deliberately: an hour of waiting is an hour of
waiting whichever agent kept you in the chair.

## Install (Gemini CLI)

Hooks ship enabled since Gemini CLI v0.26. Clone, then merge our three entries
into your settings:

```
git clone https://github.com/Eliasjunit/vibestretch ~/.gemini/vibestretch
```

Then copy the `hooks` object from `~/.gemini/vibestretch/hooks/gemini-hooks.json`
into `~/.gemini/settings.json`. That file is your whole Gemini configuration, so
merge rather than replace — with `jq` it's one line:

```
jq -s '.[0] * .[1]' ~/.gemini/settings.json ~/.gemini/vibestretch/hooks/gemini-hooks.json > /tmp/s.json && mv /tmp/s.json ~/.gemini/settings.json
```

As with Codex: the line in the session and the chime, no notification banner —
Gemini reserves a hook's stdout for JSON alone, so there's nowhere to print an
escape sequence. `BeforeAgent`, `AfterTool` and `AfterAgent` map exactly onto
the three moments the plugin cares about.

Both non-Claude adapters were built against the published hook contracts —
Codex's generated JSON schemas and Gemini's hooks reference — and have since
been run on live installs: Codex CLI 0.149.1 and Gemini CLI 0.56.0 on macOS.
That run found the one place a contract and its runtime disagree: Codex lists
`suppressOutput` in its schema and rejects it in practice, marking the hook
failed and printing an error under every nudge. The field is Claude Code's
alone as of 0.7.2. If your build behaves differently, an issue with the output
would be welcome.

## When it nudges

vibestretch counts one thing only: **agent time** — the minutes an agent turn was
in flight while you were at the machine, added up since your last nudge. That is
not how long you have been at your desk, and the counter never claims to be: an
hour of reading and typing with quick turns in between adds almost nothing. What
it measures is the time the agent kept you waiting. A nudge fires only when all
three are true:

1. The current turn has been running for a while — you're actually waiting right now
   (default: 2+ min).
2. Your accumulated agent time since the last nudge is high enough — one big task
   or several medium ones both count (default: 5+ min).
3. The last nudge wasn't recent (default: 15 min cooldown).

Step away from the keyboard for 45+ minutes and the debt resets — you already had
your break. That reset is measured against the system's input clock, not against
anything the plugin bookkeeps, so it also fires when you come back to a window
where the agent kept working on its own and you haven't typed a prompt yet.

And time when nobody touches the machine is never counted at all: on
macOS the hooks read the system keyboard/mouse idle clock, so an agent grinding
overnight adds no agent time and never chimes at an empty chair. (On Linux
there's no portable idle clock, so this guard degrades to the 45-minute reset.)
This makes vibestretch model-agnostic by construction: fast models finish
turns before thresholds hit, so there's nothing to mute.

## Configure

Environment variables, all optional (the thresholds are in seconds):

| Variable | Default | Meaning |
|---|---|---|
| `VIBESTRETCH_MIN_TURN` | `120` | Current turn must run at least this long |
| `VIBESTRETCH_MIN_ACTIVE` | `300` | Accumulated agent time since your last break |
| `VIBESTRETCH_COOLDOWN` | `900` | Minimum gap between nudges |
| `VIBESTRETCH_AWAY` | `300` | No keyboard/mouse for this long = you're away: no debt, no nudges (macOS-only detection; `0` disables the guard) |
| `VIBESTRETCH_DISABLE` | unset | Set to anything to mute nudges |
| `VIBESTRETCH_NOTIFY` | `1` | Set to `0` to drop the desktop notification |
| `VIBESTRETCH_SOUND` | `1` | Set to `0` to mute the sound |
| `VIBESTRETCH_EXERCISES` | `~/.config/vibestretch/exercises.txt` | Path to your own exercise list (not seconds — a file path) |

Running an agent headlessly (`claude -p`, `codex exec`, `gemini -p` from a
script, cron, or a bot)? Set `VIBESTRETCH_DISABLE=1` in that environment. Otherwise those unattended sessions
count as sitting time you never actually sat through, and spend the nudge you
should have gotten at your desk.

## Your own exercises

Put one exercise per line in `~/.config/vibestretch/exercises.txt` and the
built-in twelve step aside:

```
mkdir -p ~/.config/vibestretch
cat > ~/.config/vibestretch/exercises.txt <<'EOF'
# blank lines and comments are skipped
Refill the water glass. Yes, now.
Hang from the pull-up bar for 20 seconds.
Look out the window and find something green.
EOF
```

Point `VIBESTRETCH_EXERCISES` at another path if you'd rather keep the file
elsewhere (per-project lists work fine that way). The rotation covers your list
in order, so you don't get the same one twice in a row. A file that exists but
contains nothing usable falls back to the built-ins rather than nudging you with
a blank line — and quotes or backslashes in your text are safe to use.

## How it works

Three [hooks](https://docs.claude.com/en/docs/claude-code/hooks), one per moment
that matters:

| Moment | Claude Code | Codex | Gemini |
|---|---|---|---|
| the agent starts working on your prompt | `UserPromptSubmit` | `UserPromptSubmit` | `BeforeAgent` |
| a tool finished — accumulate wait, nudge if due | `PostToolUse` | `PostToolUse` | `AfterTool` |
| the turn is over — close the accounting | `Stop` | `Stop` | `AfterAgent` |

The nudge is a `systemMessage` (a brief in-session notice shown to you, never
added to the model's context) plus an optional `terminalSequence` carrying the
desktop notification. Terminals that aren't known to support the sequence get
nothing rather than stray bytes.

What your terminal then does with that sequence is its own call: some post a
real OS notification that waits in the notification center, others (Warp) draw
their own banner inside the window — which you never see if you're looking at
another app, and which is gone by the time you come back. Either way it's a
moment, not a record, so vibestretch doesn't lean on it: the chime catches you
while you're away, and the status line is what's still saying it when you
return. On macOS, terminals that post real notifications can be set to
**Alerts** (System Settings → Notifications) so the banner waits instead of
fading.

One consequence of having both channels: if your terminal plays its own sound
for notifications — iTerm2 does out of the box — a nudge arrives as two sounds,
ours and its. `VIBESTRETCH_SOUND=0` drops ours and leaves the one your terminal
already makes.

VS Code deserves its own paragraph, being a common place to keep an agent
running, and it has two surfaces that don't behave alike. In the integrated
terminal the line, the chime and the status line all work — except that Claude
Code prefixes the line with the hook that produced it (`PostToolUse:Bash says:
🧘 …`) instead of showing it on its own. In the extension's chat panel neither
the line nor the status line renders at all, so the chime is the only channel
left: you hear that it's time to move, but not what to do.

The banner is missing on both surfaces by default, and that part isn't Claude
Code's doing — VS Code has no desktop notification of its own for these
sequences and discards them without printing anything. We send it there anyway,
in the form the notifier extensions for that gap read, so installing one turns
the banner on. Tested with Terminal Notification: the nudge arrives as a toast
inside the VS Code window, and a real macOS notification additionally needs that
extension's helper to be granted permission, which macOS asks about once. With
no extension installed nothing is shown and nothing is broken. All of this was
checked on Claude Code 2.1.234.

The terminal's tab title would be the obvious place for a badge, and it isn't
available: Claude Code rewrites the title itself every turn, so anything a
plugin parks there is gone in seconds. Tried in 0.4.2, removed in 0.4.5.

State lives in `~/.cache/vibestretch/`. Exercises rotate so you don't get squats twice in a row.

`sh tests/run.sh` checks the part that matters — that the plugin never claims
time you didn't spend waiting. The system idle clock is stubbed, so "you left
for 90 minutes" is a variable and every case is deterministic.

## Show it in your status line

The in-session notice is transient by platform design, and plugins can't draw
in the status line — that bar belongs to you. So vibestretch offers the next
best thing, one command:

```
/vibestretch:statusline
```

It backs up your settings, wraps your existing status line command (or installs
a minimal one if you have none), and adds the nudge segment: the exercise for 5
minutes after each nudge, fading from bold green to dim as its time runs out,
and a quiet `🧘 12m agent time` counter whenever 2+ minutes of fresh debt have
built up. Run it again after a plugin
update to refresh the helpers; undo with `/vibestretch:statusline off`. If you
ever uninstall the plugin, run `off` first — uninstalling alone would leave the
segment configured but frozen.

Prefer wiring it yourself? The state is plain files
(`~/.cache/vibestretch/`: `current` — latest exercise text, `last-nudge` —
unix time it fired, `active` — seconds of agent time since the last nudge).
Rather than parsing
them by hand, copy `scripts/statusline-segment.sh` somewhere stable and call
it from your status line command — it handles the edge cases (empty files,
mute, staleness) that a quick snippet won't.

## Recently added

- OpenAI Codex CLI support (0.5.0)
- Gemini CLI support (0.6.0)
- Your own exercise list (0.7.0)
- The banner now reaches VS Code, where a notifier extension can show it (0.7.1)
- Codex CLI no longer reports every nudge as a failed hook (0.7.2)
- Installs in Codex as a plugin (0.8.0)

Nothing else is planned right now — the thing does what it set out to do. If it
misses something you'd actually use, open an issue.

## Who made this

Built in public by [Junit](https://github.com/Eliasjunit) — founder building AI
products, apps and games (and trying not to fuse with the chair while the agents
grind).

MIT. Privacy: [PRIVACY.md](PRIVACY.md). Terms: [TERMS.md](TERMS.md).

© Junit · MIT · hashgraph-online/awesome-codex-plugins

Похожие плагины

Каталог плагинов →
ub-mode unclebob Скилл ub-mode для Claude Code помогает разработчикам структурировать изменения в коде. Он направляет процесс разработки, следуя принципам «Сначала заставь работать, затем сделай правильно, затем следуй практикам». CX Codex +1 930установок methodology-advisor FlorianBruniaux Команда methodology-advisor для Claude Code и Codex изучает кодовую базу и задаёт три вопроса, чтобы подобрать подходящий стек методологий AI-разработки. Запускается вручную, когда нужно выбрать процесс до начала активной работы с агентом. CX Codex +1 ★ 6 529звёзд репо discernment-nudge официальный anthropics Плагин discernment-nudge для Claude Code и Claude.ai, который добавляет два-три коротких вопроса после развёрнутого ответа. Помогает проверить факты, разобрать логику и заметить, чего не хватает в рассуждении. ★ 198 522звёзд репо academy-guide официальный anthropics Плагин academy-guide для Claude Code рекомендует курсы, уроки и примеры применения Claude Academy. Он включается, когда пользователь спрашивает, как пользоваться Claude. ★ 198 522звёзд репо claude-api официальный anthropics Плагин добавляет материалы по Claude API и SDK для разработки приложений с LLM. Ставьте его, если пишете код с интеграцией Claude. ★ 198 522звёзд репо example-skills официальный anthropics Плагин example-skills для Claude Code и Claude.ai с набором примеров скиллов. Показывает, как строить скиллы, MCP-серверы, артефакты, тесты веб-приложений и внутренние коммуникации. ★ 198 522звёзд репо document-skills официальный anthropics Плагин document-skills для Claude Code помогает разбирать и готовить офисные документы Excel, Word, PowerPoint и PDF прямо в чате. ★ 198 522звёзд репо impeccable pbakaus Плагин impeccable для Claude Code, который даёт агенту словарь дизайнера и 24 команды для работы с интерфейсами. Запускается на каждом этапе: от сбора контекста проекта до финальной полировки перед релизом. ★ 114 575звёзд репо

Из того же набора391

Весь набор →
writers-loop Плагин writers-loop ведёт написание текста по шагам: рамка задачи, план, черновик, критика, правка по подтверждённым пунктам. Предпочтения запоминает только с вашего согласия. CX Codex ★ 1 596звёзд репо workflow-kit Плагин workflow-kit ведёт продукт от формулировки видения до готового пакета артефактов. Каждую задачу выполняет рабочий агент, а валидирует обязательный независимый ревьюер. CX Codex ★ 1 596звёзд репо wingman Плагин wingman хранит знания о проекте в репозитории, проверяет контракты данных и помогает найти существующие функции. Он пригодится перед правками и при подключении реальных данных. CX Codex ★ 1 596звёзд репо waggle Плагин waggle для Claude Code и Codex хранит решения, ограничения проекта и причины в локальном графе, чтобы агент мог использовать их в следующих сессиях. CX Codex ★ 1 596звёзд репо vibe-portrait Плагин vibe-portrait читает историю ваших диалогов с ИИ и собирает HTML-портрет: MBTI, радар способностей, рейтинг разработчика и persona-скилл, который думает в вашей манере. CX Codex ★ 1 596звёзд репо velith Плагин velith проводит книгу через шесть фаз от пустой страницы до EPUB и PDF: 12 агентов, зафиксированный голос и проверка готовности перед публикацией. CX Codex ★ 1 596звёзд репо usage-engineer Плагин usage-engineer для Claude Code и Codex считает расход токенов в сессиях, сжимает длинные логи и проверяет актуальность карты проекта. Он также выявляет повторные сбои команд. CX Codex ★ 1 596звёзд репо unity-agent-workflows Плагин unity-agent-workflows задаёт порядок работы ИИ-агента с проектами Unity 2D: сначала подтвердить, какие объекты управляют результатом в игре, затем менять файлы и проверять результат. CX Codex ★ 1 596звёзд репо

Спонсоры проекта

Компании, которые помогают держать аналитику открытой