Open foundation
threadpoint
When to use it
Start with free threadpoint when a project has agent-specific files that should become one shared, provider-neutral project layout. It maps local agent instructions, knowledge, rules, and skills into records that other tools can inspect without depending on one agent provider.
Public sources
threadpoint command details live in the public repository. Use those docs for install paths, command flags, examples, security posture, and the current v0 command contract.
Handoff to threadgrid
threadgrid consumes threadpoint records as the open project-scoped foundation. Paid threadgrid workflows add personal and user-level memory, private project stores, cross-project archives, recall, curation, review, publication, and license-aware behavior outside the public threadpoint repository.
Project first
Use threadpoint to establish the shared project layout before expecting threadgrid to reason over project guidance consistently.
Canonical source
Treat threadpoint's public docs as the source of truth for its commands. threadgrid docs explain where those records fit in the paid product.
Common commands
These commands cover the usual project handoff. See the public CLI reference before scripting flags, JSON output, backup restore, pruning, update, or uninstall behavior.
threadpoint init --root . threadpoint adopt --root . --plan threadpoint promote --root . --plan threadpoint scan --root . threadpoint doctor --root . threadpoint validate --root .
Boundary
threadpoint stays local, open source, and project-scoped. It does not sell, license, operate customer accounts, retain session archives, or own personal, user-level, private project, cross-project, curation, recall, or paid automation workflows.
Keep paid product claims in threadgrid surfaces. Public threadpoint behavior should stand alone for users who only want the free project layout and JSON records.
View public repository