The agent that grows with you
Python aiai-agentai-agentsanthropicchatgptclaudeclaude-codecodexhermeshermes-agentllmnous-researchopenai
import { resolveLocalReadPath } from './wsl-path-bridge'
// Path preparation shared by the file-read boundaries that hand a backend-
// reported target to the hardening resolvers. On a Windows host with a WSL
// backend the target is a WSL/POSIX path (`/home/...`, `/mnt/c/...`) the
// Windows fs can't open as-is, so each boundary must route the raw path
// through resolveLocalReadPath (a no-op off Windows / for already-Windows
// paths) before it reaches the resolver. Kept here — mirroring fs-read-dir —
// so the wiring is exercised in isolation instead of buried in main.ts.
/**
* hermes-media:// stream handler's `resolveLocalFile` dependency: the protocol
* handler already percent-decoded the request pathname into `filePath`
* (`parseMediaProtocolTarget` in media-protocol.ts), so this boundary only
* bridges. Decoding or stripping leading slashes again would turn an absolute
* POSIX path (`/home/...`) into a cwd-relative one that ENOENTs into the
* handler's silent 404, and a second `decodeURIComponent` throws on filenames
* containing a literal `%`.
*/
export function resolveMediaStreamFile(filePath: unknown): string {
return resolveLocalReadPath(String(filePath ?? ''))
}
/**
* hermes:readFileDataUrl / hermes:readFileDataUrlForAttach / hermes:readFileText
* IPC handlers: a renderer-supplied path → a bridged fs path.
*/
export function resolveIpcFileReadPath(filePath: unknown): string {
return resolveLocalReadPath(String(filePath ?? ''))
}
/**
* previewFileTarget: `file:` URLs pass through untouched, plain targets get `~`
* expanded, and the result is bridged before it reaches resolveRequestedPathForIpc.
*/
export function resolvePreviewTargetPath(rawTarget: string, expandUserPath: (value: string) => string): string {
return resolveLocalReadPath(/^file:/i.test(rawTarget) ? rawTarget : expandUserPath(rawTarget))
}