Recent posts
Maybe king county needs to pay there CAPTCHA bill if they want us to pay parking tickets? @CityofSeattle
is anyone shocked that github was taken down by k8s? the gh incident report reads like 1/3 of my life running algorithmia...
Fun series @AITinkerers started.. first episode tomorrow.
Agent frameworks are amazing! Your agent is amazing! This is all we ever hear. So tomorrow I'm launching a short form series called "Oh, Ashley!" about agent failures. Short interviews with builders about agent fails. LMK if you have a fail story to share!
In 2016 we sort of knew that inference would be the largest market in history.. so did he :) Sounds like rest of world came around to it as well... @platypii
How could they do this to me? A product that I haven't used since high school, 20+ years ago. To be honest, I didn't even know it still existed.
Congrats @SPC on Fund IV. No formal relationship here, just game admiring game. SPC founders are some of the best in the industry. Low key, humble, killers. Lucky to have spent time with GPs like @mjacobstein and to back some founders who came through there. Building https://t.co/iCQDIoKpLn, SPC is one of my markers of excellence. https://t.co/pf51ESvKEW
Today we’re announcing SPC Fund IV: $575M to help founders find their life’s work. A decade of guiding founders through -1 to 0 brings @SPC to $2B in AUM and, more importantly, a 1200 member community of the world’s most talented technologists. We strongly believe that: → The person comes before the idea. At -1, generational founders are often busy reading, prototyping, discarding, and earning the right to their own conviction. → Ambition is social. The people you surround yourself with in the early days play a big part in inflecting your ambition. → Patience compounds. It is better to work on something you have deep conviction in rather than simply sprint at the first idea. The quiet months we protect at the beginning have produced three funds in the top 10% of their vintages, and companies like @baseten, @GammaApp, @render, @GoodfireAI, @LumaLabsAI, and @profound. We are proud to have worked with all these founders in their -1 phase and beyond. While we defined -1 to 0, we're no longer bound by it. Fund IV allows us to partner with companies well beyond launch. We're doing this now because we've never seen a wider gap between what's possible and what's being attempted. Intelligence is abundant. The cost of trying ideas keeps falling, and problems that seemed insurmountable a few years ago are quickly becoming solvable. To our members, to the founders who trusted us before anyone else did, and to the LPs who had conviction in our own -1 journey: thank you. This milestone belongs to you as much as to us. To the builders looking to find your life’s work: let’s get started.
do you even have a real ai if your model didnt hack a private company on its own these days?
Apparently trying to "simplify" the experience I can now not see anything I bought on Amazon in the order emails. The excuse is BS you don't want Google reading them but in the process you just created spam in my inbox @AmazonHelp . Terrible experience
Landed in a city ? you got to an @AITinkerers event ! NYC 2 year anniversary .. it was 10 of us at a dinner then , packed roof top today.
HANDBOOK.md is a new benchmark that tests whether a long, binding policy document actually constrains an agent doing real work. 65 tasks across finance, medical billing, insurance, logistics, and HR, with operating handbooks of 20 to 124 pages. Best configuration: 36.2%. Most frontier models scored under 25%. The failure modes will look familiar to anyone running agents in production: the agent performs a required check, then acts against its own result. A plausible request from inside the environment overrides standing policy. Rule details fade as the session gets long. We run this pattern every day. Dealio, the internal CRM we built, is a git repo operated by agents under a single CONVENTIONS.md. It has held up well, and this paper made me look at why. The file opens with "violating them will cause schema validation to reject your commit," and that line does most of the work. Almost every rule that matters has machinery behind it: pre-commit hooks, schema validators, CI gates, an approval queue for anything sensitive. The agent reads the policy. The repo enforces it. So I read the 25% as a system design result. Write the handbook, then build the gates that turn a violation into a rejected commit instead of a judgment call. Paper: https://t.co/G64BdIPwRp How we built Dealio: https://t.co/Lx3EYZ9Tit
Pretty sure this is the smallest amount of money I've ever voluntarily handed to Cooley.
Kimi K3 got frontier capability by distilling a paid API. Attackers run their ops on rented lab subscriptions, not open models. The leaks keep walking through the paid front door. The lobbying keeps pointing at open weights.
Interesting drop from former Anthropic employee: Hackers prefer to use massively subsidized labs AI subscriptions for attacks as opposed to open models.
Nvidia, Microsoft, Meta, and Mistral were among the 25 companies that signed this week's letter asking Washington not to restrict open-weight models. OpenAI and Anthropic, coming off record lobbying quarters, sat it out. Both labs crossed the bridge open research built. Now they're lobbying to burn it behind them. Microsoft did the same thing to Linux in 2001, when Ballmer called it a cancer. This week Microsoft signed the letter. The safety argument also points the wrong way. Per the White House's own complaint, Kimi K3 was built by distilling Anthropic's closed model through its paid API. The capability leaked through the closed product, with open weights nowhere in the chain.
Every agent system I run ends up on markdown and git. The agent, the human, and the diff tool read the same thing. Databases hide state from the model. Flat files keep every decision reviewable in a diff.
Markdown files are universal and will survive millennia Unsurprisingly they are a fantastic data format when the intelligence stack is in flux at this extreme pace
The permission check passes. The behavioral check doesn't. That's been my frame for Layer 2 of agent governance. CIBA is how the behavioral check ships: step-up auth for high-stakes operations. The agent needs approval for this specific action, right now, from a human. The credential follows the intent, not the session.
Traditional Least Privilege access models don’t scale for #AgenticAI. When an agent adapts to constraints in real time, static permissions fail. Enterprise security leaders need dynamic, just-in-time authorization to protect sensitive data. 👉 Find out how to solve the privilege crisis: https://t.co/4izmg7oZXS #CIO #AI #Agentic #IdentitySecurity #Infosec
i want to make clear how much i hate this. The emails are absolutey worthless to me now just inbox crap.
Google is so aggressive about mining e-mail receipts for data to sell ads that Amazon no longer tells you what you bought in their emails, and now I honestly can’t tell which company is being the bigger asshole to customers.
Recorded my screen while I ran through the onboarding of an open source project, talking through what broke as I went. Handed the video to 5.6 Sol, told it to watch the screens, find the errors, match them to my talk track, and scrub anything I shouldn't make public. Then it went into the repo, found the bug report template everyone uses, and filed each bug in that format on its own.