Skip to content

v0.6.0

Choose a tag to compare

View all tags
@jperdior jperdior released this 06 Sep 19:12
· 28 commits to main since this release
v0.6.0
84d803d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

An independent plugin

Nothing of the engine lives in the host repository. Installing is three lines in Claude Code:

/plugin marketplace add jperdior/engineering-loop
/plugin install engineering-loop@engineering-loop
/plugin install superpowers@claude-plugins-official
  • The loop scripts ship inside the plugin, beside the skills. The loop resolves the repository from the directory it is run in.
  • Your settings live in ~/.config/engineering-loop/loop.env (setup-loop.sh writes the sandbox tokens there); the loop's state — lock, unit directories, the worktrees it creates, the telemetry — under ~/.local/state/engineering-loop/<repo>/.
  • The telemetry leaves the branch: its table goes into the PR body under Sessions.
  • The only local trace in a repository is .claude/worktrees/ in .git/info/exclude, never committed.
  • The sandbox mounts the plugin, and superpowers when installed, read-only and starts the session with --plugin-dir.
  • install.sh is gone, and so is the vendored .loop/.

Upgrade

Delete .loop/, the ten .claude/skills/ symlinks into it and the .loop/ lines in .gitignore; move .loop/loop.env to ~/.config/engineering-loop/loop.env; install the plugin.

PR #11.

Assets 2
Loading