Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams and power users who want remote control over coding-agent sessions without moving repos, authenticated CLIs, and local credentials into a hosted SaaS.
Who should use it
Who should skip it
Skip BennyKok/lfg if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
BennyKok/lfg is tracked by RepoRadar as a agent control plane in the Developer Infra section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, BennyKok/lfg is strongest on workflow potential (9.9) and practical usefulness (9.0) and weakest on momentum (6.0) — 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 BennyKok/lfg a composite score of 8.4 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 1.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
lfg launches coding agents with shell access on your own machine, so keep the control plane behind Tailscale or another private access layer instead of exposing it directly to the public internet; The installer provisions services, optional Tailscale serve, and local provider keys, so review the bind address, `.env`, and repo scope before turning it loose on a shared workstation or VPS.