agentleFS
DeepExtremaDeepExtrema/Tesseract/AGENTS.md

Tesseract

AGENTS.md4 starsChanged 14 days agoMITView on GitHub

Never import C-extension chains (numpy, torch, sentence_transformers) inside an MCP tool body or anything a tool calls lazily. On Python 3.14 + Windows, the first such import inside the FastMCP worker thread stalls until the next stdin message arrives — the server appears to hang forever on single requests (root-caused 2026-07-11; see the audit session log in the vault). Eager-import at server startup in the main thread instead: server._warm_start() exists for exactly this. Verify with python scripts/probe_server.py.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository9 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every pin's sha256 lock must cover each asset its release ships.

    line 22
  2. Distinctive:

    Never import C-extension chains (numpy, torch, sentence_transformers) inside an MCP tool body or anything a tool calls lazily.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Learned User Preferences

  • Executes implementation plans via subagent-driven-development: fresh subagent per task, spec compliance review first, then code quality review.
  • Prefers slow, step-by-step deployment walkthroughs when doing something for the first time.
  • For Oracle Cloud VM creation: use On-demand capacity (not Dedicated host), disable Confidential computing on the instance, and pair A1 Flex with an aarch64 Ubuntu image (e.g. Ubuntu 24.04 Minimal aarch64).
  • Oracle image list "BM Confidential computing" in the Security column does not mean every image requires confidential compute; pick aarch64 Ubuntu for A1 and turn off confidential compute only if the instance form shows an incompatibility error.
  • MCP live sync (python -m tesseract_mcp.mcp_sync without --check) and live-vault styling/provision require explicit user consent; agents dry-run with --check and throwaway vaults only.
  • Skill sync (python -m tesseract_mcp.skill_sync without --check) to the real ~/.claude/skills requires explicit user consent; agents run --check (optionally with a scratch --dest) only.
  • Obsidian screenshots from the live vault need human review of every image before commit (LiveSync banner and personal content).

Learned Workspace Facts

  • tesseract-mcp repo: C:\Users\Taimoor\Documents\GitHub\tesseract-mcp, base branch main; run Python with .venv\Scripts\python; tests with .venv\Scripts\python -m pytest -q.
  • Live Tesseract vault: C:\Vaults\Tesseract; markdown is source of truth; agent writes quarantined to Claude/.
  • Sync deployment: Oracle Always Free A1 VM running tesseract-mcp/server/ stack (CouchDB + Caddy + DuckDNS); Obsidian Self-hosted LiveSync on the vault.
  • Semantic graph markdown in Claude/Graph/ is authoritative; derived cache at ~/.tesseract-mcp/graph.db; run --rebuild-only when graph markdown changed without note re-indexing.
  • Vault installer (scripts/install_conventions.py) is idempotent and never overwrites existing files.
  • mcp-servers.json at repo root is the curated MCP manifest; tesseract_mcp.mcp_sync additively registers servers into ~/.claude.json via claude mcp add (never modify or remove existing entries).
  • vault-template/plugins.json pins Obsidian plugins; provision.py auto-enables every successfully installed pin ([s.id for s in specs if s.id not in errors]).
  • On Windows, mcp_sync resolves the claude CLI via shutil.which (injectable in tests) so npm's claude.cmd shim is found.
  • Obsidian plugin pins must use release tags whose manifest version matches the tag (avoids provision idempotency drift and LiveSync churn).
  • Every pin's sha256 lock must cover each asset its release ships; a pin bump updates the lock per docs/PLUGIN_LOCK.md (independently computed digests, cross-checked against GitHub's published digest when present).
  • (Migrated 2026-07-09 from the retired Sentinal-ESG workspace, where early tesseract work happened.)

MCP server rule: no lazy heavy imports in tool bodies

Never import C-extension chains (numpy, torch, sentence_transformers) inside an MCP tool body or anything a tool calls lazily. On Python 3.14 + Windows, the first such import inside the FastMCP worker thread stalls until the next stdin message arrives — the server appears to hang forever on single requests (root-caused 2026-07-11; see the audit session log in the vault). Eager-import at server startup in the main thread instead: server._warm_start() exists for exactly this. Verify with python scripts/probe_server.py.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.