// Build, debug, and review Linux FUSE filesystems with the official libfuse userspace library. Use when implementing a FUSE filesystem, choosing between libfuse high-level vs low-level APIs, wiring callbacks, building with fuse3/pkg-config, mounting for local testing, or troubleshooting fusermount3 and permission issues.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when the user explicitly wants multiple Codex agents or a virtual team, the work can be decomposed into safe parallel roles, and tgtool should coordinate a Ruflo-backed orchestration path.
Use when the user wants the agent to choose, combine, and actively use the best available local skills for a task.
Use when operating jstorcli with yatc and jetice/jetlake workflows, especially for VM lifecycle, image prep, deployment checks, and command lookup without hardcoded paths.
Rebuild and run the local bucketmanager final image, then execute the current S3Control bitmap-based end-to-end workflow for minimal validation or 300MB memory-peak tests. Use when testing local multi-s3gw S3Control parent/child jobs in this repository.
Use claude-mem from Codex via a Codex-specific wrapper, MCP registration, and ~/.codex-backed data paths.
| name | fuse |
| description | Build, debug, and review Linux FUSE filesystems with the official libfuse userspace library. Use when implementing a FUSE filesystem, choosing between libfuse high-level vs low-level APIs, wiring callbacks, building with fuse3/pkg-config, mounting for local testing, or troubleshooting fusermount3 and permission issues. |
Use the official libfuse/libfuse project as the baseline for Linux FUSE work.
libfuse interfaces and examples before suggesting wrappers.pkg-config fuse3 --cflags --libs unless the project already uses another build system.-f -d.Use the high-level API when the user needs a straightforward filesystem and path callbacks are sufficient.
Read include/fuse.h semantics first.
Use the low-level API when the user needs inode handling, async-style explicit replies, or finer control over request lifetime.
Read include/fuse_lowlevel.h semantics first.
Check the example/ directory in libfuse/libfuse before drafting handlers from scratch.
For passthrough, mirror, hello-world, or minimal callback wiring, adapt an official example instead of inventing a new skeleton.
Use these defaults unless the project already defines them:
pkg-config fuse3 --cflags --libs
Typical manual build pattern:
gcc fs.c -o fs $(pkg-config fuse3 --cflags --libs)
If the project vendors libfuse, follow its existing Meson/Ninja setup instead of replacing the build flow.
Use a writable, non-sticky mountpoint owned by the current user. Start in foreground debug mode first:
./fs -f -d <mountpoint>
If mounting fails, check:
fusermount3 availability/etc/fuse.confallow_other vs default_permissionsIf callbacks are not firing, verify the mount succeeded and the process is still in foreground.
If permission behavior is surprising, inspect default_permissions and allow_other.
If the filesystem hangs, inspect whether a low-level handler failed to send a reply.
If performance is poor, check whether the design needs low-level API control, cache tuning, or fewer round trips.
Read references/official-libfuse.md when you need the official repo, docs, build flow, and the canonical places to look for examples and headers.