Rashol started from a personal need.

I kept seeing people share products they had built around their own workflows. Instead of adapting to another generic tool, they created something that fit the way they actually worked. Rashol came from that same idea.

I wanted a simple place to track projects, understand where my time was going, and share progress with clients without turning it into another administrative task.

As AI agents became part of my daily workflow, I wanted my time tracker to work with them too.

Connecting an agent to Rashol starts with a single command:

From there, agents can connect with projects and record activity directly. In the example below, I use Claude Code to interact with Rashol without leaving the development workflow.

I also wanted reports to be useful beyond simply listing hours.

Rashol lets me create shared reports and choose which information is visible. A client can receive a clear overview, while more detailed or private project data stays hidden.

Projects can include clients or collaborators through managed invitations. Everyone gets the context they need without exposing the entire workspace.

Rashol is still guided by the same principle that started it: build around a real workflow, keep the experience focused, and make the relationship between people, agents, and project data feel natural.