Application settings
Overview
The Application settings allows you to customize various application-level behaviors in Faheem Code, including language preferences, notification settings, custom Git author configuration and more.
Setting maximum budget per conversation
To limit spending, go to Settings > Application and set a maximum budget per conversation (in USD)
in the Maximum Budget Per Conversation field. Faheem Code will stop the conversation once the budget is reached, but
you can choose to continue the conversation with a prompt.
Git author settings
Faheem Code provides the ability to customize the Git author information used when making commits and creating pull requests on your behalf.
By default, Faheem Code uses the following Git author information for all commits and pull requests:
- Username:
faheemcode - Email:
no-reply@faheemcode.ai
To override the defaults:
- Navigate to the
Settings > Applicationpage. - Under the
Git Settingssection, enter your preferredGit UsernameandGit Email. - Click
Save Changes
Getting started checklist
The sidebar shows a Getting Started checklist after first-run onboarding. Toggle Show getting started checklist in Settings > Application to hide or show it. The setting persists across sessions. See First Time Setup for details.
Sandbox grouping strategy
The Sandbox Grouping Strategy setting controls where Faheem Code places new
conversations started with your application settings.
| Setting | Placement Behavior |
|---|---|
| No grouping | Start a new sandbox for each conversation |
| Group by newest | Use the newest available sandbox |
| Least recently used | Use the least recently used available sandbox |
| Fewest conversations | Use the available sandbox with the fewest conversations |
| Add to any | Use the first available sandbox |
To change the setting:
- Navigate to
Settings > Application. - Select a value under
Sandbox Grouping Strategy. - Click
Save Changes.
Grouping can reduce sandbox startup time and sandbox count. Conversations in one sandbox share its filesystem, credentials, compute limits, and failure domain. The setting does not check whether a sandbox has enough CPU, memory, or disk for another conversation.
For API placement and sandbox lifecycle options, see Conversations And Sandboxes.