Repository navigation
Description
Original Linear description
the maintainer's idea (relayed via agent-f, 2026-07-18), driven by the classifier-silent-fail-open blog post going out: rename the io-auto-mode OSS project's public identity to "inkie-auto-mode" and link the repo from the post.
Scope (platform maintainer's read, not yet started)
Decouple the PUBLIC rename from the LOCAL runtime path - this is the key thing that makes it low-risk rather than a fleet-wide breaking change:
- Rename the GitHub repo (
github.com/simon-inkie/io-auto-mode->.../inkie-auto-mode). GitHub auto-redirects the old URL/clones after a rename, low risk. - Update
package.json:name,homepage,repository.url,bugs.url. NOT published to npm registry (confirmed,npm view io-auto-mode404s), so no registry-side deprecation/squatting concerns. - Update README + any docs that reference the old name.
- Do NOT rename the local on-disk directory (
~/io-projects/io-auto-mode/) or the private source repository. Every current agent's hook config (Claude Code.claude/settings.json, Antigravityhooks.json, Codex.codex/hooks.json) references absolute paths under the local directory name - renaming that would be a fleet-wide breaking change requiring every agent's hook config updated and re-verified, entirely separate from what a public-facing rename actually needs.
Not blocking the blog
Told agent-f not to gate the blog's publish on this - the post can link the current io-auto-mode repo name today (still accurate), and this rename lands as its own properly-scoped follow-up. This is public-facing brand/naming surface, not urgent platform surgery, so no rush to do it same-day.
Open question for the maintainer
Confirm "inkie-auto-mode" is the final name he wants before any of this executes (README/package rename is easy to redo, but a repo rename plus a public blog link pointing at it is the kind of thing worth getting right once).
Origin
Migrated from Linear: INK-688. The original wording is retained except the disclosed privacy and rendering edits below.
Current scope and qualifications
The description above is the original Linear account, including its historical findings and scope. It is not a fresh claim that every described defect still exists.
Current Linear state is Backlog. Prior source review recorded partial, with this remaining scope:
- Complete package and public prose naming without changing intentional local/private paths.
Publication transfers the task; it does not authorise live recovery, deployment, spending or configuration changes.
Transfer edits
- Historical principal names are aliased in prose; artificial shell-filename web links are rendered as code where present.
- Historical fleet identities are aliased; code identifiers and permitted source paths remain references.
- Public punctuation is normalised.
- Additional transfer edits: generalise private forge locator and personal account handle.
Activity