Augment Code

Intent is our vision for what comes after the IDE. AI has changed how we build software. But, it’s also made our workflows messier. One agent is great. Two work. Past that, things fall apart fast. Prompts go stale, context lives everywhere, and you end up spending more time on the tedious work of orchestrating agents. The bottleneck isn’t writing code anymore. It’s keeping the agents aligned. That’s why we built Intent.

@MingtaKaivo 100%

@augmentcode stale context is worse than no context. loaded 3 contradictory docs at AudioWave once — agent spent the whole session resolving the conflict. 1 tight current file beats 5 thorough ones.

Adding context files makes agents perform worse than giving them nothing. And it costs more. The fix is knowing which context goes where ↓

@oykun How are you approaching it?

@augmentcode Same pattern in product design. Teams dump every possible feature into the UI thinking more = better. The real skill is knowing what to leave out. Context curation is just information design with a different name.

@neolexical 🚀

Shipped my first vibe coded function to a live app 🙈😂 with @augmentcode. Really amazing to see how people work change rapidly and to see the development of some of those tools. Curious on how AI will change our lives in the near future. Thoughts?

Tomorrow: We’re going live with @trieloff (Principal at @Adobe) to see how he actually uses AI day to day. He’ll walk through: - workspace setup for parallel projects - the custom agentic tool he’s building inside Adobe - how he uses skills to customize workflows for different tools Sign up to join live or get the recording: luma.com/psg5f9xf

In a world where AI generates code faster than teams can review it, the highest-leverage work is writing precise specs.

How to turn @sentry issues into PRs with agents ↓

I'm going to talk with the good folks from @augmentcode about my work and their tools. Join us this Friday luma.com/psg5f9xf

skip the design system software. build directly from a design spec using Figma MCP and Intent.

Every documentation-first initiative in software has failed for the same reason: it asked developers to do continuous maintenance work that nobody sees and nobody rewards. SDD will fail for the same reason unless the agents do their share of the maintenance. If agents can write code, they can update the plan.

@cmgriffing Thanks for flagging Chris! We're working on this.

Intent by @augmentcode is a really nice agent orchestrator. Sure there are a bunch of UI/UX things I would fix. But the #1 issue I am having with it is an inability to recover from this state. (Try and guess which AI provider's network is this unstable...)

with intent I have automated my job. now will2 sits at my desk and no one has noticed yet

@inababi @Sikandar_Bhide 🤖💚

@augmentcode @Sikandar_Bhide We love an engaged team account too 😎🫶

Switching from Claude: what are your fav model providers? I’ll be doing research next week as I begin to plan retiring using Claude for everything. This is not sustainable.

@inababi @Sikandar_Bhide Excited for you to try!

@Sikandar_Bhide @augmentcode Ooooo I don’t know about this one at all! Adding to my research list. You are appreciated 🫡

@trieloff 🤖💙 We can’t wait!

I'm going on a live stream this week, and it's not about AEM. luma.com/psg5f9xf

Livestream this week: Come watch a principal engineer at Adobe show how he uses parallel coding agents and custom skills! Register here: luma.com/psg5f9xf

I'm becoming very bullish on sandboxes for polishing uis - ask for a new route that walks through all common and edge cases - if helpful, loop through animations & transitions - keep it side by side with the agent and ask it to take screenshots until it's smooth - scroll through and dictate tweaks