ArchAstro

Scopey — Development skill for Claude Code

Development community

Keep Claude/Codex/Grok/Pi/OpenCode sessions on scope.

How to install Scopey

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ArchAstro/scopey and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Scopey does

Keep Claude/Codex/Grok/Pi/OpenCode sessions on scope.

Alternatives in Development

Nexting — Remote control for Claude Code, Codex, Grok, and Cursor on Mac or PC 1.3k ★
Scope Recall Hermes — Local long-term memory for Hermes, Codex, Claude Code, WorkBuddy and dsh agents: one SQLite store, source-back 438 ★
Harness Remote — Native-session control plane for Codex, Claude Code, OpenCode, OMP and PI 356 ★

README

scopey

[![CI](https://github.com/ArchAstro/scopey/actions/workflows/ci.yml/badge.svg)](https://github.com/ArchAstro/scopey/actions/workflows/ci.yml) [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)

Scopey — the Scope Guy

It looks like you're writing code.
Would you like help staying in scope?

**Keep Claude Code, Codex, Grok, Pi, and OpenCode sessions aligned with your current intent.**

Scopey is a lightweight Rust CLI that turns your prompts into a current scope, checks coding-agent activity against it, and surfaces sessions that need your attention. It can inject a correction into the active session and notify you when work drifts off scope.

Scopey is pre-1.0 software. Config and session formats are designed to remain compatible, but may still evolve before the first stable release.

Install

Install the prebuilt binary with Homebrew:

brew install ArchAstro/tools/scopey
scopey setup
scopey doctor

For installation from source, prerequisites are stable Rust and at least one supported coding-agent CLI for live scope extraction. Tests do not require an agent CLI.

Install from the GitHub source repository:

cargo install --git https://github.com/ArchAstro/scopey.git
scopey setup
scopey doctor

Or clone the repository and use the Makefile:

make                 # debug build
make build-release
make install         # cargo install --path . --force
make setup           # release build + hooks + config
make doctor
make verify-models   # probe claude/codex fast defaults
make test            # unit + CLI integration tests
make lint
make release-check

Tests cover recursion guards, session storage, JSONL logs, judgement parsing, hook detection, config loading, model resolution, and hook CLI paths under isolated `SCOPEY_HOME`.

Or without make: