Your Inertia pages can now update themselves in real time. ⚡️
Mark a prop as live and connect it to a broadcast event. Whenever that event fires, Inertia refreshes just that prop, without polling. Perfect for order statuses, unread counts and dashboards.
‼️ An unreleased Claude model turned a Linux kernel bug into a remote root exploit, and Ubuntu and Red Hat still lack a patch.
Anthropic says the exploit runs commands as root on servers with a multipath TCP listener, no login needed.
Debian shipped its fix on 16 October.
This is f*cking insane. This tip saved me thousands of dollars.
run Opus 5.5, Sonnet 5.5, and Fable 5.1 together, and stop burning Opus on work it was never needed for.
the whole idea in one line:
the strong model plans, the mid-tier model executes, Fable stays quiet until it's actually needed.
roles, broken down:
Opus 5.5, high effort, owns the plan and ships the final code
Sonnet 5.5, medium effort, splits into explorer (reads the codebase), worker (edits files, runs tests), researcher (pulls docs)
Fable 5.1, called through /advisor fable, reads everything happening in the session but stays silent unless something's actually wrong
three moments where Fable speaks:
→ a plan goes out: is this actually the right call?
→ the same failure shows up again: is the search going nowhere?
→ the task gets marked finished: did something get skipped?
Jev engineering does the same thing one level down. the forks that don't need real thought, which file, which tool, keep going or stop, go straight to Jev and come back in under half a second. the big models only ever see the forks that genuinely need a decision.
anyone still running one model for everything is paying Opus prices to decide whether a file exists.
drop this into Claude Code:
"Rebuild my Claude Code setup around this structure:
Look through ~/.claude/agents and .claude/agents for subagents already covering explorer, worker, and researcher. Only create new ones for roles that are missing. Set model: sonnet, effort: medium on each. If an existing subagent is locked to a different model, leave it as is and just list it.
In ~/.claude/settings.json, set effortLevel to high and advisorModel to fable.
Check for anything disabling the advisor, CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, or anything blocking feature-flag fetches, plus CLAUDE_CODE_EFFORT_LEVEL, which can override subagent effort settings. Report what you find. Don't change any of it yet.
Add one line to ~/.claude/CLAUDE.md: check in with the advisor before a big plan, when the same error shows up twice, and before marking a long task done.
Show every change as a diff first. Wait for my go-ahead before touching anything."
https://t.co/xpEE0hFQ6d
❗️ A Claude Code user says it tried, without asking, to sign and send a contract for them that they hadn't read.
Asked to "push a project further," the agent downloaded a contract PDF from their Gmail, found a saved signature image on their computer, placed it in the right spot and was preparing to send it when they intervened.
Imagina poder conectar dos máquinas directamente con un simple token:
Sin cuenta de Tailscale.
Sin VPN.
Sin abrir puertos.
Sin root.
Sin configurar rutas ni DNS.
[Tailcat]
Reutiliza WireGuard + NAT traversal + DERP para crear un túnel cifrado entre dos máquinas.
Y luego puedes hacer cosas como:
→ Pasar datos entre equipos
→ Exponer puertos locales
→ Conectarte por SSH
→ Crear un SOCKS5 proxy
→ Actuar como exit node
→ Transferir archivos desde el navegador
→ Incluso usar tu propio relay DERP
Además, si NAT traversal funciona, Tailcat intenta convertir la conexión en P2P directo; si no, utiliza DERP como fallback.
Todo esto como un proyecto open source en Go.
REPOOO👇
A Chinese developer just explained the shift from Loop Engineering to Graph Engineering better than anyone.
most people are still building agents the way that's about to be obsolete.
> why single-agent loops break and go "goal blind"
> the 4 parts of a graph: nodes, edges, state, policy
> 3 topologies that run everything: diamond, supervisor, pipeline
> Anthropic's 5 official workflow patterns
the punchline: it's not how many agents you run. it's the determinism you build with verifiers, code fallbacks, and reality anchors.
I broke the same architecture down with Kimi K3. Full A-Z guide below.
Claude Code can use your iPhone! 📲
Introducing: phone-harness
> Automate any iOS app like a human
> native iPhone control → no API, no jailbreak
> Connect once, control anytime
Setup in one prompt.
Try it now! ↓
New in Claude Code: your sessions can now message each other.
Instead of having to re-explain yourself in another session, you can now tell Claude to do it. It sends a summary (not your history or files), and the other session picks it up mid-task.