Business Scalability and Transformation Engineer @ Ad Limen | I help businesses scale sustainably | Scalability Compass 🧭 | Let’s build impactful growth.
@ranman@VicVijayakumar@npmjs We are so lucky to have product like sfw to help with prevention, software’s history is an everyday event of exfiltration, impossible to block in advance.
@jacob_posel@kamilrextin@bcherny@claudeai 120 eur today just for weekly limit finishing 2 days and half before, while not arriving usually over 80%
Just a small change in policy
🚨 CRITICAL: Active supply chain attack on axios -- one of npm's most depended-on packages.
The latest [email protected] now pulls in [email protected], a package that did not exist before today. This is a live compromise.
This is textbook supply chain installer malware. axios has 100M+ weekly downloads. Every npm install pulling the latest version is potentially compromised right now.
Socket AI analysis confirms this is malware. plain-crypto-js is an obfuscated dropper/loader that:
• Deobfuscates embedded payloads and operational strings at runtime
• Dynamically loads fs, os, and execSync to evade static analysis
• Executes decoded shell commands
• Stages and copies payload files into OS temp and Windows ProgramData directories
• Deletes and renames artifacts post-execution to destroy forensic evidence
If you use axios, pin your version immediately and audit your lockfiles. Do not upgrade.
Am I the only one with big PROBLEMS with @claudeai after version 2.1.79?
⎿ Context limit reached · /compact or /clear to continue
After 175k approx (no autocompact active)
And no more "clear context (x% used) and auto-accept edits
AWFUL!!
I didn't touch anything.
When a super pro max plan??
I find the 200k window very good, but having the possibility to switch to 1m when session was proximate to limit permitted me many time to just finish, write continuation.md and then compact and restart!
Having the 1m window in subscription enable other workflows
Finally!!!
I never used the Mcp version as it completely ruins my context window.
This reduces a lot moving out from google workspace, meet to test it immediately.
Introducing the Google Workspace CLI: https://t.co/8yWtbxiVPp - built for humans and agents.
Google Drive, Gmail, Calendar, and every Workspace API. 40+ agent skills included.
@elvissun Lots of inspiration. I rewrote a claude agent sdk version of openclaw, and your setup seems an improvement I'd like to try soon.
tmux for agents is next level, and having the right babysitting workflow unblocks new lifestyles
@harjjotsinghh@delba_oliveira Never got it to work properly. I added a memory system that write a local memory for it to continue after compacting. I prefer compacting c unfortunately, because it maintains tasks.
Counterpoint 1st point.
I thought the same until today. For the first time ever I risk to hit my weekly limit (90% today, reset Monday 8am).
Well, on the contrarian I had probably my most productive week.
I refactored lots of obsidian notes, prepared a bunch of legal documents while refactoring many elements shared between my projects into libraries and pushed back to create coherence between some projects. Opus 4.6 together with companion reviews from codex 5.3 is simply amazing and I am using them to solve more complex problems and they usually one shot them together.
Also, I saw a great improvement in understanding frontend structure (from code)
Linux is the best profiting platform for all of this. Would it have macOS hw natively…
Since the moment I activated parallels, all my application-related coding passwords from Debian/ubuntu vms, for be pushed later to vps for production.
Codex cli, or Claude code cli or the sdk versions are just perfect with Linux.
it depends on your use case. Cc CLI requires a more fine tuned environment to get what you can easily do in https://t.co/oq4c7JOToC with projects, a good instruction/prompt and files + memory.
However, if you are already confident with your setup plus having a bit of time, moving the whole setup, rebuilding a similar environment, skills, tools in cc leverages it after the first friction.
Assuming you are a claude code user already, not from scratch.
Always.
Particularly with PRPs, as I want them to be TDD, it helps very much to have one-shot implementation.
The Opus orchestrator that plans the following implementation usually comments after this that it is “a straightaway implementation” so that I can’t avoid deleting context after the plan. Opus has full knowledge, and it goes straight with small refactoring after the green phase.
With the Codex Companion after implementation, generally it resolves issues, and it reduces a lot the back and forth with review agents in PRs. I never got easy PRs (for important features) before this companion system.
Something I need to mention: codex does not work from a blank state, so this system is particularly token-effective in api cost. I realized that with clear specs, Claude is better to implement, and Codex CLI is like a warranty agile second developer that brings to life spectacular adherence to specs.
When we spend time on clear specs, this duo is a dream realization machine.
Interesting take.
In the same way we use sub https://t.co/oaBfSS6dGC files in subfolders we can use the main https://t.co/oaBfSS6dGC as a subfolder one.
However I drive crazy every time I don’t work where the .git folder is, or every time Claude misses a task because of the wrong path.
Do you have a good hook for !pwd?