Install xcsift with Homebrew

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• xcsift

Project history

The repository was created on 2025-07-10 and shipped its first release, v1.0.1, the same day. The README states the core distinction plainly: unlike xcbeautify and xcpretty, xcsift prioritizes information density and machine readability over human-oriented terminal formatting.

The project grew with features that mirror the needs of agentic coding sessions and CI logs: JSON and TOON output, structured compiler and linker errors, test-failure extraction, coverage conversion from .profraw and .xcresult data, build timing, GitHub Actions annotations, and a .xcsift.toml configuration file. Its 2026 releases continued to harden parsing, including a v1.3.1 fix to avoid reporting failed or truncated builds as success.

Adoption history

Because xcsift is new, adoption history is mostly early ecosystem positioning rather than long-term usage. Its README and plugin files explicitly target Claude Code, Codex, Cursor, CI, and LLM consumption; a third-party MCP wrapper also appeared to expose xcsift output through the Model Context Protocol.

The author's blog post about not letting agents read whole xcodebuild output frames xcsift as part of a wider shift from human-pretty logs to machine-parseable summaries. That makes the project notable even while its conventional package history is short.

How it is used

Typical usage pipes xcodebuild build, xcodebuild test, swift build, or swift test through xcsift with stderr captured. Users can choose JSON, TOON, or GitHub Actions output, enable coverage extraction, treat warnings as errors, exit on failures, or initialize a .xcsift.toml template for project defaults.

The tool is most useful where raw build logs are too verbose for an AI assistant or CI annotation stream. It extracts the file, line, target, warning, error, test, coverage, and timing facts an agent needs without spending context on the entire build transcript.

Why package nerds care

xcsift is package-nerd significant as a sign of the coding-agent era entering Apple-platform tooling. Where xcpretty and xcbeautify made xcodebuild pleasant for humans, xcsift optimizes the same stream for token budgets, structured parsing, and automated remediation loops.

Timeline

• 2025-07-10: Repository created on GitHub.
• 2025-07-10: v1.0.1 first public release.
• 2026-03-22: v1.2.0 release published.
• 2026-05-22: v1.3.0 release published.
• 2026-06-16: v1.3.1 fixed parsing issues around runtime noise and truncated failed builds.

Related projects

• xcbeautify and xcpretty are direct comparison points because they format xcodebuild output for humans, while xcsift targets agents and machine-readable formats.
• xcsift-mcp is a related wrapper that exposes xcsift to AI assistants through MCP.

Sources

• https://github.com/johnnyclem/xcsift-mcp
• https://github.com/ldomaradzki/xcsift
• https://github.com/ldomaradzki/xcsift/blob/master/plugins/codex/SKILL.md
• https://github.com/ldomaradzki/xcsift/releases
• https://ldomaradzki.com/blog/stop-wasting-context-build-output
• https://ldomaradzki.github.io/xcsift