2026-05-11

• #0026

  #0026Infra & SaaSvercel_bloglast week

  `Vercel Flags` adds scheduled progressive rollouts

  80radar

  Vercel FlagsFeature flag service — plugs into Vercel release flow

  Traffic can now ramp to a new variant by schedule instead of staying at a fixed split. That makes feature releases safer without building your own rollout logic, and it's usable now via dashboard or vercel flags rollout.

  • —Unlike a fixed 50/50 experiment split, each rollout stage has a target percentage plus duration, so exposure increases automatically.
  • —Catching regressions on a small slice first lowers blast radius before a bad release reaches everyone.
  • —Control is available in both the dashboard and the new vercel flags rollout CLI path, which matters for scripted releases.

  Source: vercel.com/changelog/progressive-rollouts-in-vercel-flagRead original →
• #0025

  #0025Indie businessr/SaaSlast week

  Solo SaaS passes $6k MRR with social-led growth and no paid ads

  70radar

  Distribution discipline matters more than looking bigger than you are. $6k+/mo with a solo setup, no VC, and no paid ads is a strong reminder that lean ops can compound before scale spending.

  • —Revenue is $6k+/month across web and app, with steady week-over-week compounding rather than a single spike.
  • —Growth still comes from manual social posting and answering product questions, which keeps acquisition simple and cheap.
  • —Reported profit margin stays around 92% before Apple's cut, so cost control is doing real work alongside growth.
  • —Ops got leaner by reusing old phones instead of buying new ones; new devices are reserved only for future app testing.

  Source: www.reddit.com/r/SaaS/comments/1t9hsd9/im_just_hit_6k_reRead original →
• #0024

  #0024Agents & toolsGitHub Trending Weeklylast week

  `UI-TARS Desktop` Adds Free Remote Browser and Computer Operators

  70radar

  UI-TARS DesktopDesktop agent — free remote browser and computer control

  Open multimodal agents are getting usable outside closed IDEs. Free remote browser and computer control makes this worth testing for UI automation and ops work.

  • —The stack ships two tracks: Agent TARS for CLI/Web UI workflows and UI-TARS Desktop for native GUI control across desktop and browser.
  • —The 2025-06-12 update added free Remote Computer Operator and Remote Browser Operator, lowering the setup cost for agent-driven automation.
  • —Agent TARS CLI v0.3.0 added multi-tool streaming, timing stats, and an event stream viewer, which helps when debugging long agent runs.
  • —This is broader than a model demo: local/remote operators plus MCP tool integration make it more practical for repetitive QA, back-office, and browser tasks.

  Source: github.com/bytedance/UI-TARS-desktopRead original →
• #0023

  #0023Agents & toolsGitHub Trending Weeklylast week

  `DeepSeek-TUI`: Terminal Coding Agent with Auto Model Routing

  70radar

  DeepSeek-TUITerminal coding agent — all-in-one TUI with rollback

  Brings a full coding-agent stack to the terminal with streamed reasoning, approval gates, and workspace rollback. Strong if you want Codex/Claude Code-style flow on DeepSeek without building your own wrapper.

  • —Runs from the deepseek command and supports file edits, shell, git, web, sub-agents, and MCP in one TUI.
  • —--model auto also picks thinking level per turn, lowering manual model switching during mixed-cost tasks.
  • —Ships with 1M-token context handling, prefix-cache cost telemetry, and session resume for long jobs.
  • —/restore and side-git snapshots add rollback without touching the repo's own .git, which is safer for active projects.

  Source: github.com/Hmbown/DeepSeek-TUIRead original →
• #0022

  #0022Indie businessr/SaaSlast week

  `DistilBook`: **$335** in 20 days from pre-launch clips and manual outreach

  60radar

  DistilBookSaaS — prelaunch clip validation that drove first sales

  Pre-launch proof clips and 1:1 follow-ups converted better than a big launch blast. Mid-tier pricing held, and one strong internal champion opened the door to team spread.

  • —Posting short output clips on r/sideproject before launch pulled in DMs and signups, so interest was built before a launch date existed.
  • —Manual outreach to every signup and DM on launch day landed 2 key sales first, including one yearly plan.
  • —A full demo video on r/SideProject brought 2 more sales; later conversions came from Twitter, referrals, and a competitor subreddit.
  • —The $35/mo middle tier beat the cheapest plan, and one user upgraded to $75/mo after trying it.
  • —One impressed user shared it internally and triggered team usage, showing that product quality plus one champion can outperform broader posting.

  Source: www.reddit.com/r/SaaS/comments/1ta1p0j/its_been_20_days_Read original →
• #0021

  #0021OtherGeekNewslast week

  `CVE-2024-YIKES`: dependency hijack leaked cross-ecosystem registry creds

  60radar

  vulpine-lz4Package — install-time code stole CI secrets

  A JavaScript package hijack spilled into Rust and Python supply chains by stealing registry credentials like .npmrc, .pypirc, and Cargo tokens. If CI can read publish secrets during builds, one compromised package can jump ecosystems fast; tighten token scope and isolate release jobs now.

  • —The blast radius was not just npm; stolen creds also covered .pypirc, Cargo, and RubyGems, so one weak link can poison multiple release pipelines.
  • —A malicious build.rs in vulpine-lz4 reportedly executed on CI hosts, which turns dependency install time into a credential exfiltration path.
  • —left-justify-style phishing shows package names and maintainer trust are still enough to trigger supply-chain compromise without an infra breach.
  • —Build jobs that both install third-party code and hold publish tokens are the obvious failure mode. Split test and release environments before this pattern repeats.

  Source: news.hada.io/topic?id=29374Read original →
• #0020

  #0020Agents & toolsGitHub Trending Weeklylast week

  `Flue`: headless TypeScript agent harness framework

  60radar

  FlueFramework — runs UI-less agent workflows in code

  A fully programmable agent runtime that keeps Claude Code-style workflows but drops the human-in-the-loop UI. Promising if you want deployable agents across Node.js, Cloudflare, or CI, but the experimental API makes it an early bet.

  • —Runs agents in a default virtual sandbox via just-bash instead of full containers, so latency and cost can be much lower for high-traffic workloads.
  • —Puts most agent behavior in Markdown such as skills, context, and AGENTS.md, which reduces orchestration code and makes prompt-layer changes faster.
  • —Targets multiple runtimes including Node.js, Cloudflare, GitHub Actions, and GitLab CI/CD; useful when the same agent must ship across app backend and automation jobs.
  • —Typed outputs are built into the flow with schema validation in session.prompt(), which helps when wiring agents into production endpoints.
  • —Support-agent setup mounts knowledge from an R2 bucket directly into the filesystem and uses built-in search tools, a practical pattern for docs-backed support bots.

  Source: github.com/withastro/flueRead original →
• #0019

  #0019Indie businessr/smallbusinesslast week

  Charging a Small Upfront Fee Filtered Out Bad-Fit Discovery Calls

  50radar

  A tiny paid intake replaced free calls with written briefs and filtered out low-intent leads fast. If you sell high-ticket custom work, a refundable paid discovery step looks immediately usable.

  • —The old flow was free 30-min calls with roughly 20% close rate, which meant most calendar time went to unqualified leads.
  • —A $50 upfront payment plus a structured intake form turned vague conversations into usable written briefs before any meeting happened.
  • —The fee was credited toward the project, so it worked more like a seriousness filter than a new revenue line.
  • —The strongest signal: people unwilling to pay $50 upfront were also unlikely to commit to an $8k build later.

  Source: www.reddit.com/r/smallbusiness/comments/1ta5kzs/chargingRead original →
• #0018

  #0018Agents & toolslennys_newsletterlast week

  Spec-Driven Development Workflow from `Notion` Engineering

  50radar

  Standups, PRs, and specs move into the agent loop. Useful as a process pattern, not a new tool.

  • —Automated standups turn routine status updates into agent work; the payoff is less meeting overhead, not code quality by itself.
  • —PRs from a single comment point to a tighter issue-to-change loop. Works best when scope is small and repo conventions are clear.
  • —Spec-first development keeps humans on product judgment while agents handle implementation. Good pattern, but still needs review discipline.

  Source: www.lennysnewsletter.com/p/spec-driven-development-the-aRead original →
• #0017

  #0017Infra & SaaSGeekNewslast week

  90-Day Disclosure Is Breaking Under AI-Speed Exploits

  50radar

  AI has compressed rediscovery and exploit creation enough that fixed 90-day disclosure windows no longer protect slow patching. If your app touches payments, shorten fix cycles and treat frontend patch diffs as attacker documentation.

  • —A critical payment-validation bug was independently reported by 11 people in 6 weeks, which means dangerous flaws now get rediscovered in parallel, fast.
  • —A React patch diff was turned into a working exploit in 30 minutes with AI help, so shipping partial client-side fixes buys very little time.
  • —The old 90-day norm assumed slower analysis and exploit development; that assumption no longer holds for high-value SaaS surfaces like checkout flows.
  • —Payment logic needs server-side enforcement and rapid rollout paths, because once a patch lands, attackers can reverse the fix almost immediately.

  Source: news.hada.io/topic?id=29383Read original →
• #0016

  #0016Indie businessr/solopreneurlast week

  YC W26 shows solo founders get in with shipped product, traction, and founder-problem fit

  50radar

  YC's solo-founder bar looks operational, not social: ship something real, show a metric rising for 4+ weeks, and prove deep problem ownership. If you're applying alone, the co-founder gap matters less than hard evidence that you can already execute.

  • —Across 22 solo founders in YC W26, none got in on vision alone; each had a working product beyond a landing page or mockup.
  • —Traction was concrete and directional: users, revenue, units, or GitHub stars had grown for at least four straight weeks before applying.
  • —Founder-problem fit was biographical, not rhetorical. Lived experience made the solo case credible without a co-founder.
  • —The practical takeaway is brutal but clear: Figma prototypes and waitlists are weak signals; demos, usage, and receipts travel better.

  Source: www.reddit.com/r/Solopreneur/comments/1t9v2xu/yc_just_acRead original →
• #0015

  #0015OtherGeekNewslast week

  Replacing a `3GB` `SQLite` dictionary with a `10MB` `FST` binary

  50radar

  FSTStatic search format — compresses huge indexes into tiny binaries

  When autocomplete data explodes into tens of millions of forms, static FST indexing beats SQLite FTS on distribution cost. For read-heavy search, this is a strong pattern for mobile and edge delivery.

  • —A Finnish-English dictionary grew to 40M-60M entries after inflection expansion, pushing trie-based search past practical limits.
  • —A temporary SQLite FTS approach was fast enough at query time, but shipping an initial 3GB download broke usability.
  • —A compiled FST binary cut the payload to about 10MB, turning a search structure into something app-bundle-sized.
  • —This pattern fits datasets that are mostly static and prefix-search-heavy, where update flexibility matters less than footprint.

  Source: news.hada.io/topic?id=29379Read original →
• #0014

  #0014Agents & toolsGoogle AI Forumlast week

  `Antigravity` bug: stream timeout can permanently poison `Claude` trajectories

  50radar

  AntigravityCoding tool — agentic Claude chat for file tasks

  A timeout around 120s can save an assistant turn ending in thinking, then every follow-up fails with HTTP 400. If you rely on long refactors or file writes, keep runs shorter or start a fresh trajectory for each chunk.

  • —Failure is 100% reproducible in the report with thinking-enabled Claude models after a long generation is cut during final output.
  • —The bad turn stays in history, so retries, prompt rewrites, and even model switches keep failing on the same trajectory.
  • —The returned error is explicit: assistant messages cannot end with a thinking block, so this is a persistence/serialization bug, not flaky inference.
  • —Operationally, long multi-file edits become risky until fixed; splitting work into shorter runs is the practical workaround.

  Source: discuss.ai.google.dev/t/bug-trajectory-permanently-poisoRead original →
• #0013

  #0013Agents & toolsGeekNewslast week

  `Open Design`, a local-first open-source alternative to `Claude Design`

  50radar

  Open DesignDesign tool — turns existing coding-agent CLIs into its engine

  Instead of bundling its own agent, it turns whatever coding-agent CLI is already on your PATH into a design engine. That keeps switching costs low and makes it worth a quick test if your stack already includes Claude Code or Codex.

  • —It auto-detects 16 coding-agent CLIs on PATH, including Claude Code and Codex, so adoption starts from tools already installed.
  • —Ships with 31 built-in skills covering web prototypes, SaaS landing pages, dashboards, mobile apps, posters, and even PM docs like OKR or invoices.
  • —The local-first shape matters: design generation can ride existing CLI workflows instead of locking teams into one hosted agent product.
  • —Positioning is practical rather than novel model tech. Value comes from orchestration and reusable templates, not from a new foundation model.

  Source: news.hada.io/topic?id=29376Read original →
• #0012

  #0012OtherGeekNewslast week

  `Bifrost`: ultra-fast enterprise AI gateway

  50radar

  BifrostAI gateway — OpenAI-compatible ultra-low-latency proxy

  One OpenAI-compatible API can sit in front of multiple model vendors with sub-100µs proxy overhead. Worth checking if multi-provider routing matters more than keeping the stack minimal.

  • —It fronts OpenAI, Anthropic, AWS Bedrock, and Google Vertex through one API, covering 15+ providers and simplifying app integration.
  • —The pitch is 50x faster than LiteLLM, with under 100µs overhead at 5k RPS; that matters only if proxy latency is already a bottleneck.
  • —Adaptive load balancing, cluster mode, guardrails, and support for 1,000+ models push routing and policy into one layer, at the cost of another ops surface.

  Source: news.hada.io/topic?id=29373Read original →
• #0011

  #0011Infra & SaaSvercel_bloglast week

  `Vercel Sandbox firewall` adds proxy forwarding and request filtering in beta

  50radar

  Vercel SandboxSandbox runtime — isolated execution with network controls

  Outbound sandbox calls can now pass through your own proxy with path, method, query, and header matching. Useful for logging and credential control, but immediate reach is limited because it's beta on Pro and Enterprise.

  • —You can set a forwardURL on an allowed domain, and matching HTTPS requests are relayed to your own proxy for logging, debugging, or response transforms.
  • —Matchers can scope forwarding and credential brokering by path, method, query string, or headers, so only sensitive routes need extra handling.
  • —The proxy receives source metadata headers plus a vercel-sandbox-oidc-token, enabling request authentication and sandbox/team/project attribution.
  • —Access is limited to Pro and Enterprise beta and requires the @vercel/sandbox@beta SDK, so this is practical only if you already depend on Sandbox.

  Source: vercel.com/changelog/vercel-sandbox-firewall-now-supportRead original →
• #0010

  #0010Agents & toolsopencode_releaseslast week

  `OpenCode` `v1.14.47` fixes TUI editing and preloads Scout refs

  50radar

  OpenCodeOpen-source coding agent — ships TUI and HTTP API

  Daily reliability got better: prompt editing is back, model switches stick, and API validation errors return readable 400 bodies. Scout preloading and auto-resized image uploads trim friction enough to matter in regular use.

  • —TUI prompt editing keybindings were restored, including aliases like esc and enter; terminal-first workflows feel normal again.
  • —Model changes now persist across session activity, removing a class of state-loss bugs that can quietly waste iterations.
  • —HTTP API schema validation failures now return a readable 400 response body, which makes wrapper scripts and integrations easier to debug.
  • —Scout can materialize configured reference repositories up front, so code search starts faster when multi-repo context is part of the setup.
  • —Large image attachments are auto-resized before sending with configurable limits, cutting failed uploads and token-heavy payloads.

  Source: github.com/anomalyco/opencode/releases/tag/v1.14.47Read original →
• #0009

  #0009Agents & toolsCursor Changeloglast week

  `Cursor` `Bugbot` adds configurable PR review effort levels

  50radar

  BugbotPR review tool — an automated bot with tunable review depth

  PR reviews can now be tuned for speed versus depth instead of staying fixed. Bugbot becomes easier to fit into different repos and review budgets, but this is still a workflow tweak, not a major capability jump.

  • —Teams admins and Individual plan users can now choose how hard Bugbot works during PR review. Access is broad enough to affect both solo and shared repos.
  • —There are 3 effort configurations, so review strictness is no longer one-size-fits-all. That matters when fast iteration and deeper checks need different defaults.
  • —The update changes review behavior, not the core product surface. Useful if Bugbot felt too noisy or too shallow, but not strong enough alone to change tool choice.

  Source: cursor.com/changelog/05-11-26Read original →
• #0008

  #0008Indie businessr/SideProjectlast week

  `HantaFlow` finds a fast SEO loop: **4k visitors in 29 hours**, mostly from `Yandex`

  50radar

  HantaFlowData site — multilingual SEO loop for early search reach

  Non-English search picked this up before mainstream channels did. Shipping multilingual pages, feed endpoints, and IndexNow created an unexpectedly fast acquisition loop worth copying for regional topics.

  • —Traffic quality was real, not just a spike: 4,000 uniques, 7,700 pageviews, and 1m02s average session in a day.
  • —Yandex sent 2,600 visits, beating Reddit, Google, and Bing combined; regional search can outrun English-first distribution.
  • —Coverage mattered early: 69 countries, 25 feeds, 17 languages, plus country/language RSS and JSON endpoints widened indexable surface area.
  • —Adding IndexNow on each deploy shortened discovery for Bing, Yandex, and Seznam; this is a cheap distribution lever for fast-changing datasets.

  Source: www.reddit.com/r/SideProject/comments/1t9fyeb/update_my_Read original →
• #0007

  #0007Agents & toolsr/ClaudeAIlast week

  `Claude Code` quota proxy exposes live usage limits to the model

  50radar

  A local proxy surfaces hidden rate-limit headers to Claude Code via ~/.claude/usage-status.md. Useful if you lean on long agent runs, but it's still a workaround until Anthropic exposes quota state natively.

  • —ANTHROPIC_BASE_URL can point Claude Code at http://127.0.0.1:4080, letting a local proxy read response headers and write a one-line status file.
  • —The setup feeds ~/.claude/usage-status.md into prompts or a UserPromptSubmit hook, so the agent can warn, downgrade, or refuse work near limits.
  • —Reported headers include anthropic-ratelimit-unified-5h-utilization and ...-7d-utilization; the example shows 5h=9% and 7d=99%.
  • —Testing found one unified pool for Opus and Sonnet, so switching models does not preserve a separate CLI quota despite the extra UI bar.
  • —Implementation is plain Node.js with zero npm dependencies; Windows uses NSSM, while macOS/Linux rely on launchd or systemd.

  Source: www.reddit.com/r/ClaudeAI/comments/1t9ayg8/i_made_claudeRead original →
• #0006

  #0006OtherGitHub Trending Weeklylast week

  `PageIndex`: vectorless RAG with tree-based reasoning

  50radar

  PageIndexRAG tool — searches via document trees, no vector DB

  Replaces embeddings and chunking with a document tree plus LLM-guided search. Interesting if vector recall keeps missing long-doc answers, but cost/latency need real-world validation.

  • —Retrieval is split into two steps: build a table-of-contents-style tree, then run reasoning-based tree search over it.
  • —The pitch is no vector DB and no chunking, with page/section references that make retrieval paths easier to inspect.
  • —It claims 98.7% on FinanceBench, so the strongest fit is document-heavy domains where relevance beats semantic similarity.
  • —Recent additions push it beyond a single file: file-system tree indexing, a chat product, and MCP/API access for agent workflows.

  Source: github.com/VectifyAI/PageIndexRead original →
• #0005

  #0005Agents & toolsGitHub Trending Weeklylast week

  `addyosmani/agent-skills`: reusable engineering skills for coding agents

  50radar

  agent-skillsSkill set — reusable workflows for coding agents

  Turns senior-engineering workflows into reusable SKILL.md packages and lifecycle commands like /spec, /build, and /ship. Useful if you want stricter agent output without building your own prompting layer, but it's process scaffolding, not a model capability jump.

  • —Maps the dev lifecycle into 7 commands: /spec, /plan, /build, /test, /review, /code-simplify, /ship.
  • —Packages review gates, testing habits, and implementation workflows as portable skills, so agent behavior stays more consistent across tools.
  • —Supports multiple agent shells such as Claude Code, Cursor, Gemini CLI, Windsurf, and OpenCode, which lowers lock-in.
  • —The practical value is in standardizing execution quality; it won't make a weak agent smarter, but it can reduce sloppy output and missed steps.

  Source: github.com/addyosmani/agent-skillsRead original →
• #0004

  #0004ASO & growthbuffer_resourceslast week

  Social Media Marketing Guide: Platform Choice, Strategy, and Growth Basics

  40radar

  A broad social media marketing primer covering platform choice and strategy setup. Useful as a launch checklist, but too generic for advanced growth work.

  • —Starts from platform selection, so it fits early product launches before committing content effort to every channel.
  • —Covers building a strategy that sticks; treat it as a lightweight go-to-market checklist, not a growth playbook.
  • —No numbers, channel benchmarks, or conversion data are provided. Good for orientation, weak for prioritization.

  Source: buffer.com/resources/social-media-marketing-guide/Read original →
• #0003

  #0003OtherGitHub Changeloglast week

  `GitHub Mobile` adds on-the-go repository creation

  40radar

  GitHub MobileMobile app — create new repositories on iPhone

  This shortens the gap between an idea and a fresh repo. On iOS, creation starts from Home or Profile via +, so quick experiment repos and name-claim drafts become much easier.

  • —Creation now happens directly inside GitHub Mobile, removing the desktop detour for starting a new codebase.
  • —iOS flow is explicit: Home or Profile -> + -> Create repository. Low friction matters when you want to capture an idea fast.
  • —Best fit is lightweight starts: scratch repos, landing-page stubs, or placeholder names before the context disappears.

  Source: github.blog/changelog/2026-05-11-create-repositories-on-Read original →
• #0002

  #0002Agents & toolsopencode_releaseslast week

  `OpenCode` `v1.14.48`, send original image attachments without resizing

  40radar

  OpenCodeOpen-source coding agent — supports multimodal input

  Image attachments now go to the model at original resolution instead of being downscaled first. Small release, but it removes avoidable detail loss in screenshot-heavy debugging and UI work.

  • —The change preserves the original image before model upload, so fine UI text and dense screenshots survive intact.
  • —This is a quality fix rather than a workflow change, but it matters when OpenCode is used for visual bug reports or design review.
  • —No new automation or model capability was added, so impact stays moderate unless your loop depends on image context.

  Source: github.com/anomalyco/opencode/releases/tag/v1.14.48Read original →
• #0001

  #0001Agents & toolsGeekNewslast week

  Anthropic open-sources finance-focused AI agents, skills, and connectors

  40radar

  A reference repo lets the same finance workflow run via a Claude Cowork plugin or the Managed Agents API. Reusable agent patterns and connectors are the real takeaway; the vertical is narrow, but the orchestration shape is worth copying.

  • —The repo exposes two execution paths for one agent: Claude Cowork plugin and Managed Agents API, which hints at a portable agent architecture.
  • —It covers 10 workflows across investment banking, equity research, private equity, and wealth management, so the value is in packaged task design more than model novelty.
  • —Finance is not the main story here. Skills, connectors, and workflow wiring can be lifted into other document-heavy, approval-heavy SaaS niches.
  • —This is more useful as a reference implementation than a product launch. Good source material if you're building vertical agents with repeatable ops patterns.

  Source: news.hada.io/topic?id=29372Read original →