Skip to main content

Updated Files

When the AI modifies files in your project, AiderDesk tracks these changes in the Updated Files section. This feature provides a centralized view of all files that have been changed during the current task, making it easy to review, navigate, and refine the AI's work.

What Are Updated Files?​

Updated Files are files that have been modified by Aider during the current task. They appear in a dedicated section in the left sidebar, separate from your context files and project files.

Each updated file shows:

  • File path - The relative path to the modified file
  • Line statistics - Number of lines added (green) and removed (red)

Accessing the Diff View​

Clicking on any file in the Updated Files section opens a Diff View Modal that shows:

  1. Full diff visualization - See exactly what changed with color-coded additions and deletions
  2. Navigation controls - Use arrow buttons to move between multiple updated files
  3. File information - Current file name and position in the list (e.g., "2 of 5")

The diff view supports the same visualization modes as inline code diffs:

  • Side-by-Side - Original code on the left, modified code on the right
  • Unified - Changes shown inline in a single column
  • Compact - Space-saving mode with character-level highlighting

Making Inline Requests​

The most powerful feature of the Updated Files diff view is the ability to make inline code requests. This allows you to request specific changes directly on any line of code.

How to Make an Inline Request​

  1. Open the diff view by clicking on a file in the Updated Files section
  2. Click on any line in the modified code where you want to request a change
  3. Enter your feedback in the comment dialog that appears
  4. Submit the request - AiderDesk creates a focused task to implement your change

What Happens Next​

When you submit an inline request:

  • A new task is created with context about the specific file and line
  • The AI receives your comment along with surrounding code context
  • The change is implemented while maintaining code coherence with the rest of the file

Example Use Cases​

  • "Add error handling here" - Click on a function call and request try-catch blocks
  • "This variable name is unclear, rename to userCount" - Request naming improvements
  • "Add JSDoc documentation for this function" - Request inline documentation
  • "Optimize this loop for performance" - Request specific optimizations
  • "Add null check before accessing this property" - Request defensive coding

Best Practices​

DO:​

  • Be specific about what you want changed on the line
  • Provide context about why the change is needed
  • Focus on one issue per inline request
  • Use inline requests for targeted refinements after reviewing the AI's work

DON'T:​

  • Request multiple unrelated changes in one comment
  • Use vague feedback like "fix this" without explanation
  • Request changes that span multiple files (use a regular prompt instead)
  • Request large refactors through inline comments

Refreshing Updated Files​

The Updated Files list automatically updates as the AI makes changes. You can also manually refresh the list using the refresh button in the section header if needed.

  • Diff Viewer - Learn about diff visualization modes and reverting changes
  • Custom Prompts - Customize the inline request prompt template