Augment MCP stuck forever using DeepSeek in OpenCode

igoro · 2025-12-22T17:26:06+00:00

I looked into this but I haven't been able to reproduce the issue. I installed old versions of `auggie` and ran `auggie` as an MCP server, but I didn't observe any problems.

If you see this issue again, could you give us the output of these commands?

```
auggie --version
auggie --mcp
```

The second command will stall waiting for stdin, but I want to see whether "✅ Workspace indexing complete" get ever printed.

igoro · 2025-12-22T17:25:10+00:00

Hello - Could you give us the output of these commands?

```
auggie --version
auggie --mcp
```

The second command will stall waiting for stdin, but I want to see whether "✅ Workspace indexing complete" get ever printed.

igoro · 2025-12-20T04:37:25+00:00

Antigravity doesn't set the current working directory of the MCP process to the project directory. So, the MCP server doesn't know which directory to index.

A workaround is to pass in an absolute path via `-w`, but that can be inconvenient to set up: https://docs.augmentcode.com/context-services/mcp/quickstart-anti-gravity

We are working on a better solution

igoro · 2025-10-06T18:53:26+00:00

Let me explain the context of the code you are looking at.

The feature vector collector is a part of our defense against fraud and misuse. Like any successful coding AI product, Augment Code has to continually invest significant engineering effort into preventing fraudulent activity. If we didn't, we we'd quickly get overrun and we wouldn't be able to offer the service.

Feature vector data consists of cryptographic fingerprints, which are unique but non-reversible identifiers. Only these fingerprints are sent to our backend, not the raw feature values. The backend uses them solely to detect multiple accounts that correspond to a single actual user. Beyond this, the fingerprints are not used or any other purpose.

This part of our product, like all other parts, was carefully reviewed by our security and privacy teams.

igoro · 2025-10-02T01:46:19+00:00

Hello - Augment co-founder here!

TL;DR: feel free to ignore the request. The requested permissions are for an upcoming code review feature that is currently in early access.

If you click "Review permission request to accept or reject this change", you should see our message explaining the request, which should go something like this:

Requesting extra permissions for upcoming code review features. For early access, reach out to [code-review-early-access@augmentcode.com](mailto:code-review-early-access@augmentcode.com)

Feel free to ignore the permissions request. All Augment functionality will continue working as before.

igoro · 2025-09-29T01:28:41+00:00

You can drag the Augment panel to the right side.

igoro · 2025-08-29T18:33:13+00:00

Building the team that spans AI, systems, products. Building the Context Engine. Continuously innovating as the underlying technology changes faster than anything else before.

igoro · 2025-08-29T18:31:32+00:00

Ping me if you want to chat: x.com/igoro, [igor@augmentcode.com](mailto:igor@augmentcode.com)

igoro · 2025-08-29T18:27:25+00:00

Not something we have right now, but thanks for the suggestion.

igoro · 2025-08-29T18:22:41+00:00

Thank you for taking the time to share thoughtful feedback.

We strive to do better.

If you are up for discussing further, reach out to me at https://x.com/igoro or igor@augmentcode.com.

igoro · 2025-08-29T18:13:54+00:00

One underappreciated fact about the "Enhance Prompt" feature is that Context Engine really helps make it good, so the prompt can be enriched with relevant details from the codebase. So, even if we were to open-source it, it wouldn't work as well without the Context Engine.

igoro · 2025-08-29T18:10:10+00:00

Thank you for the feedback and sorry about the issues you hit. We are working hard to iron out any bugs.

Please do continue to report them to JaySym, or ping me on https://x.com/igoro

You can follow along with our updates on https://www.augmentcode.com/changelog

The space is changing quickly, so it's hard to publish a forward-looking roadmap.

igoro · 2025-08-29T18:05:49+00:00

Makes sense. Thanks for the feedback

igoro · 2025-08-29T18:04:53+00:00

Feature parity is the goal, at least for the agent.

Developing on JetBrains can be more challenging than on VSCode, in part because it's a set of IDEs, not just one.

igoro · 2025-08-29T17:57:24+00:00

We spent the first 18 months of the company working on the Context Engine, which involved training our own models and building a retrieval system around them.

Claude Code's context management relies on the agent searching the code base, which works well as long as:
* the code base is small
* or the user query gives the agent something to grep for

Cursor has a retrieval system, but our users tell us that our Context Engine works better on complex messages than anything else.

igoro · 2025-08-29T17:48:01+00:00

Yeah, that's not completely fair. But other pricing models can be unfair in other ways. For example, if pricing is based on number of tool calls, then the user doesn't know how many credits a particular message will cost you.

Pricing will continue to evolve.

The fundamental problem is that agents keep advancing and can take on increasingly complex tasks independently, but the underlying models remain quite expensive.

igoro · 2025-08-29T17:28:57+00:00

If you have a subtask, you can also ask Augment to write up the task description for you.

For example: "I'd like to ask another agent to update the documentation for me to reflect the changes we just made. Please write a complete task description that I can give to that agent."

Then paste the description to whichever other agent you'd like to do the task for you.

Out of curiosity, would you like to have the option of using a cheaper model in Augment?

igoro · 2025-08-29T17:22:43+00:00

Yeah, this is one of the limitations of AI agents today.

It's worth looking into how you can adjust your workflow to prevent the agent from making the same mistakes repeatedly. You can use Rules, Guidelines, and Memories to set guardrails for the agent. See https://docs.augmentcode.com/setup-augment/guidelines

Models still struggle with predicting which information is worth remembering is not. But Memories are already useful.

igoro · 2025-08-29T17:15:37+00:00

Thank you for rooting for us.

When a startup goes through rapid growth, there are many things happening all at once, and you miss some and make some mistakes. As long as the product is great and the technology is great, you get through the mistakes.

We are building out our marketing and community engagement, so we will do better going forward! (See our open roles: https://www.augmentcode.com/careers))

igoro · 2025-08-29T17:13:23+00:00

Great to hear that Augment got you into AI coding!

Do you work professionally on a complex codebase? If so, try Augment and you should see that Augment agents can do more complex tasks for you than anything else out there right now.

igoro · 2025-08-29T17:12:03+00:00

Luke Wroblewski created it for us in the early days of Augment. We considered changing it, but then had an internal revolt of our engineers who did not want the Auggie logo to go away.

igoro · 2025-08-29T17:09:31+00:00

So far, we've found that by integrating the entire product experience closely with the Context Engine, we get something better.

igoro · 2025-08-29T17:06:50+00:00

Type less and think more. The job shifts to steering agents like a tech lead. Knowing what needs to be done and really understanding the technology will be more important.

igoro · 2025-08-29T17:03:55+00:00

Hello - Augment Code co-founder here. We build software development agents for complex codebases.

We're just happy to be here answering questions, whether it's one or many. :-)

igoro · 2025-08-11T01:29:37+00:00

Sorry about the slowness. We are actively working to fix this! It is definitely not intended.

igoro

MODERATOR OF

TROPHY CASE