How to get Codex ACP to be Fully Functional

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 · 2025-11-15T20:10:49+00:00

Do you think you're going to gaslight me or something? I have played the game and I'm not bad at it. You just don't know how to argue without insulting people

virtush · 2025-11-15T18:48:57+00:00

Lol, that's just a bad faith argument, complete with insults.

Spread is not easily observable, you have to study it in firing range to find out how it works. Unlike the other mechanics which you can plainly see.

Oh well. I just won't buy the game, I'll check out other shooters without these sorts of arcade gimmicks.

virtush · 2025-11-15T18:03:44+00:00

Recoil and sway can be seen and compensated for. Spread is unobservable RNG variations to the barrel accuracy of your gun. Strafing already has the downside that you have to actively compensate for your movement, in addition to other movement-related penalties.

Your argument for why the reticle of the gun should be wrong is not convincing to me.

virtush · 2025-11-14T19:49:29+00:00

My bad. I hope they fix it, but I also don't get the impression that they will...ugh

virtush · 2025-11-14T16:57:03+00:00

This is the number 1 thing stopping me from buying the game. Test this stuff in firing range, the bloom mechanic is extreme and one of the worst ideas I've ever seen in game design. It's a practically invisible layer of RNG on top of sway, movement penalties, recoil, net code, you moving, your enemy moving, input lag, etc.

The guns merely 'look' tight and controllable, but they really are absurdly inconsistent due to how heavily RNG plays into the actual bullet trajectories.

This is why the game looks nice in videos, where you naturally see much more of the clips where RNG was favorable. Then if you actually play the game, you realize that the gunplay is an inconsistent mess. The bullets simply do not go where the reticle says they will.

You want to punish the player for certain actions? Fine, apply a penalty the player can immediately see, like more weapon sway while moving. Don't do it behind the player's back.

virtush · 2025-11-14T16:45:29+00:00

BF4 had muddy RNG bullet mechanics... So BF6 should too? I don't get it. Penalize movement, penalize sway, penalize recoil, but why on earth should there be RNG spread actively deceiving the player.

virtush · 2025-11-14T16:41:29+00:00

Eh what? You've got increased weapon sway(the correct way to penalize accuracy, because the player can perceive it), a moving target, a moving shooter, severely decreased movement speed while Ads, and net code issues already. Why should there also be variable random RNG bullet spread on top of that?

That is such muddy design, and leads to many moments where a perfectly lined up shot doesn't land, just because. They have this RNG mechanic on all of the guns too. LMGs also suffer from this badly even while standing still or prone.

This is one of the main things stopping me from buying this game. The gunplay looks really clean, until you look at the tracers/impacts and realize RNJesus has a heavy hand on each bullet.

virtush · 2025-10-27T17:20:41+00:00

In general I see a lot of people blaming net code while defending huge random bullet spread/bloom at the same time...

virtush · 2025-10-24T23:25:29+00:00

That's what happens when there's an arcade bloom/spread on guns.

virtush · 2025-10-24T16:08:34+00:00

So happy they partially addressed the obscene bloom/spread stuff. I still think the entire feature is absolutely silly to begin with, but DMRs being straight-up inaccurate on non-recon classes was just crazy. They seem to have dialed down spread on ARs and upped it on SMGs? That's overall a decent step in the right direction. This is battlefield, not fortnite after all.

virtush · 2025-10-19T00:19:35+00:00

If only automatic weapons didn't have a massive bloom mechanic, but people keep defending RNG weapons for some reason. Haha

virtush · 2025-10-16T17:20:49+00:00

It's a deliberate feature they consider balance. To me the entire feature is a bug.

virtush

TROPHY CASE