parallax — Claude Code plugin: what it does, how to install
Autopilot for long tasks in Claude Code: spawns an advisory agent in isolated context, finds missed requirements, and loops until the job is fully finished.
/plugin marketplace add anthropics/claude-plugins-community
/plugin install parallax@claude-communityWhat parallax does
The plugin acts as an autopilot for long, multi-step work in Claude Code. Standard runs stop the moment the model assumes the job is done. Appending parallaxthink to a prompt changes this behavior: at the end of each turn, Parallax spins up an advisor agent in an isolated context.
This advisor audits the work against implicit requirements that were left unaddressed. It then feeds the missing piece back into the active turn. The loop runs until the assignment is completed. You avoid writing manual follow-up prompts.
Tooling from the claude-automata repository requires a POSIX system such as macOS, Linux, or WSL, alongside the uv package manager. Without uv, the setup scripts will fail.
What it helps with
- complete multi-step tasks without typing manual follow-up prompts
- detect overlooked project requirements using an isolated advisor agent
- resume unfinished work automatically after the model tries to stop
- keep long Claude Code sessions on track until verified
Example prompts for the agent
- Implement JWT user authentication and cover it with unit tests. parallaxthink
- Refactor the payment processing module and update API docs. parallaxthink
- Fix the memory leak in the background worker queue. parallaxthink
How to install parallax
Plugin marketplace
/plugin marketplace add anthropics/claude-plugins-community/plugin install parallax@claude-communityStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about parallax
How do I install parallax in Claude Code?
First add the community marketplace by running /plugin marketplace add anthropics/claude-plugins-community. Then install the plugin using /plugin install parallax@claude-community.
What does parallax do?
It keeps Claude Code working until all requirements are met. At each turn's end, an isolated advisor identifies unaddressed items and redirects the agent to finish them.
What are the system requirements for parallax?
The underlying claude-automata environment requires a POSIX operating system such as Linux, macOS, or WSL, along with the uv package manager.
Source text
SKILL.md · Apache-2.0
<p align="center"> <a href="https://claude-automata.clomia.com/"><img src="https://raw.githubusercontent.com/clomia/claude-automata/main/site/assets/banner.png" alt="claude-automata: 24/7 full self-driving for Claude Code" width="840"></a> </p> <p align="center"><strong>Your agent stops when it thinks it's done. This one stops when it's actually done.</strong></p> <p align="center"> An agent environment for Claude Code, modeled on human memory.<br> Hand it months of work and rest: it finishes in days. </p> <p align="center"><a href="https://claude-automata.clomia.com/"><strong>See more</strong></a></p> <p align="center"><sub>This README is the summary. The site walks the whole system, animated.</sub></p> <p align="center"> <a href="https://pypi.org/project/claude-automata/"><img src="https://img.shields.io/pypi/v/claude-automata?style=flat&color=f54e00" alt="PyPI"></a> <a href="https://github.com/clomia/claude-automata/blob/main/LICENSE"><img src="https://img.shields.io/pypi/l/claude-automata?style=flat&color=447e48" alt="License"></a> </p> English | [한국어](https://github.com/clomia/claude-automata/blob/main/README.ko.md) --- Claude Code ends its turn the moment it believes it's finished, and loses the detail at the next compaction. claude-automata rebuilds it around the way human memory works: | Plugin | Memory role | |---|---| | **ploop** | working memory: a single session sails autonomously for days; an independent advisor judges every completion claim | | **tx** | consolidation: the screening gate into long-term memory (independent verify, CI, squash merge) | | **refine** | re-grounding: large-scale workflows that eliminate technical debt | Long-term memory is the repository's own git-tracked text, not a database. Recall is grep. Whatever never passes the gate dies with the loop, on purpose. ## Getting started Enter the following instruction in Claude Code: ``` Read https://raw.githubusercontent.com/clomia/claude-automata/refs/heads/main/INSTALL.md with curl -sSL and install claude-automata. ``` Your agent reads [INSTALL.md](https://github.com/clomia/claude-automata/blob/main/INSTALL.md) and installs claude-automata. Needs [Claude Code](https://claude.com/claude-code) and [uv](https://docs.astral.sh/uv/getting-started/installation/) on POSIX (macOS / Linux / WSL). ## Operating the loop ``` /ploop:define-mission # an agent interviews you, interprets your intent, and writes the anchor /ploop:launch [anchor text] # hand it to the loop in a fresh bypassPermissions session ``` Declare the mission done and a hook blocks the stop, demanding an audit by an independent advisor with access to the whole story; the loop ends only when the advisor certifies completion. ``` agent › Mission accomplished. Stopping. advisor › Not yet. The mobile layout was never measured. …resuming. ``` Six rounds later the advisor ends the turn. [Watch a full round on the site.](https://claude-automata.clomia.com/#advisor) The anchor survives every auto-compaction, and the loop fully complies with your subscription plan's terms of service. <details> <summary><strong>Pause, resume, observe</strong></summary> <br> - init sets Auto-Compact; keep it on. The loop runs unattended: open its session with `claude --permission-mode bypassPermissions` (it refuses to launch otherwise), and nothing in it waits for a human — every approval it would ask for is declined and the loop moves on. - `/ploop:off` pauses the loop. `/ploop:on` resumes or restores it, even after an accidental ESC, an API error, or a session limit (interrupt with ESC first if a turn is running). Nothing else stops the loop. - `/ploop:docent` reports the loop's progress. Run it in a **separate session, same directory**: questions go to the docent, and the loop session stays untouched. </details> ## Change as transactions Agents drive tx on their own. Every change lands as one verified, CI-green squash merge behind an integrity boundary, and tx blocks writes to the base branch in between. You review merged results, not work in progress. ## Keep the repository lean ``` /refine:code [focus] · /refine:docs [focus] ``` Repository-wide workflows that clear technical debt: code architecture and doc-to-code alignment. They touch only the representation layer and never change behavior. A run can sweep the whole codebase and take ten hours or more; watch it with `/workflows`. Like the loop, it runs unattended and starts only in a bypassPermissions session. --- <p align="center"><a href="https://claude-automata.clomia.com/"><strong>See more</strong></a></p> Apache-2.0 · Recursive self-improvement: claude-automata is developed inside claude-automata. A Claude Code agent running this environment authored every contribution in this repository.
© clomia · Apache-2.0 · clomia/claude-automata