API.DAILY.DEV/PUBLIC/V1/FEEDS · CURSOR PAGINATION · DIRECT / PROXY ROUTING — YOUR KEY STAYS IN THIS BROWSER
— END OF THE WIRE —
INTERNAL READING DESK · NO SERVERS · NO TRACKING
The Daily Reader
Paste your daily.dev personal access token. The page calls
GET /public/v1/feeds/foryou directly — and if the browser blocks it
(CORS), it automatically falls back to the tiny proxy described in SETUP.
THE KEY FIELD IS EMPTY — PASTE IT FIRST
To get your token, go to daily.dev settings → API → Personal Access Tokens
KEY, ROUTING AND DIAGNOSTICS — EVERYTHING STAYS IN THIS BROWSER
CORS BLOCKED? RUN THIS SMALL PROXY ON YOUR MACHINE
DAILY-PROXY.JS — NODE, ZERO DEPENDENCIES
Save this as daily-proxy.js, run node daily-proxy.js,
and keep the proxy URL above set to http://localhost:8010. Done — the page detects it automatically.
Tip: set the DAILY_KEY env var to keep the key on the server only.
Prefer a cloud deployment? The same idea works as a Cloudflare Worker —
forward the path to api.daily.dev/public/v1, echo the
api-key header, add
access-control-allow-origin: *. Ask me for that snippet if needed.
Note: the proxy is only needed if the browser blocks direct calls to daily.dev. If you can call it directly, you don't need a proxy.
Keyboard
THE DESK ANSWERS TO YOUR LEFT HAND
J / Kmove down / up the feedEnter / Oopen the selected postSsave / unsave for laterMmark read / unreadCcopy the link/jump to the filter box?this panelEscclose panels