Yesterday's Top Launches: 5 Tools from October 6, 2026
Five launches from yesterday range from a Mac screen recorder and an OpenAI shared workspace to a self-hosted email API, a Confluence auditor, and an OpenAPI ecosystem generator, three of which count as developer tools.

Five launches landed yesterday and they have almost nothing in common, which is usually a sign of a good day. A Mac screen recorder, a shared workspace from OpenAI, a self-hosted email API, a Confluence auditor, and a generator that turns one OpenAPI spec into a whole ecosystem. Three of those qualify squarely as new developer tools, and between them they touch a lot of what a small product team actually argues about: how to record a demo, where project context lives, who owns the email layer, whether the wiki is still true, and how much boilerplate an API team should be maintaining by hand.
Smooth Recorder
Screen recordings are the quickest way to explain something and the slowest thing to make look decent. The cursor jerks, interface details vanish at 1080p, and one “um” sends you into an editor. Smooth Recorder tackles this by moving the polish into the recording itself. Zooms follow your clicks automatically, the cursor and camera motion are smoothed, and captions appear as you speak, so the clip is already assembled when you hit stop.
The clever part is transcript-based cutting. Speech is transcribed locally, and the transcript becomes the editing surface: delete a sentence there and it disappears from the video. Fillers get stripped by a single command that tells you how many it removed.
Screenshots come from the same overlay, with 76 wallpapers, keyed annotation tools, and Smart Redact scanning for emails, card numbers, API keys and faces before you share. It’s a native SwiftUI and AppKit app, macOS 15 or later, on-device throughout. Worth knowing: it’s Mac-only, and the $9 early-access price is a lot lower than the $69 it’s slated to hit. For anyone who records walkthroughs weekly, that’s an easy call.
ChatGPT Space
OpenAI’s new shared workspace replaces Library and gives teams one place to keep pages, files, spreadsheets and slides, with ChatGPT, Codex or a dot tagged into the work. Pages stay updated from connected tools, which means a dashboard or launch plan can pull its own changes instead of waiting for someone to remember.
Collaboration is real-time, comments are supported, and you can @mention ChatGPT in a comment to have it act. Permissions are thought through: uploading a file into a page carries that page’s permissions, but linking to an external file does not grant access, and sharing a page never exposes your private chats.
The caveats are worth stating plainly. Mobile is read-only at launch, collaborative slides and spreadsheets are still coming, and it’s gated to Pro, Business and Enterprise. If your team lives in ChatGPT already, the pull is obvious. If it doesn’t, this won’t be the thing that moves you.
opensend.cc
Built by Kamal Panara, this is a self-hosted answer to Resend: your own email platform, delivering through your own AWS SES account, so your domain, contacts and sender reputation stay yours. The REST API is Resend-compatible, which means switching is roughly a two-line change to your base URL, and SMTP is there for anything that expects it.
Templates are React components. Audiences and broadcasts are first-class, and transactional mail and newsletters share one sending pipeline. Webhooks are signed and retried, bounces feed the suppression list automatically, and test-mode keys accept everything without delivering anything, which is exactly what CI needs.
The trade is real: you’re running Docker Compose, Next.js and a self-hosted Convex instance on a server you maintain. In exchange, there’s no per-email billing and no feature gates, Apache-2.0 the whole way. If you’ve been paying per send, the arithmetic gets interesting fast.
WikiFix for Confluence
Confluence drift is one of those problems everyone nods at and nobody fixes, because you can’t read five thousand pages to find the ten that are wrong. WikiFix reads them for you. It looks for pages that contradict each other, duplicate content, and pages whose owner has left, then quotes the conflicting claims side by side so you can pick the right one.
Approval is required for every write, and content fixes revert in a click. That last detail matters more than it sounds. Abandoned pages get reassigned, and findings that aren’t yours can be escalated with an inline comment that @mentions the owner.
There’s also a quiet argument here about AI: Rovo and every copilot answer from the same wiki your team reads, so stale docs get repeated back confidently. The pricing is the fiddly part, billed per user plus credits spent only on new or changed pages, starting with $50 of credits.
Octri.dev
One OpenAPI spec goes in, four things come out: a docs site, SDKs in ten languages, an MCP server, and production monitoring compiled into the SDKs themselves. That last piece is the pitch. When a client library reports its own errors back, integration failures reach you before the support ticket does.
The MCP server is a smart use of the same spec: your exclusion list becomes the agent’s permission list, so Claude or Cursor can call real endpoints instead of hallucinating them from memory. Docs are AI-drafted then edited like a document, and renaming a method propagates everywhere.
The honest caveat is the free tier: one SDK language, 50 endpoints. Real use means Starter at $49 or Growth at $99. The OpenAPI audit tool, which scores your spec against fourteen rules before anyone generates from it, is genuinely useful on its own.
Quick links
Voting on yesterday’s batch hadn’t settled when this went out, so no runaway favorite yet. If I had to guess where the attention lands, it’s between opensend.cc and Octri.dev, since both solve problems developers complain about rather than problems they merely tolerate.