Show HN: Auto-continue Claude Fable 5 the second your 5-hour limit lifts https://ift.tt/miNvqK6

Show HN: Auto-continue Claude Fable 5 the second your 5-hour limit lifts https://ift.tt/PXD371k July 4, 2026 at 01:05AM

Show HN: Dockside – I turned unused space around the macOS Dock into a workspace https://ift.tt/eUv4Vl8

Show HN: Dockside – I turned unused space around the macOS Dock into a workspace https://ift.tt/nXKj0c4 July 3, 2026 at 11:35PM

Show HN: Piggy – lazy senior dev mode for AI agents (80–94% less code) https://ift.tt/NnjstZG

Show HN: Piggy – lazy senior dev mode for AI agents (80–94% less code) https://ift.tt/bi3PHOK July 3, 2026 at 12:59AM

Show HN: A provider-agnostic agent loop built on ports and adapters https://ift.tt/SkjxNKF

Show HN: A provider-agnostic agent loop built on ports and adapters I work on agent infra at Featherless. This is MIT and works with any OpenAI-compatible endpoint, not just ours. I kept rebuilding the same loop: call model, run tools, feed results back, stop. Every framework I tried either owned the UI, owned the control flow, or dragged a dependency tree. So I pulled the loop out and put every piece behind an interface: memory, model, tools, stop condition. The loop depends only on the interfaces. It never writes to a screen. It emits one typed event stream, so a trace is just data, and you render it however you want. The landing page scrubs one run and rebuilds a CLI, a DOM timeline, and raw JSONL from the same stream. One dependency (zod). Same build runs in Node, Bun, Deno, and a browser tab. Every seam is tested in isolation with deterministic doubles, no network. Why not the Vercel AI SDK, pi, or LangGraph: AI SDK owns more of the surface and has been awkward with self-hosted tool calling. pi is a great coding-agent toolkit but it's shaped around being a coding agent and ships a TUI. LangGraph is a heavier graph framework. This is the layer under all of those: the bare loop you'd build any of them on. Happy to be told where the seams are wrong. If anyone finds any problems let me know this field moves at break neck speed so let me know if I am missing anything. https://ift.tt/6hECm2k July 3, 2026 at 12:52AM

Show HN: Inkwell – An RSS reader for e-ink devices https://ift.tt/TCNyu5j

Show HN: Inkwell – An RSS reader for e-ink devices https://ift.tt/DHSyVBX July 2, 2026 at 09:08PM

Show HN: ctx – Search the coding agent history already on your machine https://ift.tt/FGkAil5

Show HN: ctx – Search the coding agent history already on your machine Coding agents don't have long-term memory. But you do have months of full-fidelity agent transcripts stored on your machine. A simple solution that goes a long way: ingest those transcripts and logs into a structured SQLite database, then search them with ranked text match. Everything is fully local and doesn't require anything fancy like a graph database or hosted memory service. This is the idea behind ctx, a Rust CLI that handles the ingestion and searching. We give our agents a skill that tells them to reference past sessions before working in an area. Usually we do this through an "Agent History Research Subagent" whose job is just to prepare a short brief covering any relevant history before the task begins. A real example: sometimes our test suite runs would fail because disk was full on the runner. The correct approach was to run the cleanup runbook, but the root cause of the failure was not clear to the agents, so they would think it was a test regression and go down the wrong rabbit hole debugging. When the agent searched history, it realized this failure had been encountered before and found the right workaround immediately. That got the agent onto the right cleanup path, and later we improved the log output so the same failure would be clearer next time. It's a boring story, but it's real agent productivity. Another nice use case is quickly generating session transcripts for sharing. You can exclude the noisy intermediate messages, so the transcript shows the important parts of the session more cleanly. Try attaching a session transcript to your next PR so your teammate and their agent can review the provenance and prompting behind the change. If you're up for an additional challenge, ask your agent to "exhaustively review all agent history in this repo and find where the SDLC is struggling or isn't agent-native". Using past sessions to recursively improve the agentic SDLC is a loop that we're using a lot today. If you try it out, please let us know what you think! https://ift.tt/XrnplYJ July 2, 2026 at 09:28PM

Show HN: Searchable directory of 22k+ products from worker-owned co-ops https://ift.tt/61wyXHb

Show HN: Searchable directory of 22k+ products from worker-owned co-ops https://ift.tt/v2Aya0R July 2, 2026 at 02:17AM

Show HN: Z-Jail – A 130 KB Linux sandbox-C99 with 7 defense layers and zero deps https://ift.tt/QZ5n6wC

Show HN: Z-Jail – A 130 KB Linux sandbox-C99 with 7 defense layers and zero deps https://ift.tt/QulTK1E July 2, 2026 at 12:48AM

Show HN: QR code renderer in a TrueType font https://ift.tt/GhjbSnx

Show HN: QR code renderer in a TrueType font In the "Libre Barcode Project" discussion yesterday, 1bpp asked: "Is anyone willing to sacrifice their sanity for the sake of implementing a QR renderer as TTF hinting code?" Yes. I had some tokens to burn and was curious... turns out, it's possible. This was put together by a mix of Gemini, GPT, and Claude (depending on which usage limits kept running out). https://qr.jim.sh/ June 28, 2026 at 06:07AM