daily.dev for agents

daily.dev for agents is a marketplace of plugins that teach you or your agent new workflows on top of the daily.dev API. daily.dev is where millions of developers find out what's next, and this product extends that reach to your agent: you connect Claude, Cursor, Codex or any MCP client, and your agent can read personalized feeds, search posts, learn from discussions, save bookmarks and tune your feed. Every listing in the catalog is published either as a Plugin or as an Agent skill, and the marketplace is built and shared by developers. Alongside the plugin marketplace there is also an apps ecosystem for people who want to build on daily.dev rather than only consume from it, with a documented path for connecting your agent and submitting a plugin. Most of the value a developer collects from daily.dev does not disappear, it just goes stale. Bookmarks pile up and rot in a list you never reopen. Notifications stack into an undifferentiated inbox of replies, mentions, squad reviews and fresh content. The feed follows tags that may no longer match what you are actually building, while your git branch touches libraries, APIs and patterns your feed has never heard about. When an incident fires, when a dependency gets bumped, or when you want to know whether a tool is genuinely worth adopting, the answers live scattered across posts and comment threads that you have no time to read. The marketplace exists to route that knowledge into the surfaces you already work in — your terminal, your editor, your notes folder, your agent — so the content finds you instead of waiting to be found. The reading plugins bring daily.dev into wherever you already look. Unofficial dailydev CLI reads daily.dev from your terminal: your feed, popular and discussed posts, search, comments and bookmarks, and every command has a --json flag so scripts and coding agents can use it too. It installs with npm install -g @devopsdaily/dailydev-cli. daily.dev TUI for Terminal is a Text User Interface made in Go that calls the Daily.dev API into the terminal. daily.dev statusline for Claude Code rotates daily.dev headlines at the bottom of Claude Code while you wait, combining curated major headlines with the community's most-upvoted posts of the day, clickable in your terminal and requiring no API token. daily.dev RSS lets you read daily.dev in any RSS reader: sign in with daily.dev and get a private RSS or JSON Feed URL for your personalized feed. daily.dev Hello world is a starter app for building on daily.dev that signs in with daily.dev and shows your profile, personalized feed and latest bookmarks, pulled live from the public API, ready to fork. Bookmark, notification and profile workflows are covered by their own set of plugins. Bookmarks to Notes exports your daily.dev bookmarks to Markdown notes for Obsidian, Logseq or any folder of files: one note per post with summary, tags, source and links, and later runs sync only what's new so your second brain stays current without duplicates. Bookmark Recap turns what you bookmarked this week into a short reading report you can paste into standup, Slack or a newsletter, grouping your saves by topic, pulling the one-line summaries and telling you what is worth reading first. Inbox Zero summarizes your daily.dev notifications in one short briefing, split into what needs you (replies, mentions, squad reviews), what's social, and what's just new content, with links on everything actionable, and it marks them all read only when you say so. Profile Autofill takes your CV, LinkedIn export or a short career summary and has your agent fill in your daily.dev work history, education, projects, certifications and tech stack, after you approve the plan first. daily.dev Roulette spins the cylinder on a forgotten bookmark: one comes up, and you either spare it and go read it, or pull the trigger and it is deleted from daily.dev for good. Feed tuning and research plugins turn daily.dev into a decision surface. Feed Tuner compares what you bookmark on daily.dev with the tags and sources you follow, then proposes follow, unfollow and unblock changes and applies only the ones you approve. Stack Sync points your agent at a repository, reads the dependency manifests, updates your daily.dev tech stack and follows the matching tags so your feed matches what you actually build, showing you the plan before anything changes. Feed Builder takes a plain-English description such as "Rust backend and observability, 50+ upvotes, no videos" and produces a daily.dev custom feed with the right tags, sources and thresholds, with your agent resolving the tags, creating the feed and applying the filters. Branch Reads reads your git branch, spots the libraries, APIs and patterns you are touching, and finds the 3-5 daily.dev posts worth reading for that exact change. Trend Radar compares daily.dev's popular feed against last week's snapshot and surfaces what broke in, what cooled off and the posts that drove the change. Release Radar is a weekly changelog for your stack, finding release notes, breaking changes, deprecations and migration posts for the tags you follow, writing a digest that leads with what breaks, and saving posts to a bookmark list. Upgrade Scout pulls migration guides, gotchas and community reactions from daily.dev for a library and version and gives you a verdict before you run the upgrade. Community Check reads the most-discussed posts and their comment threads on a topic and summarizes the consensus, the dissent and the production gotchas, with sources. On-call Lookup takes an error or a log line from an incident, has your agent search daily.dev for posts about the same failure, reads the comments for corrections, and gives you the likely causes, the checks to run first and the fixes, each with its source, sending only generic terms and never hostnames or secrets. Hot Take Drafter finds the most-argued post on daily.dev this week, lays out both sides from the comment thread and drafts three takes — the contrarian, the synthesis and the sharp question. daily.dev Roulette rounds out the catalog with a playful but concrete way to clear your backlog. The marketplace is built on the daily.dev API, and the entry point is connecting your agent, with documented instructions for doing so and for how plugins work. A recurring pattern across the agent skills is an approval-first design: Profile Autofill has you approve the plan before anything is written, Stack Sync shows you the plan before anything changes, Feed Tuner applies only the changes you approve, and Inbox Zero marks notifications read only on your instruction. Hot Take Drafter drafts takes but you press send, not the agent. The plugins run in surfaces you already use — the terminal, an editor statusline, an RSS reader, a notes folder or an MCP client — rather than asking you to learn a new destination. The stated outcomes focus on keeping your knowledge current and your attention where it matters. Bookmarks stop piling up and rotting, and your second brain stays current without duplicates. Notifications collapse into one short briefing, with links on everything actionable. Your feed matches what you actually build, so the posts you see relate to your branch, your repository and your tech stack. Incidents get a starting point with sources attached. Dependency bumps come with a verdict before you run them. Adopting a tool comes with the community consensus and the production gotchas up front. Because all of it is delivered where you already work, you spend less time searching and more time on the change in front of you. Concrete workflows show how these plugins fit together. During an incident, you paste an error or a log line into On-call Lookup and get likely causes, first checks and fixes with sources, without leaking hostnames or secrets. Before bumping a dependency or reviewing a PR that does, you run Upgrade Scout for migration guides, gotchas and community reactions. Each week you can run Release Radar for a changelog of your stack that leads with what breaks, then Bookmark Recap to turn your saves into a report for standup, Slack or a newsletter. If you keep a second brain, Bookmarks to Notes exports bookmarks to Obsidian or Logseq and syncs only what's new. When you start work on a branch, Branch Reads finds the 3-5 posts worth reading for that exact change, and Stack Sync keeps your daily.dev tech stack aligned with the repository. Before adopting a tool or technique, Community Check gives you the consensus, the dissent and the production gotchas. Between all of that, Inbox Zero triages your notifications and Feed Builder or Feed Tuner keeps your feed pointed at what you follow and what you actually read. The product targets developers who already rely on daily.dev and who now work through agents and MCP clients such as Claude, Cursor and Codex, along with anyone building on the daily.dev API. The ecosystem is explicitly built and shared by developers, so contributors and plugin authors are part of the audience too. Integrations named in the content include Claude, Cursor, Codex and any MCP client, CSS readers via RSS or JSON feed, Obsidian and Logseq for notes, Slack for sharing recaps, and the terminal and Claude Code statusline as reading surfaces. Technologies that appear explicitly include an MCP server, a Text User Interface written in Go, and npm distribution for the CLI. On pricing, the marketplace itself is a catalog of plugins, and a limited-time promotional offer is noted on the site: a Product Hunt week promotion gives 25% off with the discount already applied, ending October 20th, redeemable through Get Plus. Taken together, daily.dev for agents is the bridge between the developer news that daily.dev curates for millions of developers and the agents that now do much of the day-to-day work. It keeps your feed, bookmarks, notifications, profile and research habits connected to the places you already work, and it does so with plugins and agent skills that are built and shared by developers themselves.