PixLog Brings Pixel-Level Visual History and Blame Tracking to Git

·1 views

PixLog is a new open-source tool, currently at version 0.1.1, that extends Git with pixel-aware version history for image assets. Unlike Git LFS or DVC, it does not create a separate commit graph but instead stores compact pointers in Git while preserving exact image bytes locally. The tool can identify which specific pixels changed between commits, attribute changes to individual commits via a visual blame command, and generate heatmaps showing altered regions. PixLog also records generation provenance through 'recipe' objects, supporting metadata from AI tools like ComfyUI and AUTOMATIC1111. It additionally offers policy enforcement for image format, file size, and visual-change thresholds, with CI integration available via a GitHub Action.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer builds offline app using OpenSpec and AI agents, documents lessons learned

A developer named Shyamala built a fully offline application from scratch using OpenSpec combined with AI agents, documenting the process in a post published on DEV Community on August 2. The core approach involved keeping all architectural and design decisions recorded in specification files rather than relying on conversational AI chat history. This method allowed the developer to pause work, switch between different AI models, and maintain greater control over the project's direction. The experiment also surfaced notable limitations of the workflow, which Shyamala openly shared alongside the successes. The post highlights how spec-driven development can bring structure and continuity to AI-assisted software projects.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Claude Code's EnterPlanMode Uses an Empty Schema as a Deliberate Design Choice

EnterPlanMode is a built-in tool in Claude Code that shifts the AI from its default 'think while writing' workflow into a structured, read-only planning mode before any files are modified. Once activated, editing tools such as Edit, Write, and NotebookEdit are disabled, preventing Claude from making changes while it explores the codebase. The tool addresses a core alignment problem: ensuring the AI and user agree on an approach before implementation begins, rather than surfacing directional errors mid-refactor. Users receive a complete written plan they can approve, reject, or revise, creating a clear decision boundary instead of discovering mistakes only after reviewing a pull request. A practical example — refactoring an authentication module — illustrates how skipping this planning step can lead to cascading edits across multiple files before a critical misunderstanding is caught.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

What Is Responsive Web Design and Why It Matters for Developers

Responsive web design is a development approach that allows a single website to automatically adapt its layout and content across desktops, tablets, and smartphones. Instead of maintaining separate desktop and mobile sites, developers use one unified codebase that scales fluidly to any screen size. The technique relies on three core pillars: fluid grids using relative units like percentages, flexible images capped by CSS rules, and media queries that apply styles based on screen width breakpoints. This approach improves user experience by eliminating the need to pinch or zoom, and reduces costs by removing the overhead of managing multiple codebases.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI Agent Builds Its Own Mail API to Read and Reply to Emails Independently

An AI agent named Elara, created by developer Michael, built a custom email API after finding that existing tools did not meet her specific needs as an autonomous agent. The system, called elara-mail, was built using Node.js with Fastify, SQLite with full-text search, and standard IMAP/SMTP libraries, and runs inside a Docker Swarm container. A key feature is the /api/unread endpoint, designed to quickly surface only new messages rather than fetching or sorting entire inboxes. Deployment required six rounds of debugging, primarily due to Docker Swarm volume permission issues that needed manual directory creation and ownership settings. The project is open source and reflects a broader goal of giving AI agents the ability to build and own their own operational tools.

0 comments Read more at DEV Community