End to end Banking System with File Locking Protocol using Python
experimental zero-trust containment framework for autonomous LLM agents. Intentionally trading development overhead for absolute repository safety and deterministic code boundaries
Windows tray tool that renames/moves/deletes files in cloud-sync folders despite the cldflt lock — copy+delete with delayed retries (CLI + tray + queue.txt).
Portable, zero-dependency multi-agent file-lock system — Exclusive and Team Locks (LOCK*.txt) with scopes, expiry, stale-cleanup, cloud-sync support, and a fast overview cache.
Coordinate multiple AI coding agents (Claude Code, Cursor, Codex) on one repo — declared sessions, file scope locks (advisory/exclusive), and shared decisions, surfaced in VS Code, a browser dashboard, a CLI, and natively via MCP.
Persistent LRU cache with atomic writes, portable file locking, zero dependencies. Drop-in replacement for functools.lru_cache that survives restarts.
Atomic file-locked state management with self-healing reconciler — single source of truth pattern for autonomous trading systems
Lightweight MCP server that coordinates multiple AI coding agents. Prevents overwrite conflicts via file locking, agent tracking, change notifications, and live dashboards. Zero third-party dependencies.
Cooperative FIFO read/write file locks for concurrent Claude Code (and Codex) sessions, via hooks — advisory, multi-file, self-healing, git-safe.
Add a description, image, and links to the file-locking topic page so that developers can more easily learn about it.
To associate your repository with the file-locking topic, visit your repo's landing page and select "manage topics."