Sheela
Sheela
Home
Add
Questions
Thinkers
Claims
People
Concepts
Jargon
Sources
Health
Predictions
Collections
Domain Landscape
Contribute
Review
Dedup
Topic requests
Settings
Help

← Jargon

Jargontechnology· 3 claims· 1 episode

composer

Cursor's interface for making code changes (as opposed to chat for asking questions), which in agent mode can use tools, run terminal commands, and edit files.

As defined in I spent 400+ hours in Cursor, here’s what I learned


Where it comes up · 1
  • I spent 400+ hours in Cursor, here’s what I learned3 claims

Most important claims · 3 of 3Search all claims for “composer” →
  • You should switch to a new composer when you see weird behaviors or the model forgets key information, because that signals the context window is overloaded with too much code and too many referenced files.I spent 400+ hours in Cursor, here’s what I learned
  • Environment variables should be placed in a .cursorignore file so chat and composer don't accidentally rewrite them, but you must then describe what's in those env files in the cursorrules file, otherwise Cursor has no knowledge of which env files exist.I spent 400+ hours in Cursor, here’s what I learned
  • Use Cursor's chat mode for questions (asking it something) and composer/agent mode for changes; always use agent mode since it can use tools, run terminal commands, and edit files with no real downside.I spent 400+ hours in Cursor, here’s what I learned