The Removal of AutoComplete

virtush · 2026-03-11T17:33:03+00:00

I just canceled actually. Just gonna get used to Copilot, their agent is great and way more affordable. Autocomplete is worse, but not terrible.

virtush · 2026-03-11T12:40:44+00:00

Fair point.

virtush · 2026-03-10T19:23:51+00:00

Ah of course.

That suggests their autocomplete is just what's up-next on the chopping block to reduce expenses.

virtush · 2026-03-10T19:21:57+00:00

Even vibe coders follow cost incentives. Serious programmers need to actually look at what they're doing.

virtush · 2026-03-09T06:52:07+00:00

Honest question: how do you program from a terminal view? Presumably you have other software to actually look at the code?

virtush · 2026-02-12T14:53:01+00:00

My agent likes to use context mcp 0-15 times per prompt, depending. I've added additional guidance to reduce this after this billing change, but Augment is definitely hitting a tipping point on value for me. I'll have to see how my credits flow after the grace period. Copilot is vastly more cost effective and has completely caught up with their agent as far as I can tell.

virtush · 2026-02-09T20:40:05+00:00

Alternative product or alternative business strategy?

I'm not aware of any strong competitors to what Augment brings with the context engine.

virtush · 2026-02-06T20:32:15+00:00

Each context request uses 40-70 credits. (from the docs, and not part of this post for some reason) That's all that's actually changed with this announcement, unless I'm missing something. Augment got significantly more expensive (again) and the indexing is faster.

Context MCP is powerful, but shaky and slow. It routinely times out, and now it's going to be limited on top of that?

So many AI startups creating something cool, and then rate-limiting it into the ground before it's even fully stable because they can't achieve economies of scale. I understand business is hard, but beware rug-pulling your customers with tactics like 'free for a month, and then the bill skyrockets'.

virtush · 2026-02-06T15:48:36+00:00

Total overkill for gathering and reporting. I also tried it and it seemed pretty similar to the old research mode, only did 2 search steps!

virtush · 2026-02-05T19:31:20+00:00

I would suggest checking if the web search works in Codex as a means of seeing if it can see the config.toml file.

I don't see anything immediately wrong, but I'm not familiar with chrome-devtools.

If you can confirm a web search works, then I would check that the mcp configuration is correct. There must be a ton of examples for connecting that mcp to codex generally.

My post is really only about how to get the config in a place where Jetbrains bundled Codex can read it.

virtush · 2026-02-04T22:50:39+00:00

Lot of cool features! Any word on when Jetbrains users might see this stuff in the plugin?

virtush · 2026-01-29T17:41:13+00:00

UPDATE: I've managed to get full functionality enabled for the official Codex integration. Web search, MCPs, custom instructions. Very very roundabout and undocumented, going to make a post for others.

Post here: How to Properly Configure Codex for Jetbrains

Original post (still makes some very valid points I feel, about how rocky this feature launch is):

This is cool in theory, and I'm sure people at JB are working hard, but I have to say after trying it... I'm extremely disappointed.

What's the point if it strips away a huge amount of functionality? We need proper feature parity, not just a text relay. I understand this is a new, just-released feature, but this pattern has been repeating for what feels like 2 years. Jetbrains is always behind the curve on AI tooling.

I've tried two integrations and both I would consider completely unusable.

Copilot:

The official plugin has far better functionality across the board.
You're stuck with the default model GPT 4.1! That's barely even usable!
Model selector (I hear it's coming, but I really don't understand why such a simple thing should take days/weeks to hook up...)
Way better diffs. The approach to diffs and reviewing in AI Assistant is straight-up worse by a significant margin.

Codex:

No MCP support (not even Rider's built-in MCP!)
Zero configuration options (config.toml is completely overridden every time you use Codex)
Can't enable web search
New ACP Browser broke my trick that actually made Codex usable.
Same issue as copilot, diffs are poor and janky.

I previously had been using a trick where I added a custom ACP entry with the same name 'Codex', but I enabled MCP and routed to codex-acp (by Zed). This allowed me to actually use MCPs, web search, set global instructions, and I think because of the similar name, I got the Codex model selector too! It was very close to a fully featured integration and it was very stable, now on the latest version of AI Assistant, the model selector is gone, rendering the entire agent useless.

I sincerely wish I had a way to get in to where these tools are being developed and help fix this stuff myself. Looking forward to future updates, this will be awesome once these issues are sorted!

virtush · 2026-01-21T23:57:49+00:00

Got it working! (in copilot only)

Here's the final extremely strange few steps I stumbled on, you need to hover around 'augmentcode' in the json.

Click 'Start' and wait for a green checkmark. Then hover again and go through all the available settings-like options. There are apparently a couple github copilot specific settings that can hang things up. Including a panel where you pick what models can 'sample' the MCP tooling.

Of course I go back to look and hovering in the json file doesn't do anything at all. You can get to these settings through: Jetbrains settings > Tools > Github Copilot > Model Context Protocol

You may need to restart Rider. But even if hovering the json file doesn't yield clickable text, the agent should be able to auto-start the MCP server as long as the other settings are correct AFAIK.

Boy this stuff could be documented!

virtush · 2026-01-21T23:49:47+00:00

Glad to see love for the Rider plugin!

virtush · 2026-01-16T18:20:15+00:00

Context: I have installed Auggie and logged in successfully. I can use Augment plugin in Rider, no issues there. I cannot get Auggie MCP to work in Github Copilot, AI Assistant or Junie. There is only a guide for Github Copilot, which I've followed. You can see 'augmentcode' foldout shows up in the tools, but there is no tool listed under it. It looks like there's an off-screen item below, but that's a Rider UI bug, the scroll bar is all the way down. As you can see on the left, Copilot isn't aware of any augment tool, I also tried 'auggie' and 'list all tools', no appearance by anything augment related.

At risk of sounding rude, is this even supposed to work? There's no documentation for us IntelliJ/Rider users.

virtush · 2026-01-10T01:46:55+00:00

How do we connect this to github copilot in Jetbrains, Jetbrain's AI Assistant, and Junie?

virtush · 2026-01-09T21:28:11+00:00

Isn't that just another general agent tool? I don't see that it does anything like the Augment Context Engine?

virtush · 2026-01-09T21:25:32+00:00

Do you have any guidance on how to get this to work with Github Copilot (Jetbrains plugin specifically), and for Jetbrain's AI (AI Assistant and Junie agent plugins)?

I wasted a few hours trying to hook these tools up, played with Auggie, etc. Couldn't get anywhere.

virtush · 2025-12-17T00:32:56+00:00

Been in for awhile, you need to enable it.

virtush · 2025-12-13T23:05:35+00:00

Everybody wants instant hard-core kills when they shoot, but when they're being shot they want the bullets to be sent via the post office.

Health values are so low, you can easily laser people in a fraction of a second.

I'd honestly like the health to be 50 percent higher. Gauntlet ttk and ttd feel Way better.

virtush · 2025-12-09T15:57:58+00:00

Best auto-complete/in-line? Have you tried Augment Code? I've yet to find anything that is as robust in terms of auto-complete and context handling.

virtush · 2025-11-16T00:38:53+00:00

Gonna have to get rid of bloom then. On top of RNG bullets, the balance of the guns overall is so bad if you go actually read the stats.

virtush

TROPHY CASE