Teamwork Graph CLI の一般的な問題を修正する
If you run into issues with Teamwork Graph CLI, use this page to diagnose common problems, keep the CLI up to date, and get help.
Run all of these troubleshooting commands from your terminal.
Run a health check
To check your authentication, connectivity, and build info, run:
twg doctorThis is always the best first step — it tells you what's working and what isn't.
Repair your setup
If twg doctor reports issues with your configuration or agent skills, run:
twg setupThis re-runs the setup process and refreshes your agent skill files without reinstalling the binary.
If you still encounter errors, check your network connection. If you’re on a VPN, confirm that Atlassian domains are accessible. Once resolved, run twg doctor again to verify.
Update Teamwork Graph CLI
If you're on version 0.9.6 or earlier, twg update may not work correctly. Instead, follow these steps to update it manually.
macOS and Linux — curl installer (recommended for older versions):
curl -fsSL https://teamwork-graph.atlassian.com/cli/install -o twg-install.sh
bash twg-install.shWindows — PowerShell:
curl.exe -fsSL https://teamwork-graph.atlassian.com/cli/install.ps1 -o twg-install.ps1
powershell -ExecutionPolicy Bypass -File .\twg-install.ps1Windows — Command Prompt:
curl.exe -fsSL https://teamwork-graph.atlassian.com/cli/install.ps1 -o twg-install.ps1
powershell -ExecutionPolicy Bypass -File twg-install.ps1If you're on version 0.9.7 or later and want to use the built-in updater:
twg updateTo see what's changed in recent versions, view the TWG CLI changelog.
一般的な課題
Issue | ソリューション |
|---|---|
|
|
| Add the line printed by the installer to your shell profile (for example, |
インストール中に Windows SmartScreen の警告が表示される | Select More info, then Run anyway. This is expected for pre-release builds that don't yet have a production code signature. |
OAuth authentication expired | Run |
Agent cannot refresh credentials | Give the agent write access to the active TWG config directory, or run |
Agent can see | Confirm that it can also access the macOS Keychain or Windows Credential Manager entry. On Linux, provide the same |
Linux reports a missing or invalid storage key | Supply the original unpadded base64url-encoded 32-byte key. A different key cannot decrypt the existing database. Do not fall back silently to another key source. |
Migration did not complete | Run |
Encrypted database is corrupt or cannot be recovered | Run |
Bitbucket commands fail | Run |
Agent isn’t using TWG CLI skills |
|
この内容はお役に立ちましたか?