panphora

@panphora.bsky.social

259 Followers 645 Following

malleable web: https://hyperclay.com

> Thinking depth had already dropped ~67% by late February We landed two changes in Feb that would have impacted this. We evaluated both carefully: 1/ Opus 4.6 launch → adaptive thinking default (Feb 9) Opus 4.6 supports adaptive thinking, which is different from thinking budgets that we used to support. In this mode, the model decides how long to think for, which tends to work better than fixed thinking budgets across the board. `CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING` to opt out. 2/ Medium effort (85) default on Opus 4.6 (Mar 3) We found that effort=85 was a sweet spot on the intelligence-latency/cost curve for most users, improving token efficiency while reducing latency. On of our product principles is to avoid changing settings on users' behalf, and ideally we would have set effort=85 from the start. We felt this was an important setting to change, so our approach was to: 1. Roll it out with a dialog so users are aware of the change and have a chance to opt out 2. Show the effort the first few times you opened Claude Code, so it wasn't surprising.
location ~* \.(html|htmlclay)$ { root /var/www/hyperclay; default_type text/html; add_header Cache-Control "no-cache"; add_header X-Served-By "nginx-static" always; add_header Access-Control-Allow-Origin * always; try_files ${try_static_path}$uri @app; }
Hi, I'm a solo developer working on Hyperclay as often as I can, usually about 30 hours a week. I've been doing this for the past 1,400 days. It's not anywhere near complete, but it's close enough that I can show what I have so far. Before releasing, I wanted to make sure the developer flow and user features were good enough that I'd be comfortable using them myself, every day. We're finally at that point. Long term the vision is single HTML file → app you can charge money for and release upgrades for and brand every screen your users see and give your users features like custom domains. Right now we have single HTML file → app. We're making significant progress towards the other stuff, but it's not quite a seamless experience for your users yet (they still interact quite a bit with Hyperclay) and you can't charge money for your apps yet.
Hyperclay Local app screenshot
A stick figure requests to open a local HTML file, while a robot humorously suggests it will cache the file permanently.
"ZERO WIDTH SPACE" character (hex 200B)