The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.
TypeScript 3d-modelingagent-frameworkagent-harnessai-agentscadclaude-codecodexcoding-agentsdeveloper-toolsesp32game-developmentmcp-servermulti-agentopen-hardwareopencodeopenharnesspcbroboticsterminaltmux
/**
* One containment check for every RPC that reads or browses this machine's filesystem.
*
* The rule these all got wrong at least once: a path is only inside a folder if the FILE IT RESOLVES
* TO is inside it. `resolve()` rewrites `..` and `./` as text and knows nothing about symlinks, so a
* link sitting inside an allowed folder passes a string check while the read lands anywhere on disk.
* Every caller therefore resolves its target with `realpath` FIRST and only then asks `within`.
*
* The roots differ per RPC because what they hand back differs — `mediaPreview` returns the bytes of
* a file, `gitProject` and `projectPreview` return a repository's shape — so each names its own set
* rather than sharing one global allowance.
*/
import { realpath } from 'node:fs/promises'
import { tmpdir } from 'node:os'
import { isAbsolute, relative } from 'node:path'
import { env } from '../config/env.js'
import { agentTmpRoot } from './agentTmp.js'
/**
* Whether `path` IS `root` or sits below it. Both are compared as text, so both must already be real
* paths — handing this a path straight from a client checks the name of a symlink, not its target.
*
* `relative()` rather than `startsWith`, because `/a/bc` starts with `/a/b` and is not inside it.
*/
export function within(root: string, path: string): boolean {
const rel = relative(root, path)
return rel === '' || (rel !== '..' && !rel.startsWith('../') && !isAbsolute(rel))
}
/**
* Whether the real path `target` is inside any of `roots`. Roots are resolved here, so a root given
* as a symlink still matches the files under it.
*
* A root that cannot be resolved is dropped rather than compared, which makes an empty or entirely
* unresolvable set refuse everything — the failure of this check is always a refusal, never an
* allowance. `HARNESS_FS_BROWSE_UNRESTRICTED=1` is the same opt-out the folder browser has always had.
*/
export async function withinRoots(target: string, roots: readonly string[]): Promise<boolean> {
if (env.HARNESS_FS_BROWSE_UNRESTRICTED === '1') return true
const resolved = await Promise.all(roots.map((root) => realpath(root).catch(() => '')))
return resolved.some((root) => root && within(root, target))
}
/**
* Where agents drop the files they make. macOS gives each user a private `/var/folders/…` as
* `tmpdir()`, but an agent told to "save it to /tmp" writes to `/tmp` itself, so both are roots. Beside a Team account the
* owner's agents have a private folder of their own (./agentTmp.ts), and the daemon's `tmpdir()` is not it.
*/
export function tempRoots(): string[] {
const agents = agentTmpRoot()
return [tmpdir(), '/tmp', ...agents ? [agents] : []]
}