MCP shouldn't be 1-1 to API. It should empower users and LLMs to perform tasks and see data.

CLIs don't improve upon that issue if they're designed the same way people are implementing MCPs.

I built it because I often am running multiple Claude sessions and miss when a session is waiting on me to proceed.

Comments URL: https://news.ycombinator.com/item?id=47353353

Points: 3

# Comments: 0

Imbi is our operational source of truth. As an open-source system, it maps every project, service, database, and dependency into an interconnected graph. It tracks technical debt, enforces standards, and serves as a single control plane for configuration, project state, deployments, and operational change.

Imbi Automations leverages this graph to target projects by language, version, or type, executing workflows that combine AI with traditional tooling to enforce consistency at scale. It updates project metadata, identifies deficiencies, and monitors compliance with our standards.

We've used Imbi Automations to:

- Migrate several hundred projects from GitLab to GitHub, automating the transition from GitLab CI to GitHub Actions. Finish our Python 3.9 to 3.12 migration by updating all projects to use the latest syntax, tooling, and project standards.

- Scan all projects leveraging Claude Code, creating comprehensive AGENTS.md files for every project to ensure Agent readiness to work on project related tasks.

- Automate the scanning of our projects for standards compliance, updating Imbi project facts with the results.

- Update base Docker images across all projects in minutes instead of months.

What we're focused on next:

- Python 3.14 upgrade (January 2026): one to two sprints instead of months

- JavaScript → TypeScript: bulk migration instead of individual rewrites

- AWS infrastructure, security scanning, automated incident response: all candidates for AI-driven workflows

- Standards compliance: continuous reporting and remediation

Comments URL: https://news.ycombinator.com/item?id=45476073

Points: 2

# Comments: 0

For those asking, it's about the "VitualBox 6.1.32 Oracle VM VirtualBox Extension Pack" - it's free to install but phones home and they reach out after a year or two of use and attempt to coerce you into paying for a license. Just ensure everyone has uninstalled it and tell them to go pound sand.

"yapf -i --style=pep8" works great.

I figured yapf was not "new" which is why black won.

Starting about 5-6 years ago there was a push in the Python community to replace solved problems with new ones in what appears to me as chasing the JavaScript community.

Instead of consolidating on existing tools that worked well but had some rough edges to smooth out, numerous projects came about to reinvent the wheel.

As a result, my wife and I were able to move, though we did the opposite of what you're considering. Having been in the burbs for the last 28 years of my life, we made the switch to move to the city. Sold our house during the very hot market and bought a condo in the city. We're almost a year in and loving it.

It's the team who built an open-source editor at GitHub and they are building a new editor. Cool... I want to check it out.

Signup for a waitlist? Login? Seems like they're building a business around an editor... Cool, we have a number of those. I'll wait to see when they have a product I can evaluate instead of when they're talking about what they're going to do.

pip + setuptools using setup.cfg works very well.

It seems to me the Python packaging community is chasing the nodejs community for very little value and a lot more added complexity and very little regard to the community and package maintainers in general.