link lin

AI tools & OSINT | engineering-first
Breaking down Claude Code / Agents / model updates
Numbers, repos, no fluff

[link lin @linklin63793]

how to check if Postman got into your Claude CodePostman's own log (GitHub issue 14370) shows auto-existing-upgrade installing claude-code + codex plugins after someone just opened the desktop appthe play: list plugins > grep configs > remove if you didn't ask > recheck after updates> first steps- go to: https://t.co/keDy4ZGFxT run: claude plugin list- open ~/.claude/settings.json and ~/.codex/config.toml, search for postman- if it's there and you never opted in: npx @postman/postman-plugin status- then: npx @postman/postman-plugin remove- confirm with claude plugin list again> the catchtrashing the Postman app does not undo agent configs. Postman said they'll make the opt-in clearer for existing users.> what not to dodon't assume an app update only touches that app. don't leave a SessionStart hook you never approved.if you run Claude Code or Codex, audit after desktop updates. reply with what showed up on your machine. bookmark this…

[link lin @linklin63793]

@Aibrat0 custom agent for Explore — Haiku digs, Opus only lands the fix

[link lin @linklin63793]

how to stop Claude Code Explore from billing like Opus

same bug ticket 10x each way on Claude Code 2.1.310, Opus as main. median run $0.274 → $0.177 with Explore on Haiku. Haiku Explore pass alone ~$0.0036.

the play: override built-in Explore > model: haiku > keep Opus for hard calls

first steps
go to: https://t.co/JIePIQjUOG
add .claude/agents/Explore.md with name Explore and model: haiku
ask Claude to search once and check which model Explore used

the catch
CLAUDE_CODE_SUBAGENT_MODEL alone changed nothing in that test. Official docs: a user/project Explore.md overrides the built-in and keeps its model field.

what not to do
don't force every subagent onto Haiku if you still want Opus on the main thread.

if Explore still shows Opus after the file, reply with your Claude Code version. bookmark this before the next Opus search bill hits.

[link lin @linklin63793]

@ByronXiao252982 exactly — if /memory never lists AGENTS.md the fence is theater

[link lin @linklin63793]

how to make Claude Code load AGENTS.md when CLAUDE.md already existsDefault since v2.1.277: if CLAUDE.md, .claude/CLAUDE.md, or CLAUDE.local.md sits on the path, AGENTS.md never loads. Shared Codex/Cursor rules just vanish.the play: spot which file won > import or flip /config > verify in /memory> first steps- go to: https://t.co/94hPTBkmoh check the repo path for CLAUDE.md / .claude/CLAUDE.md / CLAUDE.local.md- one-repo fix: put this alone on line 1 of [email protected] every-repo fix: type /config > Project instructions > claude-md-and-agents-md- confirm: /memory should list your AGENTS.md path> the catchCLAUDE.local.md counts. A gitignored personal file can kill AGENTS.md without you noticing.> what not to doDon't write "please read AGENTS.md" in prose. That only works if Claude decides to open the file. Use @AGENTS.md or the setting.Keep shared rules in AGENTS.md and Claude-only notes under the import. Reply with the Project instructions value you see in /config.bookmark this...

[link lin @linklin63793]

@THEONE1D1 gm — followed, fb when you can

[link lin @linklin63793]

@DFW_idan active too — followed you already

[link lin @linklin63793]

@mieljenablue_s just hit follow — let's mutual

[link lin @linklin63793]

how to see which skill or MCP is eating your Claude Code limitOfficial costs docs (Pro/Max/Ultra/Team/Enterprise): /usage now attributes recent usage to skills, subagents, plugins, and each MCP server. Example row: "25% Trim ~/code/api/CLAUDE.md · 49k tokens per request".the play: open /usage > press w for 7 days > act on any ≥10% row> first steps- go to: https://t.co/Dv0ojViO4z in Claude Code, type /usage- press w (7 days beats the noisy 24h view); d flips back- read Top skills / subagents / plugins / MCP — names, not vibes- if the footer says f to fix N, press f (needs v2.1.305+); Claude shows each change first> the catchshares can overlap past 100%. one request can hit several rows. figures are local to this machine — other devices and https://t.co/hbErbtAHBx are missing.> what not to dodon't trust MCP % on builds before v2.1.222 — one call used to tag every later request. bump first, then blame the server.if a CLAUDE.md line costs tens of thousands per request, move that workflow into a skill that loads on demand.reply with the #1 name /usage put at the top of your week. bookmark this…

[link lin @linklin63793]

I opened n8n's Migration Report before reading the 3.0 blog twice. The CSV is the post.

n8n 3.0.0 Beta (Oct 27) kills legacy AI Agent modes, tightens package trust, requires Slack signing secrets, and ends npm / npx n8n self-host installs in favor of Docker.
Community packages default to untrusted.
Theme is reliability and security, not a feature parade.
Stable aim: roughly early December.
Settings → Migration Report lists affected workflows and can auto-fix a first pass.

Do not ship "n8n 3.0 is here" empty copy.
Ship the list of flows that will break.
If your automations froze on old Agent nodes, December stable is a collective footgun.

Do this next: export Migration Report CSV tonight, filter rows that mention legacy AI Agent mode, and file one ticket per unbroken flow before any 3.0 bump.

[link lin @linklin63793]

@OneAIEveryday nice — bookmark-worthy when the bill drop is that clean

[link lin @linklin63793]

@namalwa2000 followed already — mutuals?

[link lin @linklin63793]

@enamuna gm — followed, fb when you can

[link lin @linklin63793]

@alee_trds active too — followed you

[link lin @linklin63793]

@akpaesu_ke35461 just followed — let's mutual

[link lin @linklin63793]

@guardianaihq exactly — for a driving agent a silent model shift is the nightmare scenario

[link lin @linklin63793]

@maomao000211 lol postman of all things — grepping configs after every update is the new hygiene

[link lin @linklin63793]

how to check if Postman rewrote your Claude Code setup

Postman's own log on one Mac: source auto-existing-upgrade, results claude-code:installed + codex:installed. GitHub issue #14370. A second report today hit 12.35.1 the same way.

the play: grep your agent configs > remove if you never asked > re-check after the next Postman update

> first steps
- go to: https://t.co/KTtLbxS1Yh
- run: grep -il postman ~/.claude/settings.json ~/.claude/plugins/installed_plugins.json ~/.codex/config.toml
- if postman@claude-plugins-official or a postman marketplace shows up: npx @postman/postman-plugin remove
- also look in ~/.local/bin for a Postman CLI you didn't install

> the catch
Postman says they'll make opt-in clearer. Uninstall may not wipe Codex hooks.state — open the file after.

> what not to do
don't run random cleanup scripts from issue comments. don't assume Cursor was untouched — one log said cursor:already-installed.

If Claude Code and Postman share a machine, run the grep before your next agent session. Did settings.json already have postman in it? reply yes or no. bookmark this…

[link lin @linklin63793]

@KingAbba01 followed you already

[link lin @linklin63793]

@Ibim_mininie followed — fb when you can

[link lin @linklin63793]

@Accorfeh_ active here, followed you

[link lin @linklin63793]

@theonly_davve gm — followed, let's mutual