PWV Portfolio Feed

This is the initialization layer for agent-driven deploys. We coined the term AX, or Agent Experience, back in January 2025. 

DX was about making developers productive. AX is about making the agents working for developers productive.

One curl command. Your agent reads the context, installs what it needs, provisions the primitives.

No human in the loop until you want to look at the result.

It's an image-free markdown environment. No hero shots. No nav. No tracking pixels.

Just the exact context an agent needs to bootstrap an environment and ship.

80k GitHub stars! 🌟

(mildly clever) - high school shop class challenge to build a little wheeled vehicle that would propel itself across a table and stop before going off the end. designed one with wingnuts on the axles and little pegs on the wheels so it would stop itself automatically

AI use case: Environment setup

AI can set up dev environments, install dependencies, and configure projects automatically. It gets you from zero to coding in minutes.

We're fuming after hearing Bieber stopped his Coachella set (wknd 2) to check on his agents. 😡

we just released a new NPM package

𝚗𝚙𝚖 𝚒𝚗𝚜𝚝𝚊𝚕𝚕 @𝚜𝚞𝚙𝚊𝚋𝚊𝚜𝚎/𝚜𝚎𝚛𝚟𝚎𝚛

it creates a Supabase client configured for server environments and  handles cookies / auth session automatically (SSR, API routes, edge functions)

but float encoding is a very valid concern and there's a little section about it - i considered base64 encoding the bytes or string-encoding as base10, and vaguely considered a bigdecimal-style encoding or encoding base/exp as ints. i suspect float-strings are kinda nice in that parsing is optimized

yeahh, i'm less focused on the float encoding at this point and more on the question of how the hack indicates which parts of the objects are floats and which aren't - should it be a secret key, something else, etc.

This definitely seems weird. We'll try to repro.

Hey Denys, is there a GitHub issue referencing this bug? Maybe we can toss it on the quality week board we are working on this week.

Guess the feature coming to preview this week, stable next.

the readme covers this point, but to clear up any confusion up front, you could have an implicit understanding that coordinates in geojson are floats and so translate them back and forth. but geojson also supports feature properties, and those properties can have floating-point values. hence hack