loi-light 0.1.0__tar.gz

loi_light-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

loi_light-0.1.0/PKG-INFO

@@ -0,0 +1,78 @@
+Metadata-Version: 2.4
+Name: loi-light
+Version: 0.1.0
+Summary: Back up every Claude Code session of a repo, and the metadata needed to see how the idea evolved.
+Keywords: claude-code,provenance,transcripts,backup
+Author: Daking Rai
+Author-email: Daking Rai <dakingrae@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Environment :: Console
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Operating System :: MacOS
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.11
+Project-URL: Repository, https://github.com/Dakingrai/loi-light
+Description-Content-Type: text/markdown
+
+# loil — life of ideas, light
+
+Claude Code deletes its transcripts after about thirty days. `loil` keeps them, and
+everything around them that you would need later to see how an idea evolved, in a private
+store on your disk. It does nothing else.
+
+**Everything stays on your machine. `loil` never uploads, syncs or sends anything anywhere.**
+It has no network code, no account, no telemetry and no cloud. The store is a folder on
+your own disk (`~/.loil`, readable only by you), and the only things that leave it are the
+ones you move yourself.
+
+## What it keeps
+
+For every Claude Code session of a repo you `loil init`:
+
+| in the store | what |
+|---|---|
+| `payloads/*.json` | the raw hook payloads (start, end, every compaction) |
+| `transcript.jsonl.gz` | the conversation, byte for byte |
+| `subagents/`, `tool-results/`, … | everything in the session's own Claude directory |
+| `plans/<sha>.md` | every plan file the session named, every version |
+| `file-history/*.gz` | Claude's copies of every file version it edited in the session |
+| `git/start.json`, `git/end.json`, `git/diff-end.patch.gz` | HEAD, branch, status and the uncommitted diff |
+| `claude-project-entry.json` | the project's entry in `~/.claude.json` (cost, tokens, model) |
+
+And per project: snapshots of Claude's project memory and of the repo's agent configuration
+(`CLAUDE.md`, `.claude/…`) whenever they change, your prompt history for the project with the
+pasted text it references, and Claude's own `sessions-index.json`.
+
+Everything is plain files: JSON, JSONL, gzip. `gunzip -c` gives you the original. Each file is
+recorded with its size and sha256, and `loil verify` checks them all.
+
+## Use
+
+```sh
+uv tool install loi-light    # or: pipx install loi-light
+cd ~/your/repo
+loil init                    # hooks into .claude/settings.local.json; imports the sessions Claude still holds
+loil ls                      # the sessions recorded for this repo
+loil verify                  # re-hash every stored file
+loil capture --backfill      # import again (e.g. after sessions ran on another machine)
+```
+
+The store is `~/.loil` (dirs 0700, files 0600). Set `LOIL_HOME` or `loil init --home PATH`
+to keep it elsewhere. Nothing large or sensitive goes inside the repo: it gets
+`.loil/config.toml` (commit it; it is the project's id) and two gitignored per-user files.
+
+The store may hold what Claude's own files hold, including MCP environment values from
+`.claude/settings*.json`. **Nothing in it is ever transmitted: it stays local unless you
+copy it somewhere yourself.** If you point `LOIL_HOME` at a synced folder (iCloud, Dropbox),
+that sync is yours, not loil's.
+
+## Status
+
+Pre-alpha. Hooks, capture, backfill, `ls` and `verify` work for Claude Code. Not yet:
+importing sessions from a `loi` store, a periodic capture to bound loss on a crash, Codex.
+
+## License
+
+Apache-2.0

loi_light-0.1.0/README.md

@@ -0,0 +1,60 @@
+# loil — life of ideas, light
+
+Claude Code deletes its transcripts after about thirty days. `loil` keeps them, and
+everything around them that you would need later to see how an idea evolved, in a private
+store on your disk. It does nothing else.
+
+**Everything stays on your machine. `loil` never uploads, syncs or sends anything anywhere.**
+It has no network code, no account, no telemetry and no cloud. The store is a folder on
+your own disk (`~/.loil`, readable only by you), and the only things that leave it are the
+ones you move yourself.
+
+## What it keeps
+
+For every Claude Code session of a repo you `loil init`:
+
+| in the store | what |
+|---|---|
+| `payloads/*.json` | the raw hook payloads (start, end, every compaction) |
+| `transcript.jsonl.gz` | the conversation, byte for byte |
+| `subagents/`, `tool-results/`, … | everything in the session's own Claude directory |
+| `plans/<sha>.md` | every plan file the session named, every version |
+| `file-history/*.gz` | Claude's copies of every file version it edited in the session |
+| `git/start.json`, `git/end.json`, `git/diff-end.patch.gz` | HEAD, branch, status and the uncommitted diff |
+| `claude-project-entry.json` | the project's entry in `~/.claude.json` (cost, tokens, model) |
+
+And per project: snapshots of Claude's project memory and of the repo's agent configuration
+(`CLAUDE.md`, `.claude/…`) whenever they change, your prompt history for the project with the
+pasted text it references, and Claude's own `sessions-index.json`.
+
+Everything is plain files: JSON, JSONL, gzip. `gunzip -c` gives you the original. Each file is
+recorded with its size and sha256, and `loil verify` checks them all.
+
+## Use
+
+```sh
+uv tool install loi-light    # or: pipx install loi-light
+cd ~/your/repo
+loil init                    # hooks into .claude/settings.local.json; imports the sessions Claude still holds
+loil ls                      # the sessions recorded for this repo
+loil verify                  # re-hash every stored file
+loil capture --backfill      # import again (e.g. after sessions ran on another machine)
+```
+
+The store is `~/.loil` (dirs 0700, files 0600). Set `LOIL_HOME` or `loil init --home PATH`
+to keep it elsewhere. Nothing large or sensitive goes inside the repo: it gets
+`.loil/config.toml` (commit it; it is the project's id) and two gitignored per-user files.
+
+The store may hold what Claude's own files hold, including MCP environment values from
+`.claude/settings*.json`. **Nothing in it is ever transmitted: it stays local unless you
+copy it somewhere yourself.** If you point `LOIL_HOME` at a synced folder (iCloud, Dropbox),
+that sync is yours, not loil's.
+
+## Status
+
+Pre-alpha. Hooks, capture, backfill, `ls` and `verify` work for Claude Code. Not yet:
+importing sessions from a `loi` store, a periodic capture to bound loss on a crash, Codex.
+
+## License
+
+Apache-2.0

loi_light-0.1.0/pyproject.toml

@@ -0,0 +1,36 @@
+[project]
+name = "loi-light"
+version = "0.1.0"
+description = "Back up every Claude Code session of a repo, and the metadata needed to see how the idea evolved."
+readme = "README.md"
+requires-python = ">=3.11"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "Daking Rai", email = "dakingrae@gmail.com" }]
+keywords = ["claude-code", "provenance", "transcripts", "backup"]
+classifiers = [
+    "Development Status :: 2 - Pre-Alpha",
+    "Environment :: Console",
+    "Operating System :: POSIX :: Linux",
+    "Operating System :: MacOS",
+    "Programming Language :: Python :: 3",
+]
+dependencies = []
+
+[project.urls]
+Repository = "https://github.com/Dakingrai/loi-light"
+
+[project.scripts]
+loil = "loil.entry:main"
+
+[build-system]
+requires = ["uv_build>=0.11,<0.12"]
+build-backend = "uv_build"
+
+[dependency-groups]
+dev = [
+    "pytest>=9.1.1",
+]
+
+[tool.uv.build-backend]
+module-name = "loil"

loi_light-0.1.0/src/loil/__init__.py

@@ -0,0 +1,11 @@
+"""loil — back up the trace a coding agent leaves behind."""
+
+
+def __getattr__(name: str):
+    # PEP 562: importlib.metadata costs ~70 ms; only pay it when someone asks, once.
+    if name == "__version__":
+        from importlib.metadata import version
+
+        globals()["__version__"] = v = version("loil")
+        return v
+    raise AttributeError(f"module {__name__!r} has no attribute {name!r}")

loi_light-0.1.0/src/loil/__main__.py

@@ -0,0 +1,6 @@
+import sys
+
+from loil.entry import main
+
+if __name__ == "__main__":
+    sys.exit(main())

loi_light-0.1.0/src/loil/adapters/__init__.py

@@ -0,0 +1,36 @@
+"""Coding-agent adapters: one per tool loil integrates (Claude Code today). An adapter
+name is `^[a-z][a-z0-9-]*$` and is the key everywhere a session says which tool produced
+it: `sessions/<agent>/`, `Session.agent`, and the hook contract `loil hook <agent> <event>`.
+
+Stdlib only, and this module in particular stays tiny: `hooks.run` imports it on every
+session start to validate the agent word. The adapter modules themselves are imported
+lazily by `get`.
+"""
+
+from loil.errors import LoilError
+
+KNOWN = ("claude-code",)
+
+_FIRST = "abcdefghijklmnopqrstuvwxyz"
+_REST = frozenset(_FIRST + "0123456789-")
+
+
+def check_agent(name: str) -> str:
+    """The adapter-name shape (`^[a-z][a-z0-9-]*$`), without importing `re`."""
+    if not isinstance(name, str) or not name or name[0] not in _FIRST or not all(c in _REST for c in name):
+        raise LoilError(f"invalid adapter name {name!r}; expected ^[a-z][a-z0-9-]*$")
+    return name
+
+
+def is_known(name: str) -> bool:
+    return name in KNOWN
+
+
+def get(name: str):
+    """The adapter for `name` (LoilError if the shape is wrong or no such adapter)."""
+    check_agent(name)
+    if name not in KNOWN:
+        raise LoilError(f"unknown coding-agent adapter {name!r}; known: {', '.join(KNOWN)}")
+    from importlib import import_module  # importlib is already loaded by the interpreter
+
+    return import_module(f"loil.adapters.{name.replace('-', '_')}").ADAPTER

loi_light-0.1.0/src/loil/adapters/base.py

@@ -0,0 +1,80 @@
+"""The adapter interface. Stdlib only (the handlers run on the hook path).
+
+An adapter with hooks lists them in `hook_events`; `loil init` installs
+`<shim> hook <name> <event>` for each into the tool's settings file. A passive adapter
+(a tool with no hooks) has `hook_events == ()` and relies on `discover` (find the sessions
+the tool left on disk) and `capture` (copy their artifacts).
+
+A plain class, not a dataclass: `dataclasses` costs ~14 ms on the hook path.
+"""
+
+from pathlib import Path
+
+
+class Source:
+    """One artifact to store: `kind` (transcript|subagent|tool-result|plan|file-history|
+    payload|git|claude-project-entry|other), the absolute `src` on disk — or `data`, the
+    bytes themselves, for content loil generates (a hook payload, a git snapshot) — and
+    `dst_rel` under the session's artifacts dir (`.gz` appended by the adapter when the
+    copy is gzipped; None for a plan, named by content hash). `feed`, if set, receives
+    every chunk read from `src`."""
+
+    __slots__ = ("kind", "src", "dst_rel", "feed", "data")
+
+    def __init__(self, kind, src, dst_rel, feed=None, *, data=None):
+        if (src is None) == (data is None):
+            raise ValueError("Source needs exactly one of src and data")
+        self.kind, self.src, self.dst_rel, self.feed, self.data = kind, src, dst_rel, feed, data
+
+    def __repr__(self):
+        return f"<Source {self.kind} {self.src if self.src is not None else '<data>'} -> {self.dst_rel}>"
+
+
+class Discovered:
+    """A session found on disk by `Adapter.discover`: `id`, its `transcript_path`, and
+    `start`/`end` in loil's timestamp shape (None when the transcript carries none)."""
+
+    __slots__ = ("id", "transcript_path", "start", "end")
+
+    def __init__(self, id, transcript_path, start, end):
+        self.id, self.transcript_path, self.start, self.end = id, transcript_path, start, end
+
+    def __repr__(self):
+        return f"<Discovered {self.id} {self.start}..{self.end}>"
+
+
+class Adapter:
+    #: `^[a-z][a-z0-9-]*$`; the directory name under `sessions/`
+    name: str = ""
+    #: (settings key, `loil hook <name> <event>` event word, timeout in seconds or None)
+    hook_events: tuple[tuple[str, str, int | None], ...] = ()
+    #: Whether `loil init` should add this adapter's settings file to `.gitignore`.
+    settings_are_local: bool = True
+
+    def settings_path(self, root: Path) -> Path | None:
+        """The per-user hook settings file of this tool in a checkout, or None."""
+        return None
+
+    def handle(self, event: str, payload: bytes) -> None:
+        """`loil hook <name> <event>` with a non-empty payload (raw stdin bytes). Stdlib
+        only; never imports argparse. Raise while the project is still unknown (the global
+        log), log to the project's own log afterwards — the hook always exits 0 either way.
+        Writes nothing to stdout: loil injects no context."""
+        return None
+
+    def sources(self, session):
+        """The raw artifacts of `session` on this machine, in copy order, as `Source`s:
+        the transcript first. A source whose `feed` is set gets every chunk of its bytes
+        while it is read (the plan-file scan rides the transcript read pass), and the
+        list may be a generator that yields plan sources *after* the transcripts were
+        read. Raise LoilError when the session cannot be captured here (no
+        `transcript_path`, transcript gone)."""
+        return []
+
+    def discover(self, root):
+        """The sessions this tool still holds on disk for the checkout at `root`
+        (`Discovered`s, oldest first), for backfill."""
+        return []
+
+    def __repr__(self) -> str:
+        return f"<Adapter {self.name}>"