When using the cursor editor window there is the [ cmd + . ] shortcut which opens the quick fix and is a lifesaver for auto-imports (screenshot 1). This saves a significant amount of time.
The new agent window doesnt seem to show anything for exactly the same code (screenshot 2). You must rely on tab completion (which rarely gets it right) or manual imports (which are painfully slow).
Is this a known limitation in the new agents window file editor, or is this a bad config my end?
Steps to Reproduce
For any file, reference an import/module elsewhere in your codebase. Place the cursor on the error. Use the shortcut Cmd + . and see nothing is suggested under quick fix.
Hey, thanks for the report and the detailed screenshots. I can see both images: Quick Fix with auto-import in a normal window vs an empty Quick Fix in the Agents Window on the same code.
This is a known limitation of the Agents Window (Glass). Extension-provided LSP features like go-to-definition, linting, diagnostics, and code actions like Quick Fix Cmd+. and auto-import are not fully integrated there yet. The LSP toggle in the file tab header enables basic functionality like syntax highlighting, but code actions are still being worked on.
This isn’t an issue with your config. For now, the workaround is to use the normal editor window for full TypeScript tooling, where everything works as before, and switch between it and the Agents Window as needed.
I can’t share an ETA for full extension support in the Agents Window yet, but it’s on the radar. Let me know if the LSP toggle is on and you still don’t get the basic features, then we can dig in separately.
Appreciate the mammoth task to get this over the line and all understood. Not looking for a concrete timeline, but is there a sense internally if this will be delivered in weeks, months, or years?
Trying to decide how I best invest my time to setup my daily tooling and dont want to have to change frequently.
Honestly, I can’t give even a rough estimate in weeks, months, or years. A full integration of extension LSP features like code actions, go-to-definition, and diagnostics into the Agents Window is non-trivial work, and there’s no fixed timeline for it right now.
But for your main request about setting up tooling so you don’t have to redo it often, there is a clear answer. The regular editor window isn’t going anywhere and it will stay a full environment with all the TypeScript tooling, like before. So the safest setup is to build your daily workflow around the editor window for writing code and for things like auto-imports and Quick Fix, and keep the Agents Window for working with the agent, switching between them as needed. This setup will keep working no matter when LSP parity lands in Glass.
Once there’s an update on extension support in the Agents Window, I’ll post it in the thread.
