Claude Sonnet 4.6 is the backbone of our entire platform, Humans.Team. Over 85 development sessions, Claude Code (powered by Sonnet) built 90% of our Next.js application — from Supabase database architecture and Row Level Security policies to AI journal integration, real-time notifications, PWA offline support, and a bilingual FR/EN system across 30+ pages.
What sets Sonnet 4.6 apart is its ability to hold deep context across long sessions. It remembers architectural decisions from hours ago, understands our codebase patterns, and writes production-ready TypeScript that rarely needs fixing. The reasoning is exceptional — it debugs complex issues by tracing through multiple files and connections.
We also use Claude Desktop daily for content strategy, press releases, blog articles, and bilingual copywriting. The nuance in both French and English is remarkable.
Flowtica Scribe
Hi everyone!
Claude can write the code, run it, open the app, click through the interface, and check what actually happened, all from the CLI.
You can enable computer-use from /mcp, grant macOS Accessibility and Screen Recording, approve apps per session, and stop everything instantly with Esc at any time.
Research preview for macOS on Pro and Max plans for now.
This is a game-changer for developer workflows. We use Claude Code heavily for building our PropTech platform and the biggest friction has always been switching between the CLI and GUI tools for testing. Being able to have Claude debug visual issues and automate GUI-only tools directly from the terminal is going to save so much context-switching time. Question — does the screen observation work well with map-heavy interfaces? A lot of our work involves geospatial UIs (Mapbox, zoning overlays) and I'm curious how well it handles those kinds of visually complex layouts.
The GUI-only tools use case is what gets me. So much internal tooling in companies never gets API access - it lives in dashboards, legacy web apps, Figma. This bridges that last mile without needing to build integrations first. Curious how it handles multi-step flows where intermediate state matters - like filling a form where field 2 options depend on field 1.