codemem-mcp 0.1.0__tar.gz

codemem_mcp-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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.

codemem_mcp-0.1.0/NOTICE

@@ -0,0 +1,5 @@
+codemem
+Copyright 2026 Jeff Angelcyk
+
+This product includes marked (https://github.com/markedjs/marked),
+Copyright (c) 2011-2025 Christopher Jeffrey, MIT License, vendored at codemem/web/marked.min.js.

codemem_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,209 @@
+Metadata-Version: 2.4
+Name: codemem-mcp
+Version: 0.1.0
+Summary: One MCP memory for every coding project on every machine: projects, reusable assets, sessions, commits, search
+Author: Jeff Angelcyk
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/jeang42/codemem
+Project-URL: Repository, https://github.com/jeang42/codemem
+Project-URL: Issues, https://github.com/jeang42/codemem/issues
+Project-URL: Changelog, https://github.com/jeang42/codemem/blob/main/CHANGELOG.md
+Keywords: mcp,mcp-server,claude-code,model-context-protocol,ai-agents
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Web Environment
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Version Control :: Git
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: mcp<2,>=1.10
+Dynamic: license-file
+
+# codemem
+
+<!-- mcp-name: io.github.jeang42/codemem -->
+
+**Your coding agents keep rebuilding what you already have. codemem remembers what they built,
+across every project and every machine, and scores each piece on evidence of whether it worked.**
+
+It is an MCP server for Claude Code and other MCP clients. It knows what projects exist, where
+they live, what reusable pieces they contain, what each session did and decided, every commit
+pushed to the git host, and how to do recurring things. Everything is searchable from any
+machine, from an agent, or from the web UI. It is written to *during* work, not after.
+
+One Python process, SQLite, no external services required.
+
+## What makes it different
+
+Inventory scripts snapshot a directory and you read the report once. Registries list what people
+published. codemem does neither.
+
+- **Trust from evidence, not from stars.** Every project and asset gets a computed score from
+  how recently it changed, how much work went into it, whether it is actually deployed and
+  running, whether anything else imports it, and whether a human vouched for it. `verify` records
+  "I ran it today and it works" and restarts the freshness clock. Scores are recomputed on
+  every sync, so they decay when you stop touching something.
+- **It finds the copies you forgot.** Discovery mines every repo at HEAD for scripts, modules,
+  service units, Dockerfiles and MCP servers, hashes their functions, and links repos that share
+  code. It will tell you that you wrote the same retry wrapper in three places.
+- **Agents feed it automatically.** A session hook records what each Claude Code session did,
+  and gives the next session a brief on the project it just opened. The catalogue builds itself.
+- **Maturity is a first-class label.** `authoritative`, `usable`, `experimental`, `antiquated`,
+  `sunset`, `broken`, `junk`, each with a reason. Search ranks by it, and you can exclude the
+  ratings you should not build on.
+- **Your code stays where it is.** codemem stores metadata: names, descriptions, imports,
+  symbols, function hashes, commit records. It does not copy your source anywhere.
+
+## Endpoints
+
+| Endpoint | What |
+|---|---|
+| `http://<host>:8055/mcp` | MCP (streamable HTTP) for Claude Code and other MCP clients |
+| `http://<host>:8055/` | Web UI: search, projects, assets, notes, activity, docs. Dark mode. |
+| `http://<host>:8055/api/…` | JSON API used by the UI (see docs/architecture.md) |
+| `http://<host>:8055/health` | liveness |
+
+Normally runs on the git host, the machine holding the bare repos, so it can read them directly.
+
+> **Security: codemem has no authentication.** It is built for a trusted network, and anyone who
+> can reach the port can read and write everything. Do not expose it to the internet without an
+> authenticating proxy in front of it. See docs/architecture.md.
+
+## Requirements
+
+Python 3.11 or newer, and git. Optional: a git host with bare repos for the commit feed, Gitea
+for descriptions and web links, and [Ollama](https://ollama.com) for semantic search, drafted
+descriptions and the review pass. Everything works without the optional pieces; search falls
+back to BM25 alone.
+
+## Why
+
+A developer with many project folders across several machines has no way for a new Claude Code
+session to know that a retry wrapper, a Gradio helper, a GPU monitor or a data pipeline already
+exists somewhere. So they get rebuilt. Snapshot inventory scripts (run, read, forget) do not fix
+that. codemem is the live, writable layer: it is written to during work, not after.
+
+The content is whatever is there. codemem does not filter or judge. Each project carries an
+`audience`: `unrestricted` (the default), `professional`, or `employer`, so a search or a view can
+exclude one when the context calls for it. Nothing is hidden unless asked, with one exception:
+cloned third-party repos are marked `origin = vendor` and stay out of search and lists until you
+ask for them. See docs/USER_GUIDE.md.
+
+## Install from PyPI
+
+The package is `codemem-mcp`; the command it installs is `codemem`.
+
+    pip install codemem-mcp          # or: uv tool install codemem-mcp / pipx install codemem-mcp
+    codemem serve                    # MCP at http://localhost:8055/mcp, web UI at http://localhost:8055/
+
+    uvx codemem-mcp serve            # or run it without installing
+
+Data goes to `~/.codemem/` unless `CODEMEM_DB` or `CODEMEM_DATA` says otherwise. Register it with
+Claude Code:
+
+    claude mcp add --transport http --scope user codemem http://localhost:8055/mcp
+
+That is the server alone. For the systemd units, the commit feed and the session hooks, use the
+quick start below from a clone of the repository.
+
+## Quick start
+
+Server (once, on the git host):
+
+    ./install.sh                # venv, user-scope systemd units, seed, backfill, gitea, scan, embed
+
+Client (each machine, once):
+
+    CODEMEM_URL=http://<host>:8055 client/install-client.sh    # Linux/macOS: MCP server + SessionStart/SessionEnd hooks
+    client\install-client.ps1                                   # Windows PowerShell (set $env:CODEMEM_URL first)
+
+Then in any Claude Code session the `codemem` tools are available and every session starts with a
+brief of the current project (if codemem knows it) and ends with an automatic session record.
+
+## What Claude sees
+
+| Tool | Use |
+|---|---|
+| `search` | hybrid BM25 + embedding search over everything. First call before building anything |
+| `project_brief` | everything about one project, by name or working directory |
+| `list_projects` | filter by status, tag, machine, audience, visibility |
+| `update_project` | description, purpose, status, tags, audience, origin (own/vendor), visibility, maturity |
+| `register_asset` | record a reusable script/module/prompt/skill/service with a one-line usage |
+| `find_assets` | search or list assets by kind/tag/project, or by imported library |
+| `log_session` | what was done, decided, used, abandoned, and what is next |
+| `add_note` | decision, howto, resource, issue, idea |
+| `delete_note` | remove a note written by mistake, with its index and embedding rows |
+| `link_items` | project uses / could-reuse / supersedes / derived-from another |
+| `rate` | maturity: authoritative, usable, experimental, antiquated, sunset, broken, junk, with a why |
+| `verify` | "I ran it today and it works": restarts the computed trust score's freshness clock |
+| `handoff` / `list_handoffs` | track one implementation replacing another through candidate, shadow, verified, promoted |
+| `howto` | how to publish, add a machine, use codemem, plus whatever docs are ingested |
+| `activity` | commits and sessions across all machines, last N days |
+| `add_scan_root` / `scan_path` | register a directory to scan; scan now (server machine) |
+| `stats` | counts, machines, index coverage |
+| `help` | workflow, tool list, label vocabularies. Also `/codemem` in Claude Code, `/codemem <query>` searches |
+
+## Where the data comes from
+
+- **Git host**: every bare repo in `GIT_ROOT` is backfilled; a post-receive hook posts each push to
+  `/ingest/push` so new commits appear within seconds. See docs/git-commit-feed.md.
+- **Gitea** (optional): descriptions, topics and web URLs, via its API with a read token.
+- **Local scan**: project directories under registered roots, per machine. On the server this
+  is automatic; other machines run `client/codemem_agent.py` once a root is registered.
+- **Discovery**: every own repo is mined at HEAD for scripts, modules, units, Dockerfiles,
+  prompts and MCP servers, recorded as `auto-discovered` assets, with shared-code links between repos.
+- **Docs**: markdown from `CODEMEM_DOC_SOURCES` (this repo by default), re-hashed every sync.
+- **Claude Code**: session records from the hook, plus whatever Claude writes with the tools.
+- **Local model** (optional, via Ollama): embeddings for semantic search, drafted descriptions,
+  and a targeted review of near-duplicate functions and thinly described code.
+
+## Layout
+
+    codemem/        the server package
+      config.py     every tunable, env-overridable
+      db.py         schema, connection, single FTS5 index
+      store.py      all writes (keeps the index in step)
+      search.py     BM25 + Ollama embeddings, reciprocal rank fusion
+      gitsync.py    bare-repo backfill, push ingest, push.log, Gitea
+      scan.py       project discovery + location records
+      discover*.py  asset discovery, shared-code linking (core is shared with the remote agent)
+      trust.py      computed trust scores
+      review.py     targeted model review
+      describe.py   model-drafted project descriptions
+      knowledge.py  doc ingest, howto/asset seed
+      server.py     MCP tools, HTTP routes, JSON API
+      cli.py        serve | backfill | gitea | docs | seed | scan | embed | reindex | backup | sync | discover | review | trust | describe | purge
+      web/          the single-file web UI (+ vendored marked.js)
+    client/         hook, remote scan agent, slash command, per-OS installers
+    systemd/        user-scope units: service, sync timer (6h), backup timer (02:45)
+    docs/           user guide, architecture, git-commit-feed, clients, operations, python-vs-typescript
+
+Storage: `$CODEMEM_DB` (default `~/.codemem/codemem.db`, SQLite, WAL). Backups: `$CODEMEM_BACKUP_DIR`
+(default `~/.codemem/backups/`).
+
+## Status and contributing
+
+Extracted from a system that has been running daily against 165 projects, 735 assets and 2,000+
+commits across three machines. It is stable for that use, but it has had one operator, so expect
+rough edges the moment your layout differs from that one. Issues and pull requests welcome;
+please open an issue before a large change so we can agree on the shape. See
+[CONTRIBUTING.md](CONTRIBUTING.md) for how to run it locally and the two rules that are not
+negotiable, and [SECURITY.md](SECURITY.md) for what it stores and how to report a vulnerability.
+
+Run `scripts/smoke.sh` before pushing: it boots the server against a throwaway database and
+checks that health, the web UI, the JSON API and the schema all come up.
+
+## License
+
+Apache License 2.0. See LICENSE.
+
+Copyright © 2026 Jeff Angelcyk.

codemem_mcp-0.1.0/README.md

@@ -0,0 +1,179 @@
+# codemem
+
+<!-- mcp-name: io.github.jeang42/codemem -->
+
+**Your coding agents keep rebuilding what you already have. codemem remembers what they built,
+across every project and every machine, and scores each piece on evidence of whether it worked.**
+
+It is an MCP server for Claude Code and other MCP clients. It knows what projects exist, where
+they live, what reusable pieces they contain, what each session did and decided, every commit
+pushed to the git host, and how to do recurring things. Everything is searchable from any
+machine, from an agent, or from the web UI. It is written to *during* work, not after.
+
+One Python process, SQLite, no external services required.
+
+## What makes it different
+
+Inventory scripts snapshot a directory and you read the report once. Registries list what people
+published. codemem does neither.
+
+- **Trust from evidence, not from stars.** Every project and asset gets a computed score from
+  how recently it changed, how much work went into it, whether it is actually deployed and
+  running, whether anything else imports it, and whether a human vouched for it. `verify` records
+  "I ran it today and it works" and restarts the freshness clock. Scores are recomputed on
+  every sync, so they decay when you stop touching something.
+- **It finds the copies you forgot.** Discovery mines every repo at HEAD for scripts, modules,
+  service units, Dockerfiles and MCP servers, hashes their functions, and links repos that share
+  code. It will tell you that you wrote the same retry wrapper in three places.
+- **Agents feed it automatically.** A session hook records what each Claude Code session did,
+  and gives the next session a brief on the project it just opened. The catalogue builds itself.
+- **Maturity is a first-class label.** `authoritative`, `usable`, `experimental`, `antiquated`,
+  `sunset`, `broken`, `junk`, each with a reason. Search ranks by it, and you can exclude the
+  ratings you should not build on.
+- **Your code stays where it is.** codemem stores metadata: names, descriptions, imports,
+  symbols, function hashes, commit records. It does not copy your source anywhere.
+
+## Endpoints
+
+| Endpoint | What |
+|---|---|
+| `http://<host>:8055/mcp` | MCP (streamable HTTP) for Claude Code and other MCP clients |
+| `http://<host>:8055/` | Web UI: search, projects, assets, notes, activity, docs. Dark mode. |
+| `http://<host>:8055/api/…` | JSON API used by the UI (see docs/architecture.md) |
+| `http://<host>:8055/health` | liveness |
+
+Normally runs on the git host, the machine holding the bare repos, so it can read them directly.
+
+> **Security: codemem has no authentication.** It is built for a trusted network, and anyone who
+> can reach the port can read and write everything. Do not expose it to the internet without an
+> authenticating proxy in front of it. See docs/architecture.md.
+
+## Requirements
+
+Python 3.11 or newer, and git. Optional: a git host with bare repos for the commit feed, Gitea
+for descriptions and web links, and [Ollama](https://ollama.com) for semantic search, drafted
+descriptions and the review pass. Everything works without the optional pieces; search falls
+back to BM25 alone.
+
+## Why
+
+A developer with many project folders across several machines has no way for a new Claude Code
+session to know that a retry wrapper, a Gradio helper, a GPU monitor or a data pipeline already
+exists somewhere. So they get rebuilt. Snapshot inventory scripts (run, read, forget) do not fix
+that. codemem is the live, writable layer: it is written to during work, not after.
+
+The content is whatever is there. codemem does not filter or judge. Each project carries an
+`audience`: `unrestricted` (the default), `professional`, or `employer`, so a search or a view can
+exclude one when the context calls for it. Nothing is hidden unless asked, with one exception:
+cloned third-party repos are marked `origin = vendor` and stay out of search and lists until you
+ask for them. See docs/USER_GUIDE.md.
+
+## Install from PyPI
+
+The package is `codemem-mcp`; the command it installs is `codemem`.
+
+    pip install codemem-mcp          # or: uv tool install codemem-mcp / pipx install codemem-mcp
+    codemem serve                    # MCP at http://localhost:8055/mcp, web UI at http://localhost:8055/
+
+    uvx codemem-mcp serve            # or run it without installing
+
+Data goes to `~/.codemem/` unless `CODEMEM_DB` or `CODEMEM_DATA` says otherwise. Register it with
+Claude Code:
+
+    claude mcp add --transport http --scope user codemem http://localhost:8055/mcp
+
+That is the server alone. For the systemd units, the commit feed and the session hooks, use the
+quick start below from a clone of the repository.
+
+## Quick start
+
+Server (once, on the git host):
+
+    ./install.sh                # venv, user-scope systemd units, seed, backfill, gitea, scan, embed
+
+Client (each machine, once):
+
+    CODEMEM_URL=http://<host>:8055 client/install-client.sh    # Linux/macOS: MCP server + SessionStart/SessionEnd hooks
+    client\install-client.ps1                                   # Windows PowerShell (set $env:CODEMEM_URL first)
+
+Then in any Claude Code session the `codemem` tools are available and every session starts with a
+brief of the current project (if codemem knows it) and ends with an automatic session record.
+
+## What Claude sees
+
+| Tool | Use |
+|---|---|
+| `search` | hybrid BM25 + embedding search over everything. First call before building anything |
+| `project_brief` | everything about one project, by name or working directory |
+| `list_projects` | filter by status, tag, machine, audience, visibility |
+| `update_project` | description, purpose, status, tags, audience, origin (own/vendor), visibility, maturity |
+| `register_asset` | record a reusable script/module/prompt/skill/service with a one-line usage |
+| `find_assets` | search or list assets by kind/tag/project, or by imported library |
+| `log_session` | what was done, decided, used, abandoned, and what is next |
+| `add_note` | decision, howto, resource, issue, idea |
+| `delete_note` | remove a note written by mistake, with its index and embedding rows |
+| `link_items` | project uses / could-reuse / supersedes / derived-from another |
+| `rate` | maturity: authoritative, usable, experimental, antiquated, sunset, broken, junk, with a why |
+| `verify` | "I ran it today and it works": restarts the computed trust score's freshness clock |
+| `handoff` / `list_handoffs` | track one implementation replacing another through candidate, shadow, verified, promoted |
+| `howto` | how to publish, add a machine, use codemem, plus whatever docs are ingested |
+| `activity` | commits and sessions across all machines, last N days |
+| `add_scan_root` / `scan_path` | register a directory to scan; scan now (server machine) |
+| `stats` | counts, machines, index coverage |
+| `help` | workflow, tool list, label vocabularies. Also `/codemem` in Claude Code, `/codemem <query>` searches |
+
+## Where the data comes from
+
+- **Git host**: every bare repo in `GIT_ROOT` is backfilled; a post-receive hook posts each push to
+  `/ingest/push` so new commits appear within seconds. See docs/git-commit-feed.md.
+- **Gitea** (optional): descriptions, topics and web URLs, via its API with a read token.
+- **Local scan**: project directories under registered roots, per machine. On the server this
+  is automatic; other machines run `client/codemem_agent.py` once a root is registered.
+- **Discovery**: every own repo is mined at HEAD for scripts, modules, units, Dockerfiles,
+  prompts and MCP servers, recorded as `auto-discovered` assets, with shared-code links between repos.
+- **Docs**: markdown from `CODEMEM_DOC_SOURCES` (this repo by default), re-hashed every sync.
+- **Claude Code**: session records from the hook, plus whatever Claude writes with the tools.
+- **Local model** (optional, via Ollama): embeddings for semantic search, drafted descriptions,
+  and a targeted review of near-duplicate functions and thinly described code.
+
+## Layout
+
+    codemem/        the server package
+      config.py     every tunable, env-overridable
+      db.py         schema, connection, single FTS5 index
+      store.py      all writes (keeps the index in step)
+      search.py     BM25 + Ollama embeddings, reciprocal rank fusion
+      gitsync.py    bare-repo backfill, push ingest, push.log, Gitea
+      scan.py       project discovery + location records
+      discover*.py  asset discovery, shared-code linking (core is shared with the remote agent)
+      trust.py      computed trust scores
+      review.py     targeted model review
+      describe.py   model-drafted project descriptions
+      knowledge.py  doc ingest, howto/asset seed
+      server.py     MCP tools, HTTP routes, JSON API
+      cli.py        serve | backfill | gitea | docs | seed | scan | embed | reindex | backup | sync | discover | review | trust | describe | purge
+      web/          the single-file web UI (+ vendored marked.js)
+    client/         hook, remote scan agent, slash command, per-OS installers
+    systemd/        user-scope units: service, sync timer (6h), backup timer (02:45)
+    docs/           user guide, architecture, git-commit-feed, clients, operations, python-vs-typescript
+
+Storage: `$CODEMEM_DB` (default `~/.codemem/codemem.db`, SQLite, WAL). Backups: `$CODEMEM_BACKUP_DIR`
+(default `~/.codemem/backups/`).
+
+## Status and contributing
+
+Extracted from a system that has been running daily against 165 projects, 735 assets and 2,000+
+commits across three machines. It is stable for that use, but it has had one operator, so expect
+rough edges the moment your layout differs from that one. Issues and pull requests welcome;
+please open an issue before a large change so we can agree on the shape. See
+[CONTRIBUTING.md](CONTRIBUTING.md) for how to run it locally and the two rules that are not
+negotiable, and [SECURITY.md](SECURITY.md) for what it stores and how to report a vulnerability.
+
+Run `scripts/smoke.sh` before pushing: it boots the server against a throwaway database and
+checks that health, the web UI, the JSON API and the schema all come up.
+
+## License
+
+Apache License 2.0. See LICENSE.
+
+Copyright © 2026 Jeff Angelcyk.

codemem_mcp-0.1.0/codemem/__init__.py

@@ -0,0 +1,2 @@
+"""codemem: system-coding-memory. One memory for every project on every machine."""
+__version__ = "0.1.0"