Every project I work in grows a second set of files. They are useful on my machine. The editor, the task runner, and the coding agent all expect them inside the checkout. Git should never see them.
An HTTP file with the local base URL and a token. Agent hooks and skill files that a coding tool will only read inside the workspace. A Taskfile whose paths point at this checkout. Scratch specs, and a local task list for the work that is not the product. I want those files present when I open the project. I do not want them in the diff.
Copying them by hand worked until I edited the wrong copy. A shell script could drop a directory into three checkouts. It could not tell me the three copies had drifted, and it could not stop Git from offering the files at commit time.
Symlinks looked cleaner: one real file, many paths. Two things ended that. Some tools refuse a path that escapes the workspace, so a hooked file that is only a link might as well be missing. And a symlink is one inode. Editing it in one project changes every project. That is what I want for a shared hook, and the wrong outcome on the day one checkout holds a private experiment in that same file.
I kept a private directory as the real tree and wrote a small CLI, beyond-local-file, to project it. A config maps each tree onto the projects that should see it. The tool writes an ordinary file or directory into each target, and adds that path to the project's Git exclude list. A daemon in the private directory keeps the copies live. An edit on one side becomes the new bytes and fans out. A second copy that was edited from the old bytes is marked out of sync and left in place until I confirm the result in a page on localhost. The tool does not pick a winner for me.
I have used it since the first release in March 2026. Current release is 0.9.0 on PyPI. It covers the daily case: the same local files, in the projects where the tools expect them, absent from the commit. I am not working around it.
I keep two of those private trees, each with its own config. One is personal. One is for work, and its largest entry is a local AI setup projected into a backend checkout: hooks, agent rules, editor settings, a Taskfile, and a directory the agent reads and writes. Those are real files in the target, so a tool that will not step outside the workspace can open them. On the personal tree, the single project is this tool. The task tracker and the draft notes stay out of the public repo, and the tool puts them back in the working tree while I am in it.
Stow and chezmoi stay the right tools for dotfiles in a home directory. This one is for files that belong in several project roots and in none of the commits.
uv tool install beyond-local-file 


