Support multiple profiles (instances/accounts)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 48/100
Research direction
Start by reading internal/config/CLAUDE.md, especially the profile-support TODO, then trace the existing auth login, configuration loading, keyring storage, and command flag handling. Define the migration from the flat config and verify that profile selection follows the stated precedence while preserving existing setups.
Written by the indexing model from the issue text.
Description
Is your feature or enhancement related to a problem? Please describe.
The CLI stores a single instance in ~/.chatwoot/config.yaml (base URL + account ID, with the token in the OS keyring). If you work across more than one Chatwoot there's no way to keep them side by side: a self-hosted staging vs production, an agency with several client accounts, or one person who belongs to multiple accounts. The only option today is re-running auth login, which overwrites the saved login every time you switch. internal/config/CLAUDE.md already lists this as a TODO ("Add profile support (multiple saved credentials)").
Describe the solution you'd like
Named profiles, following the CLI's existing noun grammar:
chatwoot auth login --profile staging # save a second instance
chatwoot profiles # list saved profiles
chatwoot profile staging use # set the default
chatwoot --profile staging convs # one-off override for one command
Resolution order: --profile flag, then CHATWOOT_PROFILE, then a configured default, then default. Each profile keeps its own token in the keyring. The existing flat config would migrate into a default profile on first load, so current setups keep working with no re-login.
Describe alternatives you've considered
- Re-running
auth loginto switch instances (the status quo, loses the previous login each time). CHATWOOT_API_KEYplus-afor the account, but the env var is global, so it can't hold more than one instance at once and still needs the matching base URL.- Hand-managed config files or per-shell wrappers, which is the manual version of what profiles would do.
Additional context
I run a few instances and would be glad to open a PR for this if it's a direction you'd accept.
- Dominant language
- Go
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from chatwoot/cli
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/github-mcp-server#3865 ·
Maintainers usually reply within 2 days
-
kind/features
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
TencentBlueKing/bk-nodemgr#4017 ·
Maintainers usually reply within 1 day
-
ssa: wait errors drop the kstatus message, so health check failures don't say whyPossibly taken @schdief claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
equinor/radix-operator#2066 ·
Maintainers usually reply within 2 days