no token tax
No token tax: why Quell ships zero mandatory AI
If your team already pays for a coding agent, why should its feedback tool sell you another pile of tokens? The case for a deterministic feedback rail and flat seats.
The Quell Blog
Field notes on agent-native feedback.
Notes from building a feedback product around coding agents: what worked, what was only a neat claim, and which boring design decisions mattered more than the model.
Cornerstone · Show HN
We built a feedback widget that lets a coding agent fix its own bug reports
Most bug reports discard the evidence an agent needs, then blame the agent for guessing. This is the shape of a better handoff: the report, the runtime context and the resulting change.
$ quell context 412
## Bug — export button no-op
console TypeError: r.blob is not a fn
network 500 POST /api/export
page /reports?range=q4
→ agent: reproduced · PR #412 opened
status: review-required
More posts
trust-aware routing
Why feedback trust levels matter for safe agent automation
The dangerous sentence in agent software is "it can do this automatically". Trust levels answer the missing question: on whose authority?
Claude Code
How to give Claude Code access to user feedback
Claude Code can search your codebase. It still cannot see the bug report sitting in another inbox. Give it evidence through a read-only MCP connection first.
feedback MCP
MCP server for user feedback: what your agent needs
The MCP connection is the easy part. What the agent gets when it calls get_context is what determines whether the connection is useful.
vibe coding
The missing feedback loop in vibe-coded apps
AI builders have made shipping a v1 a matter of hours. The harder problem starts the day after: knowing what broke. Here is what the Observe step looks like.
Comparisons