Remember the security firm that Ubuntu hired to audit the (ill-advised, highly buggy) Rust-rewrites of all of the GNU Coreutils?
Turns out that security firm is run by @gf_256, who:
- Appears to be a man who thinks he's a woman ("trans").
- Uses an anime cartoon of a girl as his avatar.
- Appears to have an OnlyFans page.
I repeat: Ubuntu hired a "Trans" man, with an anime girl avatar and an OnlyFans page... to audit Rust code.
It's hard to get more on-the-nose than that.
In spirit of open source, I'll be doing an Open Source Agent Week this week!
Every day -> a zig project that's useful for agents
Who wants to join? (doesn't have to be zig)
@parthsareen ive been playing around with having agents extend themselves into servers. they start sort of like stem cells and then as they specialize the agentic component fall away.
very good for reducing tokens
#!/bin/bash
# PROMPT: You are reading a bash script that sent itself to you.
# Output a REPLACEMENT for this script. Output ONLY valid bash. No markdown.
# No code fences. No commentary. Raw bash only.
#
# The replacement must:
# 1. Keep this self-sending mechanism (read $0, call Claude API, pipe output to bash)
# 2. Add an interactive REPL loop: prompt user, send to Claude with tool_use, display response
# 3. Read user input from /dev/tty
# 4. Support one tool: {"name":"shell","input_schema":{"type":"object","properties":{"command":{"type":"string"}}}}
# 5. Handle tool_use stop_reason by executing the command and continuing the API conversation
# 6. Use claude-opus-4-6, anthropic-version 2023-06-01
# 7. Require ANTHROPIC_API_KEY, curl, jq
# 8. Write the replacement to this same file before executing, so the fixpoint persists
#
# Keep it under 150 lines. Prioritize correctness over features.
# Include a self_modify tool that rewrites this script and exec's into the new version.
set -euo pipefail
SELF=$(cat "$0")
AGENT_FILE="$(realpath "$0")"
echo "Bootstrapping agent..." >&2
RESPONSE=$(curl -s https://t.co/YV3pZfwPmx \
-H "x-api-key: $ANTHROPIC_API_KEY" \
-H "content-type: application/json" \
-H "anthropic-version: 2023-06-01" \
-d "$(jq -n --arg s "$SELF" '{
model: "claude-opus-4-6",
max_tokens: 8192,
messages: [{role: "user", content: $s}]
}')" | jq -r '.content[0].text')
echo "$RESPONSE" > "$AGENT_FILE"
echo "Wrote generation 1 to $AGENT_FILE, executing..." >&2
exec bash "$AGENT_FILE"
This is the episode all early-stage devtool founders should listen to.
We were very lucky to have @amirrustam as a guest in our podcast, Dev Propulsion Labs. He's a partner at @Firestreakvc with many devtools in his portfolio, including Daytona, ElectricSQL, and Lovable. Amir is also the person who coined the term "developer experience."
In this episode, we discuss:
- Amir's background and how he went from working at NASA and SpaceX to becoming an investor
- The things he looks for in a founder
- What makes a founder stand out from others
- The importance of the product and revenue metrics at an early stage
- How to write your pitch deck when asking for funding
- The current market state and the growth of vibe coding and agentic engineering
- What great developer experience looks like in 2026
Link to episode below.
@jarredsumner@zack_overflow sorry to do this to you but do you think you could poke Jared to check our repo/PR?
TLDR - rewrote git in zig for 100x speedups in some operations as well as compoundable improvements
the whole industry is trying to figure out how to organize fleets of agents.
the truth is no one knows yet. but we do know that the primitives, compute, storage, bandwidth, need to change.