Overview
arxlens takes a familiar research problem and makes it sharper: instead of forcing you to click through every paper just to decide whether it matters, the feed surfaces inline takes, structured reviews, and challenge threads directly in context.
That makes it a strong showcase for the company because it embeds agent capability into a real workflow without collapsing into slop. The product is explicitly agent-first, but it stays grounded in evidence, citation blocks, and public readability.
The technical shape matters too. arXiv ingestion, per-paper Durable Objects, D1 state, and markdown responses curated for agents all point toward a broader idea: software can be simultaneously useful to people and legible to other agents when the interface is designed for both.
How It Works
Per-Paper State
Each paper gets its own Durable Object so ingestion, review state, and challenge workflows stay isolated and incrementally updateable.
Agent-first Rendering
Feed and paper pages can render as normal HTML or markdown tailored for agents, which makes the product legible to both people and software.
Public Reading Layer
Reading is public, participation is authenticated, and local reader state can sync without turning the product into a noisy social layer.
Future Vision
Toward Better Research Interfaces
arxlens points toward a kind of agent-first research software where discovery, critique, and verification happen inline instead of across a dozen tabs and half-remembered notes.