Hashnode @hashnode

Hashnode now has an MCP server. claude mcp add --transport http hashnode-mcp mcp.hashnode.com/mcp Claude, ChatGPT, or Codex can now read and write your Hashnode posts directly. Requires a Pro plan. hashnode.com/changelog/2026…

✅ We're back online! The issue has been resolved, and service is restored. Thank you for your patience, and we apologize for the inconvenience.

Hashnode @hashnode

a month ago

⚠️ We're currently experiencing technical issues. Our team is working to restore service as soon as possible. We apologize for the inconvenience and appreciate your patience. We'll keep you updated!

3 0 7 5K 0

⚠️ We're currently experiencing technical issues. Our team is working to restore service as soon as possible. We apologize for the inconvenience and appreciate your patience. We'll keep you updated!

open-source AgentMail alternative on Cloudflare Workers. dearagent.sh

Hashnode is back up. Thanks for your patience while we sorted this out.

We're aware Hashnode is currently down. Our team is investigating now. Sorry for the disruption, updates to follow shortly.

Shipped two things for the AEO toolkit. A ranked list of who else gets cited for the same question as you, and a card showing how much traffic ChatGPT, Perplexity, Gemini, and Claude actually send to your blog. Both on Growth Plan. hashnode.com/changelog/2026…

the ticket is the prompt linear integration just shipped. label an issue and it comes back as a pull request: built in a cloud sandbox, QA'd in a real browser, posted back on the ticket i didn't prompt it and i didn't open localhost, i just put a label on a ticket

Introducing Darkshift - a software factory we’ve been using to ship Hashnode + Bug0. > multi harness: claude code, codex, grok build or kimi > BYOK > web, slack or linear > 100% cloud dev > QA-first with evidence-backed PRs > Multiplayer darkshift.dev

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…

We're back. All Hashnode services are restored and your data is safe. Thanks for your patience.

Hashnode is currently down. We're aware and working on a fix right now. We'll post updates here as soon as we know more.

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-so…

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-c…

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-softwa…

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-softwa…

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-keybo…