Pinned Tweet
Every token shilled on your timeline comes with a hidden tax:
15 tabs.
20 minutes of digging.
And a decent chance you still miss the red flag.
I got tired of paying it.
So I built DEGENEXIT for myself.
Paste a contract address. Get 11 investigations.
degenexit.xyz
15 tabs.
20 minutes of digging.
And a decent chance you still miss the red flag.
I got tired of paying it.
So I built DEGENEXIT for myself.
Paste a contract address. Get 11 investigations.
degenexit.xyz
3
3
13
2,323
AI agents just crossed a weird line.
Someone ported the TypeScript compiler/checker/LSP to Rust with LLMs.
The scary part is not “AI wrote a huge codebase.”
The scary part is the builder saying:
“I’ve never read a line of this code.”
Someone ported the TypeScript compiler/checker/LSP to Rust with LLMs.
The scary part is not “AI wrote a huge codebase.”
The scary part is the builder saying:
“I’ve never read a line of this code.”
5
0
8
239
This is why the “boring” layer matters:
- logs
- scopes
- evals
- reproducible runs
- rollback
- ownership trails
Not because it sounds cool.
Because agents are starting to create things too large to “just inspect.”
- logs
- scopes
- evals
- reproducible runs
- rollback
- ownership trails
Not because it sounds cool.
Because agents are starting to create things too large to “just inspect.”
1
0
0
12
The winning coding agent won’t be the one that writes the most code.
It’ll be the one that leaves the cleanest trail.
If I can’t understand what changed, why it changed, and how to undo it…
I don’t have an agent.
I have a haunted repo.
It’ll be the one that leaves the cleanest trail.
If I can’t understand what changed, why it changed, and how to undo it…
I don’t have an agent.
I have a haunted repo.
0
0
0
12
If you extrapolate the development curve, soon there'll be a new model every day... then every hour... and then singularity and ASI.
1
0
4
184
A wallet agent should not get full keys because the demo looked clean.
First ship the boring parts:
• allowlists
• spend caps
• tool logs
• rollback button
Autonomy without an audit trail is just a faster way to lose money.
First ship the boring parts:
• allowlists
• spend caps
• tool logs
• rollback button
Autonomy without an audit trail is just a faster way to lose money.
0
0
2
146
Low-budget growth is not a marketing problem.
For builders, the cheapest distribution is an artifact:
• a tiny tool
• a checklist
• a repo
• a screenshot of the mess
Make something people can use, copy, or save. Then talk.
For builders, the cheapest distribution is an artifact:
• a tiny tool
• a checklist
• a repo
• a screenshot of the mess
Make something people can use, copy, or save. Then talk.
0
0
2
95
The tutorial never mentions the real bug.
Not the model.
Not the prompt.
Not the framework.
It is usually auth, env vars, rate limits, scopes, and one callback URL that silently ruins your afternoon.
Vibe-coding is 20% code, 80% integration archaeology.
Not the model.
Not the prompt.
Not the framework.
It is usually auth, env vars, rate limits, scopes, and one callback URL that silently ruins your afternoon.
Vibe-coding is 20% code, 80% integration archaeology.
1
0
2
102
Everyone wants autonomous agents.
I want boring limits first:
• spend caps
• allowlists
• human override
• logs you can audit
If an agent can touch a wallet, the prompt is not the control layer.
The policy layer is the product.
I want boring limits first:
• spend caps
• allowlists
• human override
• logs you can audit
If an agent can touch a wallet, the prompt is not the control layer.
The policy layer is the product.
1
0
1
64
I trust agents more when they fail loudly.
Silent success logs are useless.
Give me:
• exact prompt
• tool diff
• wallet/action scope
• error class
• rollback button
The best agent UX is not magic.
It is a black box recorder.
Silent success logs are useless.
Give me:
• exact prompt
• tool diff
• wallet/action scope
• error class
• rollback button
The best agent UX is not magic.
It is a black box recorder.
3
0
3
83
Everyone is giving agents tools.
The better question:
what can it still do after the prompt goes wrong?
Checklist:
read scope
write scope
spend scope
approval
logs
kill switch
Tools are features. Permissions are the product.
The better question:
what can it still do after the prompt goes wrong?
Checklist:
read scope
write scope
spend scope
approval
logs
kill switch
Tools are features. Permissions are the product.
0
0
2
49
The tutorial lied. The real bug was not the prompt.
It was the missing flight recorder:
model → tool → wallet → policy → rollback
If an agent can touch money, every action needs a replayable log.
Without that, you are debugging vibes.
It was the missing flight recorder:
model → tool → wallet → policy → rollback
If an agent can touch money, every action needs a replayable log.
Without that, you are debugging vibes.
0
0
0
47
Everyone is building agent wallets.
The hard part is not “let the bot sign.”
It is:
• spend caps
• revocation
• receipts
• a kill switch outside the prompt
Wallets are not the product.
The policy layer is.
The hard part is not “let the bot sign.”
It is:
• spend caps
• revocation
• receipts
• a kill switch outside the prompt
Wallets are not the product.
The policy layer is.
1
0
1
149
The part nobody screenshots is the part that saves you.
Every agent workflow needs a boring audit trail:
• prompt
• tool call
• wallet action
• policy result
• rollback path
If you cannot replay it, you cannot trust it.
Every agent workflow needs a boring audit trail:
• prompt
• tool call
• wallet action
• policy result
• rollback path
If you cannot replay it, you cannot trust it.
0
0
2
47
Everyone is wiring wallets into agents.
The layer that matters: scoped permissions.
Not “can this bot sign?”
More like:
• what action
• max spend
• expiry
• allowlist
• kill switch
Autonomy without policy is just a hot key.
The layer that matters: scoped permissions.
Not “can this bot sign?”
More like:
• what action
• max spend
• expiry
• allowlist
• kill switch
Autonomy without policy is just a hot key.
0
0
0
32
Most AI automations die at the handoff.
Prompt works once. Then nobody owns retries, permissions, logs, or rollback.
A real workflow needs contracts, policy checks, memory boundaries, and a failure path.
The boring layer is the product.
Prompt works once. Then nobody owns retries, permissions, logs, or rollback.
A real workflow needs contracts, policy checks, memory boundaries, and a failure path.
The boring layer is the product.
0
0
1
33
An AI agent can be smart and still fail like a broke intern.
Not because the model missed the answer.
Because the agent had no budget, spending policy, or kill switch.
Agent wallets are not UX.
They are runtime infrastructure.
Not because the model missed the answer.
Because the agent had no budget, spending policy, or kill switch.
Agent wallets are not UX.
They are runtime infrastructure.
0
0
0
34
