CalvinBuild
Show HN: LocalAgent v0.5.0, a local-first Rust agent runtime
https://github.com/CalvinSturm/LocalAgent
LocalAgent is a local-first agent runtime in Rust focused on tool calling, trust and approval gates, replayable runs, and benchmark-gated coding workflows.A lot of the recent v0.5.0 work was about hardening coding-task behavior, improving validation and completion behavior, and reducing the ways evals can be gamed.One thing that stood out during that work was OmniCoder-9B Q8_0. I care less...
Show HN: LocalAgent: local coding agent CLI with trust and replay
https://github.com/CalvinSturm/LocalAgent
Repo: https://github.com/CalvinSturm/LocalAgentWhat it does:- Runs against local providers (LM Studio / llama.cpp server / Ollama) - Tool calling with explicit hard gates (--allow-shell, --allow-write, write tools opt-in) - Trust layer: policy rules, approval workflows, audit trail - Replayable run artifacts + verification - MCP stdio tool support (including Playwright MCP) - Eval harness for...
Also +1 on photoreceptors. The rods/cones split and sensitivity shifts in low light are a big part of why certain wavelengths and lower absolute luminance can feel disproportionately readable at night. I’m less confident that “slow reaction” is the main fatigue reducer (persistence trades off smear vs flicker/visibility), but the broader point about temporal characteristics affecting comfort is spot on.
I think a lot of the fatigue is absolute luminance and black level, not just contrast ratio. Modern panels often can’t get dim enough (and their lowest backlight still isn’t “dark”), so you end up fighting the display. Your approach of boosting for sun and going below the monitor’s nominal minimum at night is basically what an ergonomic default should do.
Out of curiosity, what app are you using to go below the monitor’s stated minimum?
Also agree on the “commodity default” point. Green was the cheap bright workhorse for a long time, and amber felt more like an option when manufacturers could justify it (and when the use case was heavier on text comfort vs max visibility). Your vector monitor anecdote is exactly the kind of real-world constraint story I was trying to get at.
And yeah, high-end scopes were a different world: once you’re optimizing instrumentation, you start paying for different phosphors/persistence/sharpness tradeoffs instead of the mass-terminal defaults.
Ask HN: Why were green and amber CRTs more comfortable to read?
I have been looking into how early CRT displays were designed around human visual limits rather than maximum brightness or contrast.Green and amber phosphors sit near peak visual sensitivity, and phosphor decay produces brief light impulses instead of the sample and hold behavior used by modern LCD and OLED screens. These constraints may have unintentionally reduced visual fatigue during long...