threadgrid

Paid local memory infrastructure on open threadpoint

threadgrid

A private command layer for agent memory that survives tool churn.

Early paid local tooling for personal memory consolidation, private project scope, archive indexing, recall-ready context, and review foundations. threadpoint stays the open project core; threadgrid adds the operator-grade paid layer around it.

  • Local-first archive indexing
  • Recall-ready context surfaces
  • License-aware paid workflows

Why it exists

A focused v0 for local agent operators

Serious local agent work leaves behind plans, decisions, instructions, skills, support notes, and project-specific context. threadgrid turns those fragments into a paid local operating layer that can be indexed, reviewed, recalled, and kept separate from the open threadpoint foundation.

Archive

Index the traces

Build a durable local inventory from threadpoint knowledgebase records, agent instructions, and session evidence that would otherwise stay scattered across tools.

Recall

Shape recall context

Prepare the right cross-project context path for future work without implying hosted sync, completed recall automation, or team administration in the early paid release.

Review

Review before memory

Keep personal and project-specific findings in a review-ready lane while recall and review remain foundations until their workflow tasks ship.

Boundary

Keep the boundary clear

threadpoint remains open and project-scoped; threadgrid owns paid personal memory, private project scope, archive, recall, support, and licensing.

Archive indexing

See the local memory field before you ask another agent to continue.

The first value is orientation: which records exist, where they came from, what product boundary they belong to, and which pieces are useful for the next run. The visual system mirrors that product model: a grid of durable dots, lit paths, and recall lanes.

agents
sessions
instructions
skills
archives
recall
review
Connected memory nodes flowing into a shared knowledge graph
The v0 visual asset stays in the launch surface while the code-native diagrams add product-specific structure.

Recall-ready workflow

From scattered session residue to reviewed memory candidates.

threadgrid does not need to pretend every automation is complete on day one. The public launch story should show the durable path: collect local evidence, index it, identify useful context, and keep review visible before promotion automation ships.

  1. 01

    Collect

    Local agent materials are discovered from project and user-level surfaces without moving private memory into a hosted service.

  2. 02

    Index

    Records are organized into navigable archive structure so older work can be found, compared, and prepared for reuse.

  3. 03

    Recall

    Relevant context can be assembled for the next agent run while preserving provenance and product boundaries.

  4. 04

    Review

    Findings stay review-ready before promotion into durable memory, reducing accidental long-term knowledge drift.

Product boundary

Open foundation. Paid operating layer. Clear customer expectations.

threadpoint

Open project foundation

Free, provider-neutral project records for shared instructions, memory files, and skill mapping. It stands alone without paid product assumptions.

  • Apache-2.0
  • Project-scoped
  • Provider-neutral

threadgrid

Paid operator layer

Personal memory consolidation, private project scope, archive indexing, recall-ready context, review foundations, support, and licensing.

  • Local-first
  • License-aware
  • Private by default

Early adopter lifetime

Start with the local paid package. Keep the public-launch polish honest.

The current limited-time package is for early local operators who want threadgrid's archive indexing, record-only user-level memory consolidation, support, and license-aware path as it matures on top of threadpoint.