EfeDurmaz16

Fabric — Development skill for Claude Code

Development community

Move a coding-agent job between machines and pick it up where it stopped.

How to install Fabric

This entry records only its repository, not the path inside it, so there is no exact command to give. Open EfeDurmaz16/fabric and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Fabric does

Move a coding-agent job between machines and pick it up where it stopped. The workspace, its caches and the Claude Code or Codex session travel together. Rust node, CLI and SDKs. Early and under review.

Alternatives in Development

System Cache Cleanup — Clean temporary files and caches to free disk space: $ARGUMENTS 23.4k ★
Brainstorm Ideas New — Brainstorm feature ideas for new products in early discovery 7.8k ★
Langchain Skills — ⚠️ — This project is in early development 1.2k ★

README

Fabric

A job is the unit of development work. Storage, compute, environment and harness stay decoupled, so a job started under Claude Code on one machine can be suspended, resumed on another machine with its dependencies, and continued by a different agent.

Private repository. Working name; see [ADR 0010](docs/adr/0010-name-and-scope-boundaries.md) on the name collision.

Status, honestly

Core types only. Nothing suspends or resumes yet.

What	State
Architecture page and glossary	Written: docs/architecture.md, docs/glossary.md
ADRs 0001 to 0012	Written, see below; amended 2026-10-19 after the step 1 research
`crates/fabric-core`	Ids, paths, the job ledger with its record codec, the lease and the cooperative move protocol, snapshot manifests and the environment spec. Pure: no IO, no clock, no socket. Property-tested against the ADR 0003 invariants.
Every other crate in the layout	Does not exist yet
CI	fmt, clippy, test, doc, `cargo deny` and the hygiene script on macOS and Ubuntu

Nothing here suspends or resumes anything. Do not install it.

First gate

One job, adopted with `fabric job init` from a checkout where Claude Code is already running on a MacBook Pro, pushed to a MacBook Air with `fabric job move --to`, resumed there at the same absolute path, dependencies included when their carry key matches and rebuilt when it does not, safe under `kill -9` at every step. Two nodes, same user and home, same OS and architecture, different tool versions, explicit commands only. When that passes, the next stages are the Codex adapter, the ACP adapter, and the sleep watcher.