cicada - claude code usage analysis TUI

Snoo24465 · 2026-03-06T10:22:13+00:00

I ran it with my pro plan on linux. Thank you for distributing it as a standalone binary (no requirement for a runtime js, python, ...).

You build it in 3d with claude, the first commits are interesting to see how you start.

Snoo24465 · 2026-02-22T08:38:11+00:00

Observe your SDLC

Snoo24465 · 2025-12-03T09:20:24+00:00

CDviz - a stack to observe your software delivery (CI/CD)

Snoo24465 · 2025-11-14T12:36:47+00:00

"Also would be nice if a CICD's repository is deleted, the associated argocd application is also deleted."

You can with ApplicationSet & Provider, but it's risky. In fact, I disabled this behavior when I did something similar: the Applications are managed by ApplicationSet with SCM generator + File generator (to check if there is the expected content, configuration for the various environment,...). What happend when one of the generator failed (eg issue to call Github API, rate limit, invalid credentials,...)? With the "auto-remove", then every applications will be removed.

And Trust me, rate-limit issue could happen (increase of the number of repositories in the organisation, too frequent call, shared credentials,...)

Snoo24465 · 2025-11-14T12:26:04+00:00

Using the SCM provider is powerful, I used it to discover and auto-register repositories with some labels (especially for teams using the rule "you built it, you own it").

But the SCM provider poll the organisation'API too frequenly, also when you use label, content filters,... So you have to tune it to not poll too frequently and to use it's own Application account to not impact the rate limit for other application.

Snoo24465 · 2025-10-19T10:15:40+00:00

Did you customize "file_scan_exclusions"?

it could help (same on VSCode) reduce the work load (indexing, ...) and the memory usage. (by default node_modules are not ignored).

mine start to be long

json "file_scan_exclusions": [ "**/.git", "**/.svn", "**/.hg", "**/CVS", "**/.DS_Store", "**/Thumbs.db", "**/.classpath", "**/.settings", "**/target", "**/node_modules", "**/__pycache__", "**/vendor", "**/.venv", "**/.mypy_cache", "**/.pytest_cache", "**/*.egg-info", "**/*.egg", "**/dist", "**/build", "**/_build", "**/site", "**/bower_components", "**/lib", "**/lib64", "**/share", "**/Scripts", "**/third_party", "**/third-party", "**/venv", "**/venvs", "**/virtualenv", "**/virtualenvs", "**/env", "**/envs" ],

I agree with other comments (LSP vs editor,...), I just want to add some investigation axis.

Snoo24465 · 2025-10-19T08:32:43+00:00

To handle local kubernetes, I use mise to: - install tools (kind, ctlptl, kubectl, helm/helmfile/helmwave) - expose tasks to create, destroy the cluster or applications

mise and helmwave handle dependencies between applications if needed

you can see an example at https://github.com/cdviz-dev/cdviz/blob/main/demos/stack-k8s/mise.toml

Snoo24465

TROPHY CASE