Tanasu0417/execlocus

ExecLocus

See what your agent context resolves—and why.

ExecLocus is a read-only CLI that maps the current Windows/WSL execution context, command resolution, filesystems, and supporting evidence. When invocation or process evidence is available, it can also identify the agent runtime.

It answers a deceptively simple question:

In this context, would the command resolve to Windows, WSL, or a mixture of both—and what evidence supports that result?

Project status: pre-alpha prototype. Runtime, conservative Codex/Claude evidence adapters, path, executable-origin, terminal, JSON, shareable-report redaction, and initial rule foundations are implemented; no release is available yet.

What the first screen will show

The following is an illustrative target for v0.1, not captured output from the current prototype:

ExecLocus
See what your agent context resolves—and why.

CURRENT EXECUTION
  Profile       balanced                       selected
  Runtime       WSL2 / Ubuntu 24.04            observed
  User          dev                            OS account
  Shell         bash                           process ancestry
  Terminal      Windows Terminal               environment hint
  Session layer Wsl                            inferred · certain confidence
  Project       /mnt/c/Users/dev/project       observed · Windows-mounted

Product Claude Code inferred · high confidence · process ancestry Runtime Wsl observed · certain confidence

TOOLCHAIN Git /usr/bin/git Linux · generic PATH fallback selected #1 /usr/bin/git Linux · evidence executable.git.candidate.1 Node /mnt/c/Program Files/node.exe Windows · generic PATH fallback selected #1 /mnt/c/Program Files/node.exe Windows · evidence executable.node.candidate.1 losing #2 /usr/bin/node Linux · evidence executable.node.candidate.2

2 findings ENV002 WSL execution resolves Windows Node warning FS001 WSL project uses a Windows-mounted path info

Run execlocus explain ENV002 for evidence and suggested actions.

## Why this exists

A terminal that looks like WSL does not prove that every agent command, executable, configuration file, and project path belongs to Linux.

Common mixed-runtime setups include:

- A Linux shell resolving Windows Node.js through PATH
- Windows and WSL installations of the same agent
- Linux Git operating across a Windows-mounted project
- Agent state stored across an OS boundary
- A project intentionally kept on `/mnt/c` for Windows and Cowork interoperability

ExecLocus models those boundaries instead of treating every mixed setup as broken.

Current and planned v0.1 interface

execlocus
execlocus check
execlocus explain ENV002
execlocus report --format json
execlocus report --format markdown
execlocus report --format json --redact

The zero-argument command is the primary workflow. No configuration should be required for the first useful result.