Paid workflows
Workflow Guides
Before workflows
Start with a validated project and a configured license status. Use threadpoint for free project-scoped setup, then use threadgrid only for paid workflows that this page labels as shipped or available for customer-safe planning.
threadpoint validate --root "$PROJECT_ROOT" threadgrid license status
Public examples use placeholders and redacted output. Replace placeholder variables locally, but remove private paths, license material, account identifiers, order identifiers, local memory content, prompts, and archive content before sharing output.
Available workflows
License status
Shipped. Checks whether local paid access is configured. With no THREADGRID_LICENSE_KEY, it returns an unconfigured JSON status and does not contact the hosted entitlement service.
threadgrid license status
{ "status": "unconfigured" }
License activation
Shipped. Validates the key from the Polar order email through the hosted entitlement service and writes a redacted activation receipt under local threadgrid state.
threadgrid license activate
Keep the raw key out of source files, shell history, support requests, and public issues.
Configuration inspection
Shipped. Prints resolved local threadgrid configuration with source information and redaction for private paths or sensitive settings.
threadgrid config show
Use redacted, metadata-only configuration output when support needs runtime context.
Archive indexing
Shipped. Indexes selected project knowledgebase records from a project root and returns a JSON summary with the root, index time, and record count.
threadgrid archive --root "$PROJECT_ROOT"
Redact private project paths before sharing archive output.
User memory consolidation
Available as record-only consolidation. Catalogs and consolidates user-level agent guides, knowledge, rules, skills, plugins, imports, adapters, provider home artifacts, and private project stores into threadgrid-owned local records. It does not write shared project files or complete curation/publication.
threadgrid adopt --root "$PROJECT_ROOT" --home "$HOME" --include-user --user-action consolidate --format json
Review the preview first. Apply mode creates local threadgrid consolidation records and evidence citations only.
Planned or unavailable workflows
Treat undocumented paid personal, private, cross-project, archive, curation, recall, review, publication, handoff, support-bundle, and license-cache behavior as unavailable unless this page or the command output explicitly labels it as shipped or preview.
threadpoint remains selected-project-only. Paid personal-memory roots and private project stores are threadgrid-only, license-aware surfaces. User-level consolidation is record-only in v0 and does not publish or rewrite collaborator-facing project files.
Curation
The current CLI reports curate as a planned paid workflow.
Review
The current CLI reports review as a planned paid workflow.
Promotion and publication
threadgrid promote remains available for threadpoint-compatible project promotion. Paid shared publication and review-gate workflows are not customer-available in v0 docs.
Recall and context packs
Cross-project recall, context-pack assembly, and recall indexes remain planned until their state and workflow tasks ship.
Handoff and support bundles
Handoff bundles and reviewable support bundles are planned. Share only metadata-only redacted command output until those commands are documented.
License refresh and cache
License refresh and cached entitlement behavior are planned separately. Use license status and activation for current access checks.
Support handoff
For workflow questions, include the command name, status category, operating system, architecture, and the smallest useful metadata-only redacted output. Never include raw license keys, customer IDs, order IDs, order details, private archive content, prompts, private paths, or unpublished local memory.