Malleable for Developers
Your agents file the tickets and track the time.
You review.
Malleable is the board and the clock your coding agent can write to: the mal CLI, MCP for Claude Code and Claude Desktop, and a V1 API. Hours land by project, tickets by branch, and deep work blocks hold on your calendar.
Context switching is the real bug.
A standup notification. A Slack ping. A calendar invite for a meeting that could have been a message. By the time you're back in the code, 45 minutes are gone and you've lost the thread.
Deep work requires defended blocks of time. Most calendars don't defend anything. They just fill up.
Protect the hours that count.
A board and clock your agent writes to
Your Claude Code session files tickets, attaches commits and starts the tracker through the mal CLI or MCP. Every entry records who did it and from where, so the board stays yours to review.
AI calendar blocking
Tell Malleable what you're building. It finds the open time and blocks it before meetings can fill the gaps. Deep work by default.
Project buckets
Organize time by repo, feature, or client. See exactly how many hours went into each project, useful for estimates, retros, and billing.
One-tap timers
Start tracking without leaving your flow. Assign hours to the right project and stop guessing at week-end timesheet reconciliation.
Google Calendar sync
Bidirectional sync. What's in your calendar reflects reality, and what you log in Malleable shows up where you already look.