How does Buildermark handle code formatting differences when matching agent diffs to commit diffs?
Buildermark utilizes a formatting-agnostic matching system. This means it's designed to be robust against common issues like auto-formatting and code reorganization, ensuring accurate attribution of agent-written code even if the formatting changes between the agent's output and the final commit.
What is the purpose of the 'Conversation ratings' feature, and how does it work?
The 'Conversation ratings' feature allows users to provide feedback on their interactions with coding agents. You can manually rate your coding agent conversations, or the agent itself can log feedback. This helps in comparing how different coding agents perform and understanding their effectiveness in various projects.
Since Buildermark runs locally, how will teams be able to aggregate AI code metrics across multiple developers?
For teams, a 'Team Server' is planned as a future paid, self-hosted solution. This server will allow organizations to aggregate Buildermark data from individual developers, providing a centralized view of AI code metrics across the entire team or organization.
Which specific coding agents are currently supported for importing chat history?
Buildermark currently supports importing chat history from Claude Code CLI, Claude Code Cloud, Codex CLI, Codex Cloud, Gemini CLI, and Cursor. Users can also file feature requests for additional agent support.
What is the technical architecture of Buildermark running on a local machine?
Buildermark operates as a local desktop application where an app container manages a Go server on localhost. This Go server then serves the web user interface, typically accessible at http://localhost:55022. This architecture ensures that all processing and data storage remain on the user's machine.