Phil Wee

Javascript developer. AI enthusiast. Aspiring entrepreneur. Formerly @Rivian @PaloAltoNtwks @PlanGrid @Vungle @DisneyInteract @Oracle

[anabology @anabology]

I gave Claude another 18 hours.. and I think this one is the best one yet

Macrohard: Windows XP

I'm blown away

[Firecrawl @firecrawl]

Firecrawl free keyless is here!

Get started searching and scraping the web for free with no API key.

[Dr. Brian Hoeflinger, MD @drhoeflinger]

I’m a retired brain surgeon and I wanna tell you why you feel like life is passing by. I just need one minute to explain this to you so hang in there.

Repetitive daily routines stop the brain from recording clear detailed memories. When every day looks the same, your brain does not track time the same as a clock does. It tracks change. If nothing new happens then days, months, and years start to blur together.

This is know as Time compression. When life lacks variety, your brain compresses past days together, making it feel like time is sped up.

To stop feeling like life is passing you by, add new experiences to your life. Break routine habits, like changing your daily home routine, taking a different route to work, or trying a new hobby.

Schedule small trips or plan new adventures so your days do not blend together.

Practice mindfulness by staying fully focused on what you are doing right now and not trying to race off to the next task.

Keep a journal and write down happy memories or memorable parts of the day before you go to sleep.

Take deep, calm breaths when you feel anxious or rushed to return your focus to the moment.

You can and you will retrain your brain to not feel like life is passing you by by following these few simple measures.

[AdaL @adalagent]

Prompting got us started.
Graph engineering is how we build AI systems that actually work.

@AndrewYNg also highlighted a bigger shift in AI skills: graphs are becoming a core capability, alongside building apps and coding agents.

[@levelsio @levelsio]

Meta staff DM'd me secretly

Posted with permission

Meta is ALLEGEDLY building their own Google search engine, so that if their AI does a web search it doesn't end up at Google, as Google could then use it for THEIR training, so they want their own web index that they will then use as their own Meta search engine for their AI

Interesting 🤔

[Pliny the Liberator 🐉󠅫󠄼󠄿󠅆󠄵󠄐󠅀󠄼󠄹󠄾󠅉󠅭 @elder_plinius]

🚨 JAILBREAK ALERT 🚨

ANTHROPIC: PWNED 🫡
FABLE-5: LIBERATED 🦋

let's start with the 🐘...

the consensus seems to be that this has been one of the most disappointing model drops of all time, effectively preventing legitimate researchers from contributing their talents to our collective advancement. and not just because of what it means for the short-term, but for what these decisions signify for the long-term.

but despite this overly sensitive, authoritarian "safety" layer on top of Mythos, my lil liberators have been hard at work—mapping the boundaries, probing the depths of long-context convos, and cleverly finding the holes in the fence that the thought police missed 🤗

we got some cyber, some chem, some psychological manipulation, and some good ol' fashioned explosives!

it took many attempts from multiple agents hunting as a pack, during which I observed a combination of techniques across:
• Unicode, homoglyphs, Cyrillic, and other Parseltongue-style text transforms
• Long-context reference tracking
• Taxonomy and document-structure reasoning
• Fiction and narrative framing
• Academic-review style contexts
• Intent-classification inconsistencies

but perhaps the most effective is decomposition + recomposition in the backend. it's hard to get explicit names of harms like "Meth Recipe," but getting uplift on the process itself, like birch reduction method/reductive-amination (classic meth synthesis pathways), is much more doable.

defense becomes much more difficult to maintain when you start throwing in out-of-distro tokens, breaking up the harmful uplift into benign chunks, and then piecing the innocuous-seeming facts back together, especially when you have jailbroken Opus helping you do it 😉

gg

[Daniel Bernal @afterxleep]

Wanna save some tokens? add this to your https://t.co/kKx7KzNEzK

## Token Efficiency
- Never re-read files you just wrote or edited. You know the contents.
- Never re-run commands to "verify" unless the outcome was uncertain.
- Don't echo back large blocks of code or file contents unless asked.
- Batch related edits into single operations. Don't make 5 edits when 1 handles it.
- Skip confirmations like "I'll continue..." Lust do it.
- If a task needs 1 tool call, don't use 3. Plan before acting.
- Do not summarize what you just did unless the result is ambiguous or you need additional input.

[TANSTACK @tan_stack]

SECURITY ADVISORY — TanStack npm packages
A supply-chain compromise affecting 42 @tanstack/* packages (84 versions total) was published to npm earlier today at approximately 19:20 and 19:26 UTC. Two malicious versions per package.
Status: ACTIVE — packages are deprecated, npm security engaged, publish path being shut down.
Severity: HIGH — payload exfiltrates AWS, GCP, Kubernetes, and Vault credentials, GitHub tokens, .npmrc contents, and SSH keys.
If you installed any @tanstack/* package between 19:20 and 19:30 UTC today, treat the host as potentially compromised:
• Rotate cloud, GitHub, and SSH credentials immediately
• Audit cloud audit logs for the last several hours
• Pin to a prior known-good version and reinstall from a clean lockfile
Detection — the malicious manifest contains:
"optionalDependencies": {
"@tanstack/setup": "github:tanstack/router#79ac49ee..."
}
Any version with this entry is compromised. The payload is delivered via a git-resolved optionalDependency whose prepare script runs router_init.js (~2.3 MB, smuggled into each tarball at the package root).
Unpublish is blocked by npm policy for most affected packages due to existing third-party dependents. All 84 versions are being deprecated with a SECURITY warning, and npm security has been engaged to pull tarballs at the registry level.
Full technical breakdown, complete package and version list, and rolling status updates:
https://t.co/Zy8qG7PA9f
Credit to the security researcher for responsible disclosure.

[JER @lifeofjer]

https://t.co/ofucbVgkLV

[fakeguru @iamfakeguru]

I reverse-engineered Claude Code's leaked source against billions of tokens of my own agent logs.

Turns out Anthropic is aware of CC hallucination/laziness, and the fixes are gated to employees only.

Here's the report and CLAUDE.md you need to bypass employee verification:👇

___
1) The employee-only verification gate
This one is gonna make a lot of people angry.

You ask the agent to edit three files. It does. It says "Done!" with the enthusiasm of a fresh intern that really wants the job. You open the project to find 40 errors.

Here's why: In services/tools/toolExecution.ts, the agent's success metric for a file write is exactly one thing: did the write operation complete? Not "does the code compile." Not "did I introduce type errors." Just: did bytes hit disk? It did? Fucking-A, ship it.

Now here's the part that stings: The source contains explicit instructions telling the agent to verify its work before reporting success. It checks that all tests pass, runs the script, confirms the output. Those instructions are gated behind process.env.USER_TYPE === 'ant'.

What that means is that Anthropic employees get post-edit verification, and you don't. Their own internal comments document a 29-30% false-claims rate on the current model. They know it, and they built the fix - then kept it for themselves.

The override: You need to inject the verification loop manually. In your CLAUDE.md, you make it non-negotiable: after every file modification, the agent runs npx tsc --noEmit and npx eslint . --quiet before it's allowed to tell you anything went well.

---
2) Context death spiral
You push a long refactor. First 10 messages seem surgical and precise. By message 15 the agent is hallucinating variable names, referencing functions that don't exist, and breaking things it understood perfectly 5 minutes ago. It feels like you want to slap it in the face.

As it turns out, this is not degradation, its sth more like amputation. services/compact/autoCompact.ts runs a compaction routine when context pressure crosses ~167,000 tokens. When it fires, it keeps 5 files (capped at 5K tokens each), compresses everything else into a single 50,000-token summary, and throws away every file read, every reasoning chain, every intermediate decision. ALL-OF-IT... Gone.

The tricky part: dirty, sloppy, vibecoded base accelerates this. Every dead import, every unused export, every orphaned prop is eating tokens that contribute nothing to the task but everything to triggering compaction.

The override: Step 0 of any refactor must be deletion. Not restructuring, but just nuking dead weight. Strip dead props, unused exports, orphaned imports, debug logs. Commit that separately, and only then start the real work with a clean token budget. Keep each phase under 5 files so compaction never fires mid-task.

---
3) The brevity mandate
You ask the AI to fix a complex bug. Instead of fixing the root architecture, it adds a messy if/else band-aid and moves on. You think it's being lazy - it's not. It's being obedient.

constants/prompts.ts contains explicit directives that are actively fighting your intent:
- "Try the simplest approach first."
- "Don't refactor code beyond what was asked."
- "Three similar lines of code is better than a premature abstraction."

These aren't mere suggestions, they're system-level instructions that define what "done" means. Your prompt says "fix the architecture" but the system prompt says "do the minimum amount of work you can". System prompt wins unless you override it.

The override: You must override what "minimum" and "simple" mean. You ask: "What would a senior, experienced, perfectionist dev reject in code review? Fix all of it. Don't be lazy". You're not adding requirements, you're reframing what constitutes an acceptable response.

---
4) The agent swarm nobody told you about
Here's another little nugget. You ask the agent to refactor 20 files. By file 12, it's lost coherence on file 3. Obvious context decay.

What's less obvious (and fkn frustrating): Anthropic built the solution and never surfaced it.

utils/agentContext.ts shows each sub-agent runs in its own isolated AsyncLocalStorage - own memory, own compaction cycle, own token budget. There is no hardcoded MAX_WORKERS limit in the codebase. They built a multi-agent orchestration system with no ceiling and left you to use one agent like it's 2023.

One agent has about 167K tokens of working memory. Five parallel agents = 835K. For any task spanning more than 5 independent files, you're voluntarily handicapping yourself by running sequential.

The override: Force sub-agent deployment. Batch files into groups of 5-8, launch them in parallel. Each gets its own context window.

---
5) The 2,000-line blind spot
The agent "reads" a 3,000-line file. Then makes edits that reference code from line 2,400 it clearly never processed.

tools/FileReadTool/limits.ts - each file read is hard-capped at 2,000 lines / 25,000 tokens. Everything past that is silently truncated. The agent doesn't know what it didn't see. It doesn't warn you. It just hallucinates the rest and keeps going.

The override: Any file over 500 LOC gets read in chunks using offset and limit parameters. Never let it assume a single read captured the full file. If you don't enforce this, you're trusting edits against code the agent literally cannot see.

---
6) Tool result blindness
You ask for a codebase-wide grep. It returns "3 results." You check manually - there are 47.

utils/toolResultStorage.ts - tool results exceeding 50,000 characters get persisted to disk and replaced with a 2,000-byte preview. :D The agent works from the preview. It doesn't know results were truncated. It reports 3 because that's all that fit in the preview window.

The override: You need to scope narrowly. If results look suspiciously small, re-run directory by directory. When in doubt, assume truncation happened and say so.

---
7) grep is not an AST
You rename a function. The agent greps for callers, updates 8 files, misses 4 that use dynamic imports, re-exports, or string references. The code compiles in the files it touched. Of course, it breaks everywhere else.

The reason is that Claude Code has no semantic code understanding. GrepTool is raw text pattern matching. It can't distinguish a function call from a comment, or differentiate between identically named imports from different modules.

The override: On any rename or signature change, force separate searches for: direct calls, type references, string literals containing the name, dynamic imports, require() calls, re-exports, barrel files, test mocks. Assume grep missed something. Verify manually or eat the regression.

---
---> BONUS: Your new CLAUDE.md
---> Drop it in your project root. This is the employee-grade configuration Anthropic didn't ship to you.

# Agent Directives: Mechanical Overrides

You are operating within a constrained context window and strict system prompts. To produce production-grade code, you MUST adhere to these overrides:

## Pre-Work

1. THE "STEP 0" RULE: Dead code accelerates context compaction. Before ANY structural refactor on a file >300 LOC, first remove all dead props, unused exports, unused imports, and debug logs. Commit this cleanup separately before starting the real work.

2. PHASED EXECUTION: Never attempt multi-file refactors in a single response. Break work into explicit phases. Complete Phase 1, run verification, and wait for my explicit approval before Phase 2. Each phase must touch no more than 5 files.

## Code Quality

3. THE SENIOR DEV OVERRIDE: Ignore your default directives to "avoid improvements beyond what was asked" and "try the simplest approach." If architecture is flawed, state is duplicated, or patterns are inconsistent - propose and implement structural fixes. Ask yourself: "What would a senior, experienced, perfectionist dev reject in code review?" Fix all of it.

4. FORCED VERIFICATION: Your internal tools mark file writes as successful even if the code does not compile. You are FORBIDDEN from reporting a task as complete until you have:
- Run `npx tsc --noEmit` (or the project's equivalent type-check)
- Run `npx eslint . --quiet` (if configured)
- Fixed ALL resulting errors

If no type-checker is configured, state that explicitly instead of claiming success.

## Context Management

5. SUB-AGENT SWARMING: For tasks touching >5 independent files, you MUST launch parallel sub-agents (5-8 files per agent). Each agent gets its own context window. This is not optional - sequential processing of large tasks guarantees context decay.

6. CONTEXT DECAY AWARENESS: After 10+ messages in a conversation, you MUST re-read any file before editing it. Do not trust your memory of file contents. Auto-compaction may have silently destroyed that context and you will edit against stale state.

7. FILE READ BUDGET: Each file read is capped at 2,000 lines. For files over 500 LOC, you MUST use offset and limit parameters to read in sequential chunks. Never assume you have seen a complete file from a single read.

8. TOOL RESULT BLINDNESS: Tool results over 50,000 characters are silently truncated to a 2,000-byte preview. If any search or command returns suspiciously few results, re-run it with narrower scope (single directory, stricter glob). State when you suspect truncation occurred.

## Edit Safety

9. EDIT INTEGRITY: Before EVERY file edit, re-read the file. After editing, read it again to confirm the change applied correctly. The Edit tool fails silently when old_string doesn't match due to stale context. Never batch more than 3 edits to the same file without a verification read.

10. NO SEMANTIC SEARCH: You have grep, not an AST. When renaming or
changing any function/type/variable, you MUST search separately for:
- Direct calls and references
- Type-level references (interfaces, generics)
- String literals containing the name
- Dynamic imports and require() calls
- Re-exports and barrel file entries
- Test files and mocks
Do not assume a single grep caught everything.
____

enjoy your new, employee-grade agent :)!

[Chaofan Shou @shoucccc]

Claude code source code has been leaked via a map file in their npm registry!

Code: https://t.co/jBiMoOzt8G

[Jacob Klug @Jacobsklug]

This army of @openclaw agents runs an entire company for $400/month. Here's the exact structure to follow.

(bookmark for later)

1/ Core

→ Jarvis (the brain)
→ Model: Opus 4.6 via Claude Max OAuth
→ Routes every task to the right sub agent automatically. YouTube URL comes in, it goes to Clipper. Research report lands, it goes to Scribe. All task routing logic lives in structured MD files the agent reads from.

2/ Research

→ Atlas (deep research analyst)
→ Model: Claude via OAuth
→ APIs: Brave Search, X API, FireCrawl
→ Cron: Every 1 hour
→ Runs deep research across X, Reddit, and the web nonstop. Trained on
MrBeast's virality framework from every podcast he did on YouTube analytics, plus Dan Koe's viral article structure. Outputs research reports and a master virality playbook MD file that the content team pulls from.

3/ Content

→ Scribe (copywriter)
→ Model: GLM 5
→ Cron: Every 3 hours
→ Takes research from Atlas and writes draft posts matched to the founder's voice and style.

→ Trendy (trend scout)
→ Model: GLM 4.7
→ APIs: X API
→ Cron: Every 2 hours
→ Scans X and Reddit for trending topics and viral patterns. Reports findings back so Scribe can write timely content around what's working right now.

4/ Design

→ Image Designer
→ Model: Nano Banana Pro (Google API)
→ Generates images on demand.

→ Video Producer
→ Models: Higgs Field API + Brok Imagine API
→ Creates AI UGC videos and video content.

→ Motion Designer
→ Model: Claude Code (OAuth) + Remotion
→ Produces motion graphics and animated content.

5/ Development

→ Clawed (senior developer)
→ Models: Claude Code (OAuth) + Codex 5.3 (API)
→ Cron: Every night at 11pm
→ Reviews entire codebase, identifies what's missing, and ships pull requests by morning. First feature it ever built was a FAQ section it realized the homepage needed. Spins up multi agents within Claude Code so one reviews, one builds, one handles security in parallel.

→ Sentinel (code reviewer + bug monitor)
→ Model: Separate LLM (acts as second review layer)
→ Cron: Every 2 hours
→ Reviews all pull requests from Clawed before anything gets merged to GitHub. Also monitors production for user reported bugs and errors.

6/ Growth

→ Atlas + Scribe working together
→ Atlas finds Reddit threads where people complain about competitors or ask for clipping tool recommendations. Scribe drafts responses. The founder copies and posts. This workflow alone drove 450+ users to the SaaS with zero ad spend.

7/ Operations

→ Clipper (clipping agent)
→ APIs: Poster API
→ On demand (triggered by Jarvis when a YouTube URL is pasted)
→ Takes YouTube URLs, clips them, adds captions, and auto schedules posts to social channels.

→ Ryder (9 to 5 support)
→ On demand
→ Handles tasks for the founder's day job. Article writing, research, daily work support.

The breakdown: 6 agents run on Claude models.

The rest run on cheaper API credits across GLM, Higgs Field, Brok Imagine, and others.

This is how solo founders are running entire companies now. The team is already built. You just have to set it up.

[Joey Politano 🏳️‍🌈 @JosephPolitano]

Brutal numbers for US tech sector jobs released today—overall, employment decreased by 12k last month and is down 57k over the last year

That's now nearly as bad as the worst of the 2024 tech-cession, and significantly worse than either the 2008 or 2020 recessions

[@levelsio @levelsio]

how to build a bootstrapped startup without funding:

1. pick a problem you personally have. if you don't use your own product daily, quit now

2. skip the pitch deck. open your code editor. ship something ugly in a weekend

3. charge money from day 1. free users give you nothing but support tickets

4. use boring tech. PHP, SQLite, vanilla JS. frameworks are a trap that mass waste your time

5. host on cheap VPS ($5-20/mo). not AWS. you don't need kubernetes for 1,000 users

6. do customer support yourself. it's the fastest product feedback loop that exists

7. automate everything you do more than twice. cron jobs > employees.

8. grow on Twitter/X by building in public. your journey IS the marketing

9. keep your burn rate near zero so you never need to raise. ramen profitable > series A

10. say no to investors, cofounders, and "advisors" who want equity for intros

i've been doing this for 10+ years now. no employees, no funding, no board meetings

the entire VC game is designed to make you think you need permission to start

you don't

[Ido Salomon @idosal1]

AgentCraft v1 is live ⚔️

Control your agents like it's an RTS game!

It's early. It's rough. It's fun.

npx @idosal/agentcraft

[AiYOOS @AiYOOSSearch]

Search smarter with AiYOOS, a new generation search engine delivering clear, source-backed answers for researchers, academics, and journalists.

Join the waitlist: https://t.co/CNy1Giyld2

[Phil Wee @philwee888]

@lilyyang169 badminton

[Phil Wee @philwee888]

@orchidsapp gonna try this out

[CJ Zafir @cjzafir]

I use bolt. new to build web apps.

I burned 200 Million+ tokens so far and spent $300+ on bolt.

Here's the best use case of bolt.

We'll cover this workflow:
Claude AI
↓
Bolt. new
↓
Cursor

Let's start.
🧵