Let your agents work locally. Keep the boundary.
Lynx is a Windows-first local control center with two independent surfaces: a multi-client MCP Gateway and a bring-your-own-CLI Agents runtime. Accept MCP clients individually or orchestrate coding CLIs already installed on your computer while keeping projects, terminals, approvals, credentials, commands, Git, and cloud automation local.
https://your-tunnel.example/mcpWhat Lynx supports.
A focused local bridge rather than a hosted coding platform. The desktop app controls which projects exist in the MCP catalog, how requests are approved, and which tunnel carries the authenticated endpoint.
How it works.
An MCP application receives no project access until Lynx accepts its OAuth identity. Accepted clients see only Shared workspaces plus explicit Restricted / Private grants, and every project operation stays inside the workspace selected for that client session.
Bring your own coding CLIs.
Lynx Agents does not add another model. Known coding CLIs now use declarative optimized profiles through one shared builder, while custom executables can be capability-tested by the Adaptive CLI Bridge and promoted only after a verified prompt/response path succeeds.
Discover & verify
Rescan known CLIs, add any custom executable, infer candidate capabilities from safe help/version probes, then explicitly Verify adaptive before Lynx enables automation.
Assign roles
Configure Thinker / Lead, Planner, Implementer, Tester, and Reviewer. Mix different CLIs or reuse one tool across several roles.
Run the pipeline
Tasks move deterministically through planning, implementation, testing, review, and bounded revision loops while Lynx tracks each step.
Adaptive transports
Prefer generic headless/stdin execution. Unknown agentic TUIs can fall back to task-scoped lynx-emit callbacks or cryptographic nonce extraction from a rendered hidden PTY.
Verify, don't guess
Write capability is tested only inside a disposable directory. Unknown permission walls are never blindly auto-approved; unverifiable tools remain interactive-only.
Gateway stays independent
MCP client access and Agents orchestration share the workspace registry but have separate policies, sessions, activity, and execution paths.
47 callable MCP tools.
Read operations are bounded. Local mutations follow each client's capability scope, cloud automation follows the global integration policy, and Git mutation tools require the selected workspace to be the repository root. Each client also receives Lynx operating instructions on initialization and can call lynx_info to inspect its current scope, visible projects, integrations, limits, and available tool categories.
Workspace routing
04 TOOLSFiles & search
07 TOOLSLocal command
01 TOOLGit
09 TOOLSCloud & developer automation
26 TOOLSAuthorize once. Keep control.
Lynx persists encrypted OAuth client registrations locally. Previously accepted clients can reconnect normally, while you can disconnect sessions, revoke or block clients, require legacy re-approval, set local capability and request-rate limits, or trigger emergency lockdown at any time.
/mcp URL.What to expect.
Lynx is intentionally transparent about its boundary. It protects workspace paths and adds an approval layer, but it does not pretend local command execution is an operating-system sandbox.
Local-first control
Project contents, workspace registry, approvals and tool execution stay on the machine running Lynx. The public tunnel is transport to the authenticated endpoint.
Workspace containment
File paths are resolved relative to the selected saved root. Traversal and symlink/junction escapes outside that root are rejected.
Commands use your OS permissions
run_command can execute code, reach the network and modify files under your normal Windows account. Review requests is the safer default.
Unsigned Windows builds
Windows SmartScreen may warn until Lynx is distributed with a trusted code-signing certificate. Download releases only from this project's GitHub Release assets.
Tunnel URLs may change
localhost.run addresses are temporary. If the URL changes after restart, update the MCP URL in connected clients. A dedicated ngrok development domain is more stable.
Git is recommended, not required
Normal file editing works without Git. Lynx requires the selected workspace to be the repository root before it exposes Git mutation operations.
Your code stays local.
Connect clients or direct your CLI team.
Install Lynx, connect compatible MCP applications through the authenticated Gateway, or use Agents to orchestrate coding CLIs already installed on your computer.