File Context

Why File Context Matters

YeePilot gives much better answers when it can see the real file you are talking about. This matters for:

• project files
• config files
• scripts
• logs
• text documents

Without file context, the AI has to infer structure and values. With file context, it can inspect the real content.

Attach Files

Attach a file directly:

/file /etc/nginx/nginx.conf

List everything currently attached:

/files

Remove something you no longer need:

/unfile /etc/nginx/nginx.conf

Use Uploads When Typing Paths Is Annoying

Use:

/upload

This opens the interactive upload flow. It is useful when you want to choose files instead of typing long paths manually.

Clipboard File-Path Paste

YeePilot can also help when you paste file paths from your terminal or file manager. The behavior is controlled by:

files:
  clipboard_paste_mode: auto

Available values:

• auto
• on
• off

For most users, auto is the right choice.

Limits

Default file-context limits are:

These limits stop a session from becoming overloaded with too many or too-large attachments.

Live Stream Panel

The live stream panel is the user-facing view for file edits while YeePilot is working on a mutating task.

Use:

/livestream
/livestream status
/livestream scope all
/livestream scope files
/livestream off

The panel helps you watch:

• which file is being edited
• whether the panel is enabled
• whether sensitive paths and content are redacted
• how much file activity is happening during a task

Live Stream Settings

The main user-facing live stream settings are:

tui:
  live_stream_panel_enabled: true
  live_stream_panel_height: 12
  live_stream_panel_scope: all_mutating_tools
  live_stream_panel_redact_sensitive: true
  live_stream_panel_animation: true

The most useful scope values are:

• all_mutating_tools
• file_tools_only
• off

Best Way To Use File Context

1. attach the exact files that matter
2. remove files from old tasks when they are no longer relevant
3. keep the live stream on for risky or multi-file changes
4. use /plan <task> before asking for edits across several files

This keeps answers accurate and keeps the session focused.