Track time effortlessly. Generate reports instantly. Your data stays yours.
π Get Started β’ β¨ Features β’ π How to Use β’ π Support Us
CronoHub was born from a real need at Gopenux, a Colombian software development company with years of experience building enterprise solutions.
Our development teams needed a way to track time on GitHub issues without:
- β Leaving their workflow to use external tools
- β Manually updating spreadsheets (tedious and error-prone)
- β Sharing sensitive data with third-party services
- β Spending hours compiling team reports
We built CronoHub β a Chrome extension that integrates seamlessly into GitHub:
- β Log time directly on issues with one click
- β Automatic formatting as professional GitHub comments
- β Generate multi-user reports instantly
- β 100% local β your data never leaves GitHub
- β Zero data collection β your privacy guaranteed
We found it so useful, we're sharing it with everyone under the MIT License.
|
|
|
|
When you first install CronoHub, you'll see helpful setup instructions:
When you open the panel, CronoHub automatically validates your token's permissions:
What's validated:
- β Repository exists and you have read access
- β Your token has write permission (required to post comments)
- β No rate limiting or network issues
If validation fails, you'll see:
- π΄ Access Denied - Clear error message explaining the issue
- π‘ Possible Solutions - Step-by-step guidance to fix the problem
- π Quick Links - Direct links to GitHub settings to regenerate token
This proactive validation prevents you from filling out the form only to receive an error on submit.
π Important Note: The floating button (β±οΈ) only appears on GitHub issue pages. This includes:
- Classic issue view:
github.com/:owner/:repo/issues/:number- GitHub Projects side panel when viewing an issue
The button will not appear on repository home pages, pull requests, or other GitHub pages.
Smart Navigation Features:
The report includes intelligent navigation with dual clickable links:
-
Issue Number (e.g.,
#33): Click to navigate to the issue- Opens the issue at the top (beginning of the page)
- Opens in a new tab if different from current issue
- Scrolls to top if you're already viewing that issue
-
Description (e.g., "Created categories data model"): Click to navigate to the specific comment
- Opens the issue and scrolls directly to the time tracking comment
- Opens in a new tab if different from current issue
- Scrolls to comment if you're already viewing that issue
This dual-link approach gives you flexibility: quick issue overview or direct comment access.
- Google Chrome (Stable or Beta)
- GitHub Personal Access Token (create one here)
- Required scope:
repo(Full control of private repositories)- This includes: read user info, read/write issues, read comments, search repositories
- Recommended: Grant access to all repositories to use CronoHub across all your projects
- Alternative: Grant access to specific repositories if you only need it for certain projects
- See Token Permissions below for detailed explanation
- Required scope:
# 1. Clone the repository
git clone https://github.com/Gopenux/CronoHub.git
cd CronoHub2. Open Chrome and navigate to chrome://extensions/
3. Enable "Developer mode" (toggle in top-right corner)
4. Click "Load unpacked" button
5. Select the CronoHub folder
6. Click the CronoHub extension icon in your toolbar
7. Paste your GitHub token
8. Click "Save configuration"
β Installation complete! Navigate to any GitHub issue to start tracking time.
For CronoHub to work correctly, your GitHub Personal Access Token must have the following scope:
repo (Full control of private repositories)
This scope grants access to:
- β
repo:status- Read commit status (required for API access) - β
repo_deployment- Read deployment status - β
public_repo- Read and write to public repositories - β
repo:invite- Access to repository invitations - β Write access to issues - Required to post time tracking comments
β οΈ Important: Thereposcope is necessary because CronoHub needs to:
- Read your user information and organization members
- Read issue comments to generate reports
- Write time tracking comments to issues
- Search across repositories for time entries
When creating your token, choose how broadly it should work:
Option 1: All Repositories (Recommended)
- Grant the token access to all repositories
- β Use CronoHub on any repository you have access to
- β No need to regenerate tokens for new projects
- β Seamless experience across your entire GitHub account
Option 2: Specific Repositories
- Grant the token access to selected repositories only
- β More granular security control
- β Useful if you only track time on specific projects
β οΈ Will need to update token permissions to add new repositories later
π‘ Tip: Most users prefer "All Repositories" for convenience. Your token is stored locally and never shared with external services, so the broader access is safe.
β οΈ Important: The CronoHub floating button only appears on GitHub issue pages. Make sure you're viewing an issue (either in classic view or GitHub Projects side panel) to see the time tracking button.
|
1. Navigate to Issue Open any GitHub issue (works in classic view and GitHub Projects) |
2. Click Button Look for the green floating button (β±οΈ) in the bottom-right corner |
3. Enter Time Input hours (e.g., |
Your time entry is posted as a formatted comment:
β±οΈ **Time Tracked:** 2.5 Hours
Implemented user authentication and session management
---
Logged with CronoHub by Gopenux AI Team|
1. Open Panel Click the CronoHub button |
2. Switch Mode Select "Reports" tab |
3. Select Team Choose collaborators (you're pre-selected) |
4. Generate Pick date range and click "Generate Report" |
Report Features:
- Total hours per user and grand total
- Breakdown by date (collapsible sections)
- Smart dual clickable links:
- Issue number β navigates to issue top
- Description β navigates to specific comment
- Context-aware navigation (new tab vs. scroll)
- Support for up to 90-day ranges
We don't collect ANY data. Ever.
This is not marketing speak β it's architecturally guaranteed:
| Aspect | How We Protect You |
|---|---|
| Token Storage | Stored locally in chrome.storage.local β never sent to external servers |
| API Calls | Direct to api.github.com β no intermediary services |
| Data Collection | Zero telemetry, zero analytics, zero tracking |
| Open Source | MIT License β audit every line of code yourself |
| Manifest V3 | Modern security standards enforced by Chrome |
- Open Source: Every line of code is public on GitHub
- Local-First: All processing happens in your browser
- No Backend: We don't operate any servers that could collect data
- Reputable Team: Built by Gopenux, a Colombian company with years of enterprise experience
|
Modern Architecture
|
Optimized Performance
|
|
Comprehensive Testing
|
Security First
|
- Daily Runs: Automated tests every day at 2:00 AM UTC
- PR Validation: All pull requests tested before merge
- Auto Issue Creation: Failed tests create GitHub issues automatically
- Multi-Version: Tests run on Chrome Stable and Beta
Gopenux is a Colombian software development company with years of experience delivering high-quality enterprise solutions. We specialize in building tools that solve real problems for development teams.
Time tracking was a pain point in our projects. We needed:
- Seamless GitHub integration
- Multi-user reporting
- Zero data leakage
- Professional-grade quality
When we couldn't find a solution that met all requirements, we built it ourselves.
| Value | What It Means |
|---|---|
| π Open Source | MIT License β free to use, modify, and distribute |
| π Privacy First | Your data stays yours β we never collect anything |
| π Community Driven | We fix bugs and add features based on user feedback |
| π¨π΄ Made in Colombia | Proud to contribute to the global open source community |
Learn more about our work: gopenux.com
If CronoHub saves you time and improves your workflow, please consider supporting our development:
|
π Fix Bugs Faster Dedicate more time to addressing issues |
β¨ Add Features Develop requested functionality |
π Improve Docs Create tutorials and guides |
π Keep It Free Maintain the project for everyone |
Sponsors get:
- ποΈ Recognition in our README
- π Priority support for issues
- π£ Early access to new features
- π¬ Direct line to the dev team
Time entries follow this standardized GitHub markdown format:
β±οΈ **Time Tracked:** {hours} Hour(s)
{optional description of work performed}
---
<sub>Logged with CronoHub by Gopenux AI Team</sub>Why this format?
- β±οΈ Visual identification: Easy to spot in issue timelines
- π Report parsing: Consistent pattern for automatic aggregation
- πΌ Professional appearance: Clean, readable format
- π Transparency: Clear attribution to the tool
We welcome contributions from the community! Here's how you can help:
|
π Report Bugs |
π‘ Request Features |
π Improve Docs Submit documentation updates |
π§ Submit Code Create pull requests |
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Write tests for new functionality
- Ensure all tests pass (
npm test) - Commit your changes with clear, descriptive messages
- Push to your branch
- Open a Pull Request
Note: All PRs are automatically tested before merge.
# Clone repository
git clone https://github.com/Gopenux/CronoHub.git
cd CronoHub
# Install dependencies
npm install
# Run all tests
npm test
# Run specific test suites
npm run test:unit # Unit tests only (287 tests)
npm run test:e2e # End-to-end tests (49 tests)
npm run test:coverage # Generate coverage report
npm run test:watch # Watch mode for development
# Linting
npm run lint
npm run lint:fix
# Validate manifest
npm run validate:manifestCronoHub/
βββ manifest.json # Extension config (Manifest V3)
βββ background.js # Service worker
βββ content.js # Main UI & time logging
βββ reports.js # Reports module & API calls
βββ popup.html / popup.js # Extension popup & auth
βββ styles/
β βββ content.css # Panel & button styles
β βββ popup.css # Popup window styles
βββ icons/ # Extension icons (16, 48, 128)
βββ docs/
β βββ screenshots/ # README images
βββ tests/
β βββ unit/ # Unit tests (287 tests)
β βββ e2e/ # E2E tests (49 tests)
β βββ mocks/ # Reusable API mocks
βββ .github/workflows/ # CI/CD with GitHub Actions
MIT License β Copyright Β© 2026 Gopenux AI Team
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND.
| Resource | Link |
|---|---|
| π Company Website | gopenux.com |
| π¦ GitHub Repository | github.com/Gopenux/CronoHub |
| π Report Issues | GitHub Issues |
| π‘ Feature Requests | Request a Feature |
| π Sponsor Project | GitHub Sponsors |
| π§ͺ Test Documentation | tests/README.md |
Built with love by the Gopenux AI Team
Special thanks to:
- The GitHub team for the excellent API
- The Chrome Extensions team for Manifest V3
- The open source community for inspiration
- Our users for feedback and support






