agentleFS
Arch1eSUNArch1eSUN/Arcgentic/skills/cross-session-handoff/SKILL.md

cross-session-handoff

Skill286 starsChanged 5 months agoMITView on GitHub

Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.

The file

Files
SKILL.md

cross-session-handoff

Manages .arcgentic/state.yaml as the shared state medium across multiple AI sessions.

Commands

arcgentic cross-session-handoff read
arcgentic cross-session-handoff write --session-id dev-session --updates '{"current_phase":"dev"}'
arcgentic cross-session-handoff snapshot --session-id audit-session
arcgentic cross-session-handoff acquire-lock --session-id dev-session --ttl 600
arcgentic cross-session-handoff release-lock --session-id dev-session

Rules

  • Reads do not acquire a lock.
  • Writes acquire a TTL lock, write through a temp file, then rename atomically.
  • Snapshots go to .arcgentic/state-history/.
  • A session must not overwrite another non-expired lock.

See also

  • toolkit/src/arcgentic/skills_impl/cross_session_handoff.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.