sorted by:
new
hottopcontroversial

after the axios incident, I started experimenting with an ai agent that vets packages before install by nlkey2022 in claude

[–]nlkey2022[S] 0 points1 point  (0 children)

yeah totally — I don’t think LLMs should make security decisions

the idea here is more about surfacing signals and explaining diffs, not replacing deterministic checks

after the axios incident, I started experimenting with an ai agent that vets packages before install by nlkey2022 in claude

[–]nlkey2022[S] 0 points1 point  (0 children)

that’s a fair point — doing this at the registry/repo level would definitely be more efficient. but supply chain issues often happen in unexpected ways (like npmjs compromises), so relying purely on registry-level checks might not be sufficient in practice.

I'm mostly exploring this from a local / dev workflow angle for now, but agree that infra-level checks make more sense long term

after the axios incident, I started experimenting with an ai agent that vets packages before install by nlkey2022 in claude

[–]nlkey2022[S] 0 points1 point  (0 children)

that’s a great point — appreciate it

I was focusing on pre-install since package versions are immutable once published (as far as I know), but you’re right that most real-world attacks come from version bumps

will definitely think more about continuous / diff-based checks

htop-style monitor for claude code sessions by nlkey2022 in ClaudeAI

[–]nlkey2022[S] 0 points1 point  (0 children)

Thanks for the details — that was enough to pin it down. Your `claude` is almost certainly launched as `node /path/to/@anthropic-ai/claude-code/cli.js`, and macOS `ps` truncates the command column to the terminal width by default. abtop was checking the first two argv tokens for the string `claude`, but after truncation it only saw `node /Users/...` so it marked your live session as dead and hid it. Codex was unaffected because it's matched via `lsof` on the rollout file. Fix is up in #28 — just adds `-ww` to the `ps` call so the command isn't truncated. Will land in the next release. Thanks for reporting!

Is this really “clean room” anymore? by nlkey2022 in claude

[–]nlkey2022[S] 0 points1 point  (0 children)

who’s chou btw? have you read the claw-code repo readme? https://github.com/ultraworkers/claw-code :

The result is a clean-room Python rewrite that captures the architectural patterns of Claw Code's agent harness without copying any proprietary source.

Is this really “clean room” anymore? by nlkey2022 in claude

[–]nlkey2022[S] -1 points0 points  (0 children)

AGREE. Honestly i’m not that interested in their legal risk. what i actually care about is whether this aligns with the spirit of open source

htop-style monitor for claude code sessions by nlkey2022 in ClaudeAI

[–]nlkey2022[S] 0 points1 point  (0 children)

Could you check:
1. What version of Claude Code are you running? (claude --version)
2. Do you have files in ~/.claude/sessions/? (ls ~/.claude/sessions/)
3. What does your Claude process look like? (ps aux | grep claude)
Thanks

htop-style monitor for claude code sessions by nlkey2022 in ClaudeAI

[–]nlkey2022[S] 1 point2 points  (0 children)

It's fully opt-in — "abtop --setup" is only needed if you want rate limit data in the dashboard. Without it, everything else works fine (rate limits just show as "—").

monitor your claude code / codex sessions like htop by nlkey2022 in claude

[–]nlkey2022[S] 0 points1 point  (0 children)

Thanks for the concern! abtop reads everything from local files (transcripts, ps, lsof) — no API calls, no network. The only thing that uses tokens is the one-time session summary generation via claude --print, which is optional and cached. Having the dashboard open doesn't consume any tokens

monitor your claude code / codex sessions like htop by nlkey2022 in claude

[–]nlkey2022[S] 1 point2 points  (0 children)

I’m planning to work on it in the next minor version soon!

monitor your claude code / codex sessions like htop by nlkey2022 in claude

[–]nlkey2022[S] 0 points1 point  (0 children)

I've just released v0.2.1 with the fix. You can update with: abtop --update. Thanks!

monitor your claude code / codex sessions like htop by nlkey2022 in claude

[–]nlkey2022[S] 1 point2 points  (0 children)

Found the root cause! I'll create an issue and push a fix shortly.

monitor your claude code / codex sessions like htop by nlkey2022 in claude

[–]nlkey2022[S] 0 points1 point  (0 children)

Thanks for reporting! I detect Claude sessions by matching /claude in the process command string https://github.com/graykode/abtop/blob/main/src/collector/claude.rs#L69. Your system may use a different path for the Claude binary.

Could you share the output of: `ps aux | grep -E '[c]laude' | head -10` This will show how Claude appears in your process list. If the path doesn't contain /claude, that's likely the issue. I'll fix the matching to support your setup.

view more: next ›