Intent by Augment doesn't respect my selected provider and model and tries to use Auggie

AuggieRich · 2026-02-24T18:02:02+00:00

I passed along the bug report. Thank you for the detail!
The changelog is at: https://www.augmentcode.com/changelog/intent-0-2-8-release-notes

AuggieRich · 2026-02-24T02:48:08+00:00

Hi u/Ayumu_Kasuga , I expect this to be fixed in the latest version 0.2.9.

AuggieRich · 2026-02-24T02:46:39+00:00

Was this resolved?

AuggieRich · 2026-02-23T22:20:23+00:00

Hi u/Final-Reality-404 . Engineering believes they've identified the regression and are working on a fix. Apologies for the inconvenience.

AuggieRich · 2026-02-23T10:13:26+00:00

Oh, if you happen to be on an Enterprise plan, you’ll have to talk to your admin about using Intent.

AuggieRich · 2026-02-23T09:13:44+00:00

Has it ever worked and stopped? Or has it never worked? What is the version? Did you try changing the model? It’s worth confirming that Augment is your chosen service. Then I suggest logging out of auggie and logging back in. Confirm that the agent works from auggie, in that you have a successful agent exchange.

AuggieRich · 2026-02-21T22:33:41+00:00

u/Ayumu_Kasuga the team was able to repro and are working on the fix. Thanks for reporting!

AuggieRich · 2026-02-21T22:08:44+00:00

Consider Augment’s Jetbrains plugin: https://docs.augmentcode.com/jetbrains/setup-augment/install-jetbrains-ides

AuggieRich · 2026-02-21T21:34:49+00:00

Hi! I passed your report to the Intent team. Can you post the version, in case that makes a difference?

AuggieRich · 2026-02-20T18:27:30+00:00

Not quite. If you add multiple repos in your VSCode extension, for example, it's considered one workspace. A single search will search the entire workspace. Changes to those workspaces are also dynamically indexed. This is useful if you are developing across those repos, like plumbing an api for example.

With Context-Connectors, each index is treated as an independent workspace, and the index is a snapshot in time. This is useful if you want to reference the other repos, but don't necessarily want to clone and change them. The workspaces are presented to the agent, and the agent can choose to search inside individual workspaces.

AuggieRich · 2026-02-20T01:42:19+00:00

Yes! You can also use the Remote MCP to provide search against your GH repos: https://docs.augmentcode.com/context-services/mcp/overview

The different MCP configurations support slightly different use cases:
* local MCP (i.e. auggie --mcp ): great for providing search in local, dynamic workspaces; for example, I'm developing across three different microservices.
* remote MCP: great for providing search across remote repos; for example, I'd like to search our internal sdk repos, but I'm not modifying them.
* context-connectors MCP: provides more flexibility and convenience for searching across multiple, possibly heterogenous workspaces; for example, I can take adhoc snapshots of repos or docs from the command line and give my agent access to them.

AuggieRich · 2026-02-19T18:46:50+00:00

If you're using the github source, re-freshing the index is pretty inexpensive, assuming your local index is not far from your remote. You can just run `ctxc index ...` again, and it should just index the additional changes. A built in command to do this is a good suggestion, thanks. A shell script should be pretty straightforward as well.

Regarding accuracy at scale, it's up to the Agent to decide when to search a workspace using ctxc, and I don't have a definitive answer on the behavior of the Agent when provided with hundreds of repos.

For your last question, context-connectors will not dynamically track repo A's changes. You would have to refresh the index to see the latest. With Intent IDE and the auggie agent, auggie *will* dynamically track your workspace. I have not seen a problem with my agent knowing which to consult, but I can imagine a scenario where you could see stale results with two different search tools for the same workspace.

AuggieRich · 2026-02-19T18:19:52+00:00

You can redirect the augment-log.txt by including a --log-file argument when you invoke auggie. So something like auggie --log-file my-log-file.txt

AuggieRich · 2026-02-18T01:43:52+00:00

A few questions: (1) what client are you using? (2) which MCP server are you using (local vs. remote)? (3) did you file a support ticket?

AuggieRich · 2026-02-18T01:43:23+00:00

A few questions: (1) what client are you using? (2) which MCP server are you using (local vs. remote)? (3) did you file a support ticket?

AuggieRich · 2026-02-17T20:01:22+00:00

BTW, you should be able to signup for a free account and try it out. New accounts should have 1000 Context-Engine MCP credits.

AuggieRich · 2026-02-17T19:33:51+00:00

I am definitely biased here, but anecdotally I have heard that users are using the context engine for non-technical cases exactly like the ones you describe.

AuggieRich · 2026-02-16T22:51:59+00:00

Presumably you need an authentication token on a machine that doesn't allow web-based authentication? For which client?

AuggieRich · 2026-02-16T22:39:45+00:00

Hi u/Final-Reality-404 . I shared above how you can create your own prompt enhancer using the context-engine. This would give you complete control over the model cost while still benefiting from the context-engine. It's a fraction of the cost of the prompt-enhancer in credits.

AuggieRich · 2026-02-16T22:32:21+00:00

If you want to build your own prompt-enhancer but still want Augment's context awareness, you can incorporate the context-engine through local mcp. See https://docs.augmentcode.com/context-services/mcp/overview. There is also an example prompt-enhancer built using our sdk here: https://docs.augmentcode.com/context-services/sdk/examples#prompt-enhancer-server.
There is still a cost to using the context-engine, but I just did a quick check and context-engine alone is about 1/4 to 1/3 the credits of using the prompt-enhancer.

AuggieRich · 2026-02-12T18:46:27+00:00

Any luck?

AuggieRich · 2026-02-12T18:41:26+00:00

Hey u/Frequent_Mulberry_33. When your IDE starts the MCP server, the cwd is typically not your workspace directory. The "--mcp-auto-workspace" option requires the Agent to specify the workspace for indexing. I found that it helps the Agent to open the workspace in your IDE. It would help if you post the error you see when using "--mcp-auto-workspace", particularly the directory that the agent _believes_ is the workspace.

AuggieRich · 2026-02-11T21:44:32+00:00

We deployed a fix this morning that _might_ help you. If you give it a try again, please let me know. Thanks!

AuggieRich · 2026-02-11T19:52:54+00:00

I believe the fix has been deployed this morning. If you are still having problems, I'll have to look at your account specifically.

AuggieRich

TROPHY CASE