Files and workspace
Read, search, create, patch, move, hash, and inspect files inside authorized workspace roots instead of copying an entire project into chat.
PRODUCT / YOUR COMPUTER
Give your AI the computer environment where the work actually happens.
Connect a Windows, macOS, or Linux computer you explicitly authorize. Noxgild gives compatible AI clients controlled access to local files, terminal processes, the signed-in browser, and native applications while keeping identity, policy, command state, and human gates under Noxgild control.
ONE AUTHORIZED COMPUTER, FOUR EXECUTION SURFACES
The environment around the repo matters.
Real work often depends on local files, installed tools, long-running services, an authenticated browser, and desktop software that a generic coding sandbox cannot reproduce.
Terminal and persistent processes
Run bounded shell commands or start managed processes that stay alive while the AI reads output, sends input, waits, or verifies completion.
Signed-in browser
Use the browser session on the authorized computer when the task depends on an authenticated dashboard, web app, or existing browser state.
Desktop applications
Inspect and operate native desktop interfaces when the workflow cannot be completed through files, terminal tools, or the web alone.
LOCAL EXECUTION
The computer performs the work. Noxgild coordinates the control plane.
File operations, terminal processes, browser rendering, and desktop interaction execute through the authorized local runtime. Noxgild services coordinate authentication, device identity, policy, durable command state, usage, wakeups, and permitted results.
Current local runtime
Windows / macOS / Linux
Certified local runtimes are available for Windows, macOS, and Linux. Cloud Browser remains a separate hosted execution surface.
PERSISTENT WORK
Start a process, keep it alive, and come back to its output.
Development servers, test runners, REPLs, log streams, and other managed processes can outlive a single tool call. The AI can read new output, send input, wait for completion, inspect status, or terminate a managed process when the work is finished.
1Start
2Read output
3Send input
4Wait or terminate
Exact computer targeting
Work is sent to the computer explicitly selected by the AI workflow instead of an ambiguous desktop session.
Authorized workspace roots
File capabilities operate inside the workspace roots authorized for that device.
Verify before replay
When a side-effecting action has an uncertain outcome, verify the real state before repeating it.
WHAT THIS UNLOCKS
Ask the AI for outcomes that require the whole environment.
Run this branch on my QA computer, keep the app running, and verify the fix in the signed-in browser.
Inspect the local service, reproduce the failure, and show me the process and application state.
Find the local project documents, update the right file, then launch the native app and verify the result.