CC Break Monitor

Automatically tracks your active, break, and offline time on Command Center. Works on Firefox and Chrome.

Latest: v2.0.2
⚠️

Firefox users: Set auto-updates to "On"

After installing, go to about:addons → click CC Break Monitor → set "Allow automatic updates" to On (not "Default").

Why? "Default" relies on your browser's global update setting, which may be off in managed environments. Setting it to "On" ensures you always get the latest bug fixes and features automatically.

🦊

Firefox

v2.0.2 · Signed by Mozilla

Download .xpi

Click to install directly in Firefox.
Auto-updates are built in.

🌐

Chrome

v2.0.2 · Chrome Web Store

Install from Chrome Web Store

Click to open the Chrome Web Store listing.
Auto-updates handled by Chrome.

Optional — just your alias so I know who's using it

🙏 Thanks for downloading!

Let me know you grabbed it — helps me track adoption.

Features

⏱️

Auto-Detection

Detects status changes automatically by monitoring Command Center API calls. Zero manual input.

📊

Time Tracking

Tracks active, break, and offline time with second-level precision throughout the day.

🎯

Daily Target

Set your daily active time goal (default 7h 46m) and see remaining time at a glance.

Reset View

Zero the displayed timers without affecting stored data. View-only reset for a clean mid-shift starting point.

Theme Toggle

Switch between dark, light, and system themes. Click ◐ in the panel or configure in Settings.

🔄

Cross-Device Sync

Optional sync across browsers and machines via a self-hosted backend. Your data, your control.

📥

Export Reports

Download daily CSV reports or full JSON backups with one click.

📌

Dock or Float

Panel docks into the CC widget area or floats freely. Drag to reposition in floating mode.

🔒

Privacy First

All data stored locally by default. No analytics, no telemetry, no third-party services.

FAQ

What statuses are tracked?

Active: Available, Available - Live contacts, Profile Role, Internal Meeting, Personal Time, Project Work, System Issues, In Training, Mentoring, Interviewing, Sup Ops, Q+, PSAP, Deep Dive, Customer Meeting, After Chat, After Call, On Chat, On Call, Missed-Chat, Documenting.
Break: On Break, At Lunch.
Offline: Offline, Offline d, Error, Status Unavailable.
Unknown statuses default to Active — new CC statuses work without an update.

Where is my data stored?

All data is stored locally in your browser. Nothing leaves your machine unless you enable cross-device sync. Data persists across page reloads, tab closes, and browser restarts.

What does the Reset View button (↺) do?

It zeros the displayed timers without affecting stored data. Useful for a clean visual starting point mid-shift. The reset clears on page reload — your actual totals remain intact.

How do I change the theme?

Click the ◐ button in the panel header to cycle: dark → light → system. Or set it in Settings. The system option follows your OS dark/light preference.

Does it work across multiple tabs?

Yes. A single background script handles all tabs — each status change is recorded exactly once. All open CC tabs see the same data.

How much does sync cost?

$0/month. The CloudFormation stack uses API Gateway, Lambda, and DynamoDB — all within the AWS Free Tier for individual use. Data auto-expires after 90 days.

The time display shows wrong values.

This was fixed in v1.4.0. Make sure auto-updates are set to On (not "Default"): go to about:addons → CC Break Monitor → set "Allow automatic updates" to On. You can also force-check via the gear icon → "Check for Updates". If still wrong, reinstall from the latest .xpi above.

Installation Guide

1

Download the Extension

Click the "Download .xpi" button above. Firefox will prompt you to install.

2

Allow Installation

Click "Add" when Firefox asks for permission. The extension icon will appear in your toolbar.

3

Open Command Center

Navigate to command-center.support.aws.a2z.com. The Break Monitor panel will appear automatically.

4

Configure (Optional)

Click the toolbar icon → Settings to adjust your daily target or enable cross-device sync.

5

Enable Auto-Updates (Important!)

Go to about:addons → click CC Break Monitor → set "Allow automatic updates" to On.

⚠️ Don't leave this on "Default" — in managed environments, the global setting may be off, which means you'd silently miss updates.

1

Open the Chrome Web Store Link

Click the "Install from Chrome Web Store" button above, or go directly to: Chrome Web Store listing. This is an unlisted extension — it's only accessible via direct link.

2

Add to Chrome

Click "Add to Chrome" and confirm the permissions. The extension icon will appear in your toolbar.

3

Pin the Extension (Recommended)

Click the puzzle icon in Chrome's toolbar → find "CC Break Monitor" → click the pin icon to keep it visible.

4

Open Command Center

Navigate to command-center.support.aws.a2z.com. The Break Monitor panel will appear automatically.

5

Configure (Optional)

Click the toolbar icon → Settings to adjust your daily target or enable cross-device sync.

6

Auto-Updates

Chrome updates extensions automatically every few hours. No action needed.

Chrome: Manual install (developer mode) — if Chrome Web Store is not available
1

Download the Extension Files

Get the extension folder from your team (or clone the repo).

2

Enable Developer Mode

Go to chrome://extensions/ → toggle "Developer mode" (top right).

3

Load Unpacked

Click "Load unpacked" → select the Chrome-Extension/CC-StatusChange folder.

4

Note

Unpacked extensions don't auto-update. You'll need to manually reload when a new version is available.

Why deploy your own? The sync backend runs in YOUR AWS account. Your data stays under your control. No shared infrastructure, no dependency on anyone else's account. If you don't need cross-device sync, skip this — the extension works fully offline.
1

Get an AWS Account

Use your personal Isengard account or any AWS account you have access to. The stack uses only free-tier eligible services (API Gateway, Lambda, DynamoDB) — effectively $0/month for individual use.

2

Launch the CloudFormation Stack

Choose your preferred method:

Option A: One-Click Launch
🚀 Launch Stack in AWS Console Opens AWS Console with the template pre-loaded. Select your region and click "Create stack".
Option B: AWS CLI
aws cloudformation deploy \
  --template-file cloudformation.yaml \
  --stack-name cc-monitor-sync \
  --capabilities CAPABILITY_NAMED_IAM \
  --region ap-southeast-2
Download the template first: cloudformation.yaml
3

Wait for Stack to Complete (~2 minutes)

The stack creates: 1 API Gateway, 1 Lambda function, 2 DynamoDB tables, 1 IAM role. Status will show CREATE_COMPLETE when done.

4

Copy the API URL from Stack Outputs

Go to CloudFormation → Stacks → cc-monitor-sync → Outputs tab. Copy the SyncApiUrl value. It looks like:

https://abc123def.execute-api.ap-southeast-2.amazonaws.com/prod

Or via CLI:

aws cloudformation describe-stacks \
  --stack-name cc-monitor-sync \
  --query "Stacks[0].Outputs[?OutputKey=='SyncApiUrl'].OutputValue" \
  --output text
5

Configure the Extension

In the extension: click toolbar icon → Settings → scroll to Cross-Device Sync:

  • Paste the API URL from step 4
  • Enter your Amazon alias (e.g., bhaskern)
  • Check "Enable sync"
  • Click "Save Sync Settings"

The extension will validate the API URL and show 🟢 Connected if successful.

6

Verify It Works

Open Command Center on two different browsers or machines. Change your status on one — the other should pick it up within 30 seconds.

What gets created in your account:
ResourceTypeCost
cc-monitor-sync-prodDynamoDB Table (on-demand)Free tier
cc-monitor-config-prodDynamoDB Table (on-demand)Free tier
cc-monitor-sync-prodLambda FunctionFree tier
cc-monitor-sync-prodHTTP API GatewayFree tier
cc-monitor-sync-lambda-prodIAM RoleFree

Total estimated cost: $0.00/month for typical individual use (well within free tier). Data auto-expires after 90 days via DynamoDB TTL.

To remove everything:
aws cloudformation delete-stack --stack-name cc-monitor-sync --region ap-southeast-2

This deletes all resources. Your local extension data is unaffected — only sync stops working.