Share your status line and roll it out to a team

A good status line is worth sharing: with a colleague who likes yours, with your future self on a new laptop, or with a whole team so everyone sees the same numbers. This lesson covers the ways to do that, from one link to a file in the repository.

#Send a design as a link

Click Share in the bar at the top of Statusline Studio. It copies a link that opens this exact design: the segments, the theme, the preview data and the language.

The design travels inside the link, in the part after #, which browsers never send to a server. Nothing is uploaded. Whoever opens the link can change the design freely; their changes do not touch yours.

#Know where your work is kept

While you work, the studio keeps your design in this browser, so it is still there tomorrow. It stays until you reset it. The round-arrow button, Reset to defaults, puts the studio back to where it started. Undo next to it brings your design back while the page is open, but a share link keeps it for good, so save one first.

#Keep it in your dotfiles

If you keep your configuration in a dotfiles repository, treat the status line like any other config file:

1. Download the script with Download, or copy it from Generated code
2. Save it in your dotfiles as claude/statusline.sh
3. Link it into place and add the setting from the settings.json tab

ln -sf ~/dotfiles/claude/statusline.sh ~/.claude/statusline.sh

Because the setting runs bash ~/.claude/statusline.sh, a symlinked file works without an executable bit.

#Give a whole project the same status line

Claude Code reads settings from several places. ~/.claude/settings.json is yours alone. A project's .claude/settings.json is checked into the repository and applies to everyone who opens Claude Code in it, and it wins over the user file in that project.

To give a team one status line:

1. Commit the script into the repository, for example as .claude/statusline.sh
2. Add the setting to the project's .claude/settings.json. git rev-parse --show-toplevel finds the project root, so the command works from any folder in the repository and on every teammate's machine

{
  "statusLine": {
    "type": "command",
    "command": "bash \"$(git rev-parse --show-toplevel)/.claude/statusline.sh\"",
    "padding": 0
  }
}

1. Pick a design with modest needs: Text icons (not everyone has a Nerd Font) and a language everyone has. Bash needs jq; if some teammates lack it, choose Python.

#Make one that is safe to show

On a screen share or a stream, your status line shows paths, branch names, your user name and what you spend. The Screen Share template shows none of that: no paths, names or money, with text icons that work on any machine.

Keep it as a second design: load Screen Share, adjust it, and save its share link. Before a meeting, open the link, copy the install command, and paste it. After the meeting, paste your normal design's install command again. Both designs write the same ~/.claude/statusline.sh, and installing Screen Share keeps your own script as statusline.sh.bak, so putting that back works too:

cp ~/.claude/statusline.sh.bak ~/.claude/statusline.sh

That was the last lesson. You now know all of Statusline Studio: segments, styling, themes, layouts, the script, fixing it, subagent rows and sharing. If something is missing or does not work as described, the Feedback button in the studio's bar sends it to the issue tracker.