I used to have this status line config for a while. And it was really helpful I have to admit. ~/Documents/prjs · Opus 4.8 (1M context) · ctx 18% · 5h 27% · 7d 14% (1d20h) Then I think the place for the status line is very special, it always show in the terminal while prompts and responses flow in and out frequently. What can I do to make the most use of it? It would be more helpful if providing more insights, more up-to-date notes, lively data. And even more interesting if it is like a mini secretary that lives inside your terminal. So I built ccbit , a session-awareness status line that tell you what is really happening across my sessions: is anything working, done, waiting, broken, or stopped here — what just changed, what’s happening in my other sessions, and is this turn behaving normally? And to make it more interesting and lively, a kaomoji face that changes on states. Some examples: (••) idle · 3 other sessions running (••) idle · The session “Read and review project” has new updates — take a look -(๏๏)- editing ccbit (3 files) · 1/4 todos · 2m14s (つ•‿•)つ 4 files edited, line changes: +885/-99. Build succeeded. Tests succeeded. (→←") 2 files edited. Build green again. (╯°□°)╯︵ ┻━┻ ccbit build failed (¬°-°)¬ stopped · last: editing render.go · 2m ago Have been using for a while and really happy with it. It is one Go binary, no hooks and no daemons. Claude Code already writes the session transcript, so Bit just reads it. Repo here (free and MIT): https://github.com/livlign/ccbit How about you guys? What is your favorite status line config? Do you think this would be useful in your daily work? submitted by /u/ahihidummy
Originally posted by u/ahihidummy on r/ClaudeCode