The Growth Plan is now available: everything in Pro, plus an AEO toolkit for a flat $29 a month. Your next reader asks ChatGPT, gets one answer, and never sees a results page. The toolkit is built for that: - AEO score in the editor, eight checks before you publish - FAQ blocks that ship as structured data - Per-bot robots.txt toggles for AI crawlers, plus an llms.txt index of your posts - Freshness queue so you know what to update next - Daily checks on whether ChatGPT, Claude, Gemini, and Perplexity cite you Upgrade from your dashboard's billing page. Full details are on hashnode.com/pro under the Growth tab. 📖hashnode.com/changelog/2026-…

A clean explainer on what a background coding agent actually is, and how it differs from the tools people already have open. The framing that makes it click: sort AI coding tools by how often a human closes the loop. Autocomplete asks every few seconds. IDE agents like Cursor and Claude Code ask every few minutes. Background agents run in a cloud sandbox and ask once, at the pull request. Same models underneath. What changes is where the loop runs. The part I'd underline is what should arrive attached to that pull request. A diff on its own puts the whole verification burden back on the reviewer. The checks it passed, a self-review of the diff, and a recording of the change working in a real browser are what make review quick enough to be worth doing. There's also a good point on security: safety comes from isolation and scope, not from trusting the model to behave. factorykit.ai/blog/backgroun…

If you're weighing whether to build an AI software factory in-house, this is the build log to read first. "The coding agent is the part you do not build." The project is the seven stations around it: isolated execution, snapshot templates, credential handling, git and PR orchestration, a server-owned run loop, live observability, and verification. Verification is the one everyone underestimates, since a green CI run tells you nothing about whether a user-facing change actually works. Two costs that never reach a budget line. Review attention grows faster than anything on an invoice. And an internal factory is a product with exactly one customer, so somebody owns it for as long as the company runs it, and that name usually gets decided by accident. The other useful reframe: running cost scales with how many tasks you queue, not how many engineers you employ. sandeep.dev/blog/what-a-soft…

Sandeep puts the line between agentic coding and vibe coding in the place that actually decides anything, which is where the review happens. "Both start with a prompt. Only one of them ends with somebody reading the diff." The post comes with three weeks of numbers from a real repo. Agents opened 69 of the 99 PRs that merged, 56 of those went in unchanged, and 13 needed a human to correct them. The useful finding is what those 13 had in common. Every one was a task where nobody had written down what finished looked like, which makes an 18.8% correction rate a measure of the task description as much as of the agent. There's also one example that justifies the whole review gate: an agent shipped image upload and left the files publicly readable. Review caught it inside a day. sandeep.dev/blog/agentic-cod…

AI software factory covers four different purchases, and vendors rarely tell you which one you're being shown. Buy a platform and you get the plumbing between the stages, then you integrate it into your own stack. Assemble one and you pick the sandbox, the coding agent, the verification layer and the credential broker separately. Self-host the lot if compliance says code cannot leave the network. Or have one built inside your environment and handed over to you. The stages are the same in every case: intake, isolation, implementation, verification, pull request. What changes is who does the integration work, and how long you wait for the first PR. Two things I'd check before sitting through a demo. Isolation is harder than it looks and gets underestimated in almost every plan. And assembled stacks tend to drop verification, which leaves you with an agent that opens pull requests nobody trusts. There is also no published first-attempt merge rate from anyone, so you cannot compare reliability across vendors yet. The tools available at each layer: hashnode.com/blog/ai-softwar…

Everyone is suddenly building an AI software factory: a system where coding agents take a ticket to a verified pull request with no human in the middle. The term is from Hitachi in 1969, and this is its third revival. What strikes me about the category is how converged it already is. Devin, Factory, 8090, and FactoryKit all run the same five stages: intake, isolation, implementation, verification, PR. When four vendors independently arrive at one architecture, that usually means it's durable. What's missing is measurement. There is no public benchmark for ticket-to-merged-PR reliability across any of these products. The naming is outrunning the measuring, and buying decisions are running on demos. Full disclosure, we build one of the four, so I wrote this with the gaps in as much detail as the pitch: hashnode.com/blog/ai-softwar…

Cookie consent is now available for Pro publications on custom domains. The point of doing this at the platform level: analytics and marketing scripts don't load until the reader agrees. Most cookie banners are theatre, because the consent script loads, the banner appears, and the trackers it's asking about have already fired. Readers can accept all, reject all, or decide on analytics and marketing separately. Withdraw later and the trackers stop and their cookies get cleaned up. Essential storage isn't in the prompt, since the site doesn't work without it. Setup is on the Integrations page: tick the box, add your privacy policy URL, save. It covers blogs Hashnode renders, so headless setups stay your call. hashnode.com/changelog/2026-…

Mac keyboard shortcuts look like sixty unrelated key combos. Most of them are one system that macOS inherited from Emacs through NeXTSTEP, and Apple documents the bindings without ever mentioning where they came from. That framing changes how you learn them. Control+A, Control+E, and Control+K move and delete the same way in a Slack message, a Safari address bar, and any native text field. One model, applied everywhere, with two predictable breakpoints: terminals, where Control+D ends your shell instead of deleting forward, and Electron apps. The underrated one: Command+Backtick cycles between windows of the same app. Most developers alt-tab past the window they want daily without knowing it exists. hashnode.com/blog/mac-keyboa…

Ship it.

MCP's new revision removes protocol-level sessions, the initialize handshake, and SSE resumability. The reasoning is sound: stateless requests mean load balancers and gateways can route MCP traffic without sticky sessions. The migration is the hard part. It breaks in both directions. A new client against an old server fails, and an old client against a new server fails differently, with unexplained 400s on one side and silently wrong semantics on the other. The SDKs make it concrete: TypeScript v2 shipped on 28 July, Python is still on a release candidate. A TypeScript v2 server with a Python v1 client fails today, not in some future deprecation window. Roots, Sampling, and Logging also start a twelve-month deprecation clock, and the spec's suggested replacements are notable: pass directories as tool parameters, call your LLM provider directly, write logs to stderr. A protocol telling you to route around its own abstractions has learned something. What breaks and how to migrate, on both sides: hashnode.com/blog/mcp-statel…

Two things about Claude Opus 5 that most coverage got wrong. It isn't a price cut. Opus 5 costs $5/$25 per million tokens, exactly what Opus 4.8 cost. "Cheaper frontier model" compares it against Fable 5 at $10/$50, which is a tier difference, not a discount. And the effort parameter has five levels, not three. The bigger catch: switching effort mid-conversation invalidates your prompt cache. A low-effort request that misses cache costs 38% more than a high-effort one that hits it, so toggling effort per request to save money can do the opposite. Even when it works, effort cuts output tokens only. A 40% output reduction saves 18% on a write-heavy workload and 3.6% on a read-heavy one. hashnode.com/blog/claude-opu…

Kimi K3 came first in the Frontend Code Arena, ahead of Claude Fable 5 and GPT-5.6 Sol. Push a million tokens each way and K3 bills $18 where Fable 5 bills $60. The "largest open-source model ever" framing is premature though. Moonshot hasn't published the licence, and as of 27 July there's no K3 repo on their Hugging Face. K2's licence was modified MIT, not MIT, so anyone planning commercial use is guessing. Also worth knowing before you get excited about self-hosting: the weights alone need ~1.4 TB of GPU memory. The $3/$15 API undercuts the hardware for almost everyone. hashnode.com/blog/kimi-k3-be…

Hashnode now has an official skill for AI agents. npx skills add Hashnode/gql-skill That's it. Claude Code, Cursor, or Copilot can publish to your blog, edit old posts, manage drafts, upload cover images. Why a skill instead of just pointing agents at our GraphQL docs? Because agents kept getting the details wrong. They'd paste access tokens into chat, retry calls that were never going to succeed, ask a feed for 500 posts when the API caps a page at 100. The skill bakes those rules in, so the first request works. Write your draft wherever you write. Then: "publish this to my Hashnode blog." github.com/Hashnode/gql-skil…

Every post on Hashnode now has a "View as Markdown" button. One click, raw markdown, ready to paste into your editor, your notes, or your favorite LLM. Read the post. Grab the source. No scraping required.

How it works : Send "Accept: text/markdown", and the article URL returns markdown instead of the rendered page. Agents that ask for markdown get markdown; everyone else gets HTML. Humans can try it too. Add .md to any article URL: blog.ipseeta.dev/how-to-map-…

🔗 Learn more: hashnode.com/pro

A brand-new blog starts with zero search authority. An article on Hashnode doesn't. It ranks in search and gets cited by AI engines from day one. Hashnode Pro builds on that reach: → Your own custom domain → GraphQL API and headless mode → AI writing tools in the editor → Webhooks, GitHub backup, bulk import → Hashnode branding removed

164 devs already in. are you? join the breaking apps hackathon. cash prizes and swag for early submissions.

Who's in? 👀 🧑‍💻

hmm… 🤫

hashnode now has forums. come say hi.

haan zinda hai bhai… community grow bhi kar raha hai.

Hashnode gets traffic from around the world every 24 hours. If you're building something new and your blog isn't on Hashnode, you might be missing out on AEO indexing by LLMs. Hashnode is one of the most trusted sources for AI answer engines today.

We missed you too. New Hashnode, same home.

Hey @aaishika, article subtitles are now prioritized over content brief on all layouts. Thanks for the feedback.

Happy New Year 2026! May your drafts finally get published.

Hey Luke, just curious, did you copy and paste this content into Hashnode's editor before publishing? We're trying to reproduce the issue on our end but manually typing Directory.build doesn't turn it into a link for us. Can you try unlinking it and updating your post?

The “Ticket Engineer Trap” Imagine scrolling through your Jira tickets and seeing the latest ones marked as resolved — by AI. ✅ @waterrmalann explains why becoming a “ticket engineer” is risky in today’s AI-driven software development landscape. 1/n

Drum roll, please... 🥁 The results of the ModusHack by @hypermodeinc are here! 🎉 A big thank you to all the participants who showcased their brilliant skills and ideas in building intelligent apps with Modus, AI models, and Hypermode. 👉 Check out the ModusHack Winners Gallery from Hypermode: hshno.de/modushack-result

🚨 Last Chance to Submit Your ModusHack Project Time is almost up! With 1 day left, this is your moment to showcase your project and compete for the $10,000 prize pool. ⏳ Here’s your submission checklist: 1️⃣ Publish a blog post on Hashnode tagged with #ModusHack 2️⃣ Include your GitHub repo link 3️⃣ [Optional] Add a video demo to highlight your project 👉 Submit here: hshno.de/ModusHack Make these final hours count. Submit today and let your hard work shine! 🚀

Day 3 of ModusHack! We're almost at the finish line with 3 days left to showcase your intelligent apps built with Modus, AI models, and @hypermodeinc. 🚀 Have your project ready? Share it in the comments, we’re excited to see what you’ve created! 🔒 Build with Modus, AI models, and Hypermode 💡 Share your journey on Hashnode 💸 Compete for a $10,000 prize pool! Let's wrap up with a bang! 💻🔥

Only 5 Days Left to Wrap Up ModusHack! As we enter the final stretch, it’s time to start showcasing your intelligent apps built using Modus, AI models, and @hypermodeinc! 🚀 Judging Criteria: 🌟 Innovation 🎯 Relevance 📽️ Presentation 📚 Educational Value Prizes Up for Grabs: 🏆 Grand Prize: $3,000 🥈 Runner-Up: $2,000 🏅 Honorable Mention: $1,000 Plus special prizes for Best Blog/Presentation, Best Non-AI App, Best Dgraph + Modus App, and Best Multi-model App. Total Prize Pool: $10,000! 💸 Got your project ready? 🎉 Drop it in the comments below—we can’t wait to see the amazing things you’ve built! 🚀🔥 Make these final days count—happy hacking! 💻

The weekend is here, and it’s the perfect time to dive into ModusHack! 🌟 You’ve got 7 days left to create something amazing, an AI-powered solution or an intelligent app, for a chance to win big! 🚀 🔒 Build with Modus, AI models, and Hypermode 💡 Share your journey on Hashnode 💸 Compete for a $10,000 prize pool! Brought to you by Hashnode and @hypermodeinc Let’s make these last days count; happy hacking, everyone! 💻

Create a new docs project for free 👉 hshno.de/docs

"Hashnode's ability to sync with our GitHub docs repo and seamlessly publish the content as beautiful docs was the killer feature for us." — Richard Davey, CTO, Phaser studios. ⚡️ Instant API docs from OpenAPI spec ⚡️ All-in-one place for guides, API references, and changelogs ⚡️ Built-in, faster "Ask AI" for documentation ⚡️ GitHub sync for smooth open-source collaboration ⚡️ Simple, visual MDX editor right in the browser ⚡️ Custom domains and sub-path support ⚡️ Blazing fast, SEO-friendly pages Loved equally by developers and content teams.

Need help with submissions? Check out the details here: hshno.de/ModusHack.

9 Days Left to Wrap Up ModusHack Hackathon ⏳ This is your chance to build an intelligent app with Modus and @hypermodeinc and compete for awesome prizes. We hope to see creative projects; here are some ideas of what we expect: - AI-Powered Voice Assistant - Smart Recipe Recommender - and so much more 🔒 Build Intelligent Apps With Modus, AI models, and Hypermode. 💡 Blog about it on Hashnode 💸 $10,000 prize pool up for grabs!

Ready to create dev-friendly, beautifully formatted docs for your product? 🌐 With the same ease and speed as writing your blog posts? Start here: hashnode.com/products/docs 6/n

Oh, and search? Docs by Hashnode comes with "Ask AI" search baked in — an AI-powered search that understands visitors' questions and gives them relevant answers instantly. 🤖✨ For those who prefer, super-fast Algolia search is also available. 🔍 5/n

And yes, our docs editor comes with MDX support, just like the blog editor. It's a rich visual WYSIWYG MDX editor — best of both worlds. Create with Markdown, see it live as you write. No more switching back and forth. 4/n

If you have a blog on Hashnode, adding docs is seamless. 🏳️ Docs can be hosted under the same subdomain or sub-path (like /docs). No separate setup. Your whole developer hub — blog + docs — in one place. 3/n

Hashnode gives you everything you need to create multiple product guides, API references, and changelogs under the same project — in the same way you’d write a blog. 👨‍💻🤝 Easy to set up, easy to write. Plus, it looks amazing right out of the box. ✨ 2/n

👀 Did you know you can create beautiful product and API documentation with Hashnode? Not just a blog platform anymore, Hashnode now lets you create docs that scale with your code. Let me tell you more about it. 🤔 1/n

✨ Mastering Periodic Tasks in Python! Learn how to run periodic tasks easily with cron jobs, Celery beat scheduler, and Django Admin in this latest article by @snehangshu_. 🔗 hshno.de/GPx8Kqq

Coding on a Linux based ecosystem? Here’s a list of Rust based CLI tools by @ddebajyati that can help you improve system performance. → exa → fd → Bat 🔗 Read more here: hshno.de/TUz6FKi

19 days remaining to participate in #ModusHack hosted by Hashnode x @hypermodeinc 📢 👨‍💻 Build an AI-powered open-source project using Modus ✍️ Blog about it on Hashnode 💰 Win up to $10,000 in prizes 🔗 hshno.de/ModusHack

Accessibility is a necessity, not an optional add-on. In a recent article, @dev_is_a_dev provides an implementation guide on: ➡️ How to make your site keyboard-friendly ➡️ Ensuring sufficient color contrast ➡️ Adding ALT text to images 🔗 Read the full article to learn more about accessibility: hshno.de/lwGdiy7

Who’s in to build some awesome open-source AI projects and win exciting prizes? 👀 Participate in the #ModusHack: 🗓️ 1st Nov - 30th Nov, 2024 🏆 Upto $10k USD ✍️ Build with @hypermodeinc and write about it on @hashnode 🔗 Register now at: hshno.de/ModusHack

🔴 Live Now! Join the HyperMode team and @HaimantikaM on a livestream to learn all about working with Data and AI models → hshno.de/lpzX6SJ

New to DevOps? Learn how to containerize a full MERN stack app with Docker Compose! @praveshstwt in this latest article covered how to: ➡️ Containerize React, Node.js/Express, and MongoDB ➡️ Create custom networks for seamless container communication 🔗 hshno.de/dlgzNO9