Configure the devloop statusline in Claude Code settings.
Configures the devloop statusline in Claude Code settings to display model, context, tokens, path, branch, and plan progress.
/plugin marketplace add Zate/cc-plugins/plugin install zate-devloop-plugins-devloop@Zate/cc-pluginsConfigure the devloop statusline in Claude Code settings.
Read the user's Claude Code settings:
Read ~/.claude/settings.json
Analyze the settings to determine the current state:
The devloop statusline script path follows this pattern:
~/.claude/plugins/cache/cc-plugins/devloop/{version}/statusline/devloop-statusline.sh
Find the installed version by checking the plugin cache directory.
Add the statusLine field to settings.json:
{
"statusLine": {
"type": "command",
"command": "~/.claude/plugins/cache/cc-plugins/devloop/{version}/statusline/devloop-statusline.sh",
"padding": 0
}
}
Check if path needs updating (version change). Update if necessary.
Ask user:
AskUserQuestion:
question: "You have an existing statusline configured. What would you like to do?"
header: "Statusline"
options:
- label: "Replace with devloop"
description: "Use devloop statusline instead"
- label: "Keep existing"
description: "Don't change current statusline"
Use the Edit tool to update ~/.claude/settings.json with the statusLine configuration.
Tell the user:
Devloop statusline configured!
Path: ~/.claude/plugins/cache/cc-plugins/devloop/{version}/statusline/devloop-statusline.sh
Restart Claude Code to see the statusline displaying:
- Model name (Opus/Sonnet/Haiku)
- Context window usage (progress bar + %)
- Session tokens
- Current directory
- Git branch
- Plan progress (if .devloop/plan.md exists)
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences