WorkBack
Find the root cause of bugs using logs and github issues, instantly.
Installation
pipx install workback
Usage
1. Set Claude API key:
echo "{{CLAUDE_API_KEY}}" > ~/.workback/api_key
2. Navigate to your project:
cd path_to_your_project
3. Launch:
workback
4. Start with logs or github issues to find the root cause:
/analyze /var/log/system.log
5. Setup GitHub (only required for /github command):
echo "{{GITHUB_TOKEN}}" > ~/.workback/github_key
6. Analyze GitHub Issues:
/github https://github.com/ParabolInc/parabol/issues/11258
Open Source Root Causes
Here are some real-world examples of root cause analysis performed by WorkBack on open source projects:
Parabol Meeting Timer
Analysis of a race condition in Parabol's meeting timer implementation causing unexpected resets.
View Analysis →Bolt Task Failures
Investigation of task execution failures in Puppet Bolt's parallel operation mode.
View Analysis →InfluxDB Timestamp Precision
Analysis of replication failures with high-precision timestamps in InfluxDB.
View Analysis →Reports
All analysis reports are automatically saved in:
~/.workback/reports
Interactive Help
When WorkBack needs a specific file:
/resume /absolute/path/to/file
Use this when WorkBack asks for files from libraries or other repositories.
When WorkBack has a question:
/answer Your response to the question
Use this to provide additional context or clarification when asked.
Security
WorkBack runs entirely between you and your private Claude API key. For questions or to report issues, contact [email protected].
-
APIs: WorkBack uses two following APIs
- Claude for analysis
- GitHub for issue fetching
-
Storage: WorkBack stores everything locally on your machine
- Analysis reports in
~/.workback/reports
- API keys in
~/.workback/
About
Connect | GitHub X LinkedIn Blog |
Contact | [email protected] [email protected] |
Team | Priyank Chodisetti Arthur Gousset |