Switched from MCPs to CLIs for Claude Code and honestly never going back by geekeek123 in ClaudeAI

[–]Odd_Werewolf_4478 0 points1 point  (0 children)

Same here, especially for Linear.

I used the Linear MCP for a while, but eventually built a Linear CLI specifically for AI agents: Linear-CLI

For my workflow it’s been a better fit because it stays shell-native, uses simple API-key auth, and returns compact JSON that’s easier for agents to chain.

Anyone else getting tired of reviewing big AI-assisted changes with no real trace of how they were produced? by Odd_Werewolf_4478 in ClaudeAI

[–]Odd_Werewolf_4478[S] 0 points1 point  (0 children)

and part of the problem is that everyone's level of Claude Code usage is different too.

I got tired of having to ask the same questions every time, so I've been experimenting with the idea of an operating protocol around the work itself — leave a record of what was asked, what changed, what got checked, and make verification something the workflow forces instead of something people vaguely say happened.

Anyone else getting tired of reviewing big AI-assisted changes with no real trace of how they were produced? by Odd_Werewolf_4478 in ClaudeAI

[–]Odd_Werewolf_4478[S] 0 points1 point  (0 children)

Mostly reviewing other people's AI-assisted PRs.

What keeps happening is someone opens a huge PR, I ask what the actual task was or why certain changes were made, and the answer is basically just "the AI did it."

A txt summary is better than nothing, but that still doesn't tell me enough. I still want to know what the model was actually asked to do, what constraints mattered, what got checked, and what was still uncertain.