PWV Portfolio Feed

Format-on-save is now disabled by default, except for languages with official formatters.

For existing users, this means their custom configurations will stay, but any values that were previously "default" will be updated.

We've moved all the key agent-related settings to the settings editor. Configure LLM providers, external agents, and MCP servers directly from the Settings UI.

We now have a setting for rendering the current-line git blame in the status bar instead of inline at the cursor. 

Thanks Koshkaj!

None of this needed a smarter model. A 2018 XGBoost and a 2025 one score about the same.

What never scaled was the engineer running 20 feature loops a week. The agent runs 60 overnight for pocket change, and trying things was most of the job anyway.

it didn't get there by brute force. Nobody told it crystals are periodic.
It worked out that raw atom-to-atom distances misread the chemistry across a cell boundary, then rebuilt them as metal-to-oxygen nearest neighbors. 

677 features by the end. 😳

The headline run was a materials-science task. Predict formation energy and bandgap of a transparent conductor from its crystal structure.

It landed 1st of 685. OOF score 0.04853 against a 0.05589 gold line. The humans who won it originally spent weeks.

Sixty cycles later, across four MLE-bench datasets at once, it had two golds and three of four finishes above the Kaggle median.

No human in the loop the whole run. One NVIDIA L40 on @CoreWeave and a few dollars.

Tabular ML didn't die. It was just waiting for agents. 

We rented one GPU for the price of a coffee and asked an agent to top a Kaggle leaderboard on its own. 

It came back with two gold medals. Here's the run 👇

62 apps shipped at Hot AR Summer and counting. 🚀

Builders are turning out some seriously creative AR experiences. Browse the showcase and see what you could add to it! ✨

the options i see look like running bitwarden or hoping that proton doesn't enshittify

it has been fantastic, one of my favorite pieces of software. but they raised way too much money, the quality is going down, and they're doing dumb shit like putting logos on race cars

my bet: 1password will be unusable in 3 years

You can restrict deployments to approved sources: only GitHub orgs you allowlist can ship, and it's a hard boundary, even for admins

Personal repos, CLI deploys, Docker images, and templates are all blocked, official database templates can still be deployed

Restrict TCP proxy does the same for raw TCP: non-admins can't create public TCP proxies, so there's no accidentally exposing your database to the internet 

Neither policy touches custom domains or private networking between services, and admins keep full access

Restrict generate domain stops non-admins from generating public *.railway.app domains, so internal services stay internal

• Non-admins see a banner explaining the restriction
• API requests are rejected
• Auto-generation is skipped for templates and new environments