-
-
Notifications
You must be signed in to change notification settings - Fork 437
Open
Description
Hi! Thanks for the great tool.
I'm using ccusage statusline with AWS Bedrock, and I ran into an issue with the statusline model label.
When using AWS Bedrock Inference Profiles, the displayed model identifier can be very long.
In many cases, it is an ARN(Amazon Resource Name) such as:
# arn:aws:bedrock:<region>:<accountId>:application-inference-profile/<profileId>
arn:aws:bedrock:ap-northeast-1:012345678910:application-inference-profile/abcde12345
This causes two problems:
- Statusline gets truncated due to very long ARN.
- The model name is often not included within the ARN, so even the visible part is not very informative.
This makes it hard to tell which model is currently being used, for example:
🤖 arn:aws:bedrock:ap-northeast-1:012345678910:application-inference-profile/abcde12345 | 💰 $0.00 session / $17.28 today / $17.28 block (57m left) | 🔥 $4.
Proposed Solution
It would be helpful if users could define custom aliases for model labels in the statusline config, for example:
{
"commands": {
"statusline": {
"modelLabelAliases": {
"arn:aws:bedrock:ap-northeast-1:012345678910:application-inference-profile/abcde12345": "claude-opus-4-6"
}
}
}
}🤖 claude-opus-4-6 | 💰 $0.00 session / $17.28 today / $17.28 block (57m left) | 🔥 $5.75/hr | 🧠 50 (0%)
Considerations
- Bedrock inference profile IDs are ARNs, which may contain AWS account IDs, so for some users, exact aliases may be awkward to commit or share (e.g. detected-aws-account-id). Pattern matching alias would be ideal, but too much for the first step.
- If this change feels too broad, I'll also be happy with a more specific improvement for AWS Inference Profiles!
What do you think?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels