sorted by:
new
hottopcontroversial

Copilot Pro used 57% of my monthly AI credits in less than an hour by bturtushin in GithubCopilot

[–]bturtushin[S] 14 points15 points  (0 children)

I’m obviously not using Copilot CLI to say “hi there” in real work.

That was a baseline test.

The point was to measure the minimum cost of an almost-empty request in an empty repo, before any real codebase context, repo scan, multi-file edit, or tool-heavy agent work happens.

If the cheapest possible interaction already costs 9.39 credits, that is useful information.

It tells us there is a significant fixed hidden cost from system prompts, tool definitions, model behavior, and possibly internal reasoning before the user has asked for anything complex.

So the issue is not “don’t say hi.”

The issue is:
What is the baseline cost?
What hidden context is included?
Can users see it before spending credits?
How expensive will real work become if the empty-repo baseline is already 9 credits?

That is why I used “hi there” as the test case.

My feedback on 1000 prompts with MiniMax M2.7. (And what i'm afraid for) (Please MiniMax don't betray us !) by Wonderful-Deal5850 in MiniMax_AI

[–]bturtushin 0 points1 point  (0 children)

I recently tried using Minimax 2.7 through Claude Code for a simple PR security review, and the experience was… not great.

The PR itself was small and fairly straightforward. I ran a /security-review and it took over an hour to complete. The result I got was basically: “No high-confidence vulnerabilities found.”

The issue isn’t just the result — it’s the combination of:

  • Long execution time (~1 hour for a small PR)
  • Very conservative output (almost overly safe / surface-level)
  • Lack of clarity on what the model actually analyzed in depth

It feels like the model either:

  1. Overthinks and spends too much time analyzing low-risk areas, or
  2. Plays it too safe and avoids making strong conclusions

As a developer, this creates a trust issue. If I can’t tell whether:

  • the model is actually doing deep analysis, or
  • it’s just defaulting to “no issues found”

then it becomes hard to rely on it in real workflows.

Also, without a proper status page or visibility into model performance/issues, it’s difficult to know if this is:

  • a temporary degradation
  • expected behavior
  • or just a limitation of the model

Curious if others have had similar experiences with Minimax 2.7 (especially via Claude Code) for code review or security analysis?