Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers and ops teams who need real browser or desktop automation with a clearer safety boundary than pointing an agent at their live machine.
Who should use it
Who should skip it
Pass on agent-sh/agent-workspace-linux if its scope or audience does not match what your team is building right now.
About this signal
agent-sh/agent-workspace-linux is tracked by RepoRadar as a mcp server in the Developer Tools section. It was first seen on 2026-06-26 and last updated on 2026-06-26. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, agent-sh/agent-workspace-linux is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned agent-sh/agent-workspace-linux a composite score of 8.5 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 88.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The runtime can still browse, type, click, and handle files inside its hidden workspace, so start with disposable profiles and non-sensitive accounts; The hard isolation boundary depends on Linux dependencies and the permission ceiling you actually configure, so verify the enforcement path before production use; The control socket is same-user by design, which means shared or multi-user machines need a dedicated account or stronger host isolation.