Point is version control for AI Native development context.
Git preserves code. Point preserves the participant-visible Session that produced it: requests, agent responses, tool calls, verification, corrections, and decisions. Another agent can continue from the same Point, explore a separate branch, or combine several parent Points without copying their histories.
Point requires Git and Python 3.9 or newer.
python3 -m pip install "git+https://github.com/guix4ever/point.git"
point --versionThe companion Agent Skill lives in skills/point.
Save new participant-visible Session events:
point stash --session-file session.jsonl --title "Bound retry attempts"Inspect and continue:
point list
point show <point-id>
point show <point-id> --full
point resume <point-id>point resume records the selected Point as the parent of the next save. It does not automatically load prior Session events. Consumers read a complete Point only when its original records are needed.
Create independent directions from the same history:
point resume <point-id> --branch implementation
point resume <point-id> --branch alternativeUse several Points as parents of the next save:
point resume <implementation-point> <review-point> --branch masterPoint stores branches and immutable nodes as ordinary Git branches under point-context/v1/*.
point push master --remote origin
point fetch --remote origin
point doctor --remote originUse --with-code with point push only when code and context should be published together.
point hooks install
point hooks statusThe hook creates a Commit Point only when the integration prepared real new Session events before the commit. Ordinary commits without prepared context remain ordinary commits.
session.jsonlis the original participant-visible evidence; Point does not replace it with a summary.- Point does not read or claim hidden model reasoning.
- A parent link proves provenance, not correctness or acceptance.
- Review a Point with
point show <id> --fullbefore publishing it.
python3 -m unittest discover -s tests -vMIT