What is the Joshu WakaTime connection?

Joshu connects to WakaTime through OAuth and reads the programming metrics, project durations, and language summaries logged by your editors. It tracks focus time, calculates engineering hours per project, verifies weekly deep-work goals, and connects development effort back to your client billing and sprint reviews. You work with an assistant who has a desk, a computer, and persistent memory, not another analytics tab to inspect for time tracking.

Is my WakaTime data secure?

Yes. Every Joshu runs in its own isolated, sandboxed cloud computer. Editor metrics, branch names, and coding duration data Joshu reads stay in that private sandbox. Joshu only accesses metrics you authorize, and your data is never used to train public AI models.

Will Joshu share my coding stats with team members without asking?

Joshu operates privately by default. Summaries of your coding time and project hours remain on your personal desk unless you explicitly direct Joshu to format a public team report.

What can Joshu access in WakaTime?

Only the WakaTime user account, organizations, and project metrics granted during OAuth authentication. Joshu cannot view file contents or keystrokes beyond the duration metadata captured by WakaTime.

What is the difference between WakaTime dashboards and Joshu?

WakaTime dashboards display passive charts of your editor activity. Joshu is an assistant with long-term memory across WakaTime, your calendar, QuickBooks, GitHub, and task managers. It correlates active coding hours with scheduled calendar blocks and drafts client time logs based on actual editor activity.

Do I need a paid plan?

Joshu is $95 a month with a simple flat rate. That includes your sandboxed cloud computer, a dedicated US phone number, an @joshu.me email address, eight-level cortex memory, and all tool connectors, including WakaTime. There are no surprise usage tiers or seat markups.

Home ConnectConnect Joshu to WakaTime

Connect Joshu to WakaTime

Connect WakaTime so Joshu can check coding hours, review language breakdowns, and track development focus across your projects.

WakaTime

“How many hours did I spend coding across projects in WakaTime this week?”

Joshu queries your active editor metrics, tallies hours across repositories, and drops a clear time breakdown on your desk.

“What was my top programming language by active editor time this month?”

Joshu analyzes your development statistics, compares language distributions, and quotes the exact percentage split.

“Summarize active development time spent on the client portal branch.”

Joshu aggregates editor sessions logged against the specific Git branch and reports total engineering time invested.

Editor metrics, active coding hours, and project focus time in WakaTime connect directly to your daily productivity reviews and client billing.

What Joshu does

Joshu reads your WakaTime activity logs to understand where your engineering time is spent. It summarizes deep-work hours across branches, highlights shifting language focus across sprints, and calculates engineering time spent on specific client repositories for accurate billing and retrospectives.

What you do

Connect your WakaTime account using OAuth and choose which projects or timeframes Joshu may inspect. Decide whether weekly coding summaries appear in your Friday recap or remain on call for ad-hoc reviews.

Why it sticks

Translating actual coding time into client invoices or sprint retrospectives usually requires guessing or manual time logging. Joshu pulls objective editor durations directly from WakaTime so your project time accounting stays grounded in reality.

Permissions and limits

Joshu accesses WakaTime using authorized OAuth tokens. It reads aggregated time metrics, project names, and language statistics within your approved account scopes. It cannot modify your logged time entries or inspect source code files through WakaTime.

Frequently asked questions

: Joshu connects to WakaTime through OAuth and reads the programming metrics, project durations, and language summaries logged by your editors. It tracks focus time, calculates engineering hours per project, verifies weekly deep-work goals, and connects development effort back to your client billing and sprint reviews. You work with an assistant who has a desk, a computer, and persistent memory, not another analytics tab to inspect for time tracking.
: Yes. Every Joshu runs in its own isolated, sandboxed cloud computer. Editor metrics, branch names, and coding duration data Joshu reads stay in that private sandbox. Joshu only accesses metrics you authorize, and your data is never used to train public AI models.
: Joshu operates privately by default. Summaries of your coding time and project hours remain on your personal desk unless you explicitly direct Joshu to format a public team report.
: Only the WakaTime user account, organizations, and project metrics granted during OAuth authentication. Joshu cannot view file contents or keystrokes beyond the duration metadata captured by WakaTime.
: WakaTime dashboards display passive charts of your editor activity. Joshu is an assistant with long-term memory across WakaTime, your calendar, QuickBooks, GitHub, and task managers. It correlates active coding hours with scheduled calendar blocks and drafts client time logs based on actual editor activity.
: Joshu is $95 a month with a simple flat rate. That includes your sandboxed cloud computer, a dedicated US phone number, an @joshu.me email address, eight-level cortex memory, and all tool connectors, including WakaTime. There are no surprise usage tiers or seat markups.