Configuration Reference
This file is auto-generated. Do not edit manually.
.wseng Configuration Files
.wseng files
The CLI uses a set of .wseng configuration JSON files, of the following types:
Personal Configuration (located in your home directory)
| Property | Description |
|---|---|
| awsProfile | Optional AWS profile for commands that read AWS resources. |
| truefoundryToken | Your personal TrueFoundry gateway token, used for every LLM call. |
| truefoundryBaseUrl | TrueFoundry gateway base URL (OpenAI-compatible). |
| truefoundryModelOverrides | Gateway slug overrides, keyed by CLI model name (e.g., { 'claude-opus': 'claude-group/claude-opus-4-6' }). |
| emailAddress | Your work email address. |
| ci | Run in CI mode (no interactive prompts). Persisted by init --automation. |
| localPaths | The local paths where our repositories are cloned. |
| commandConfigurations | User-specific command configurations, with command names as keys |
| extensionVersions | The current version of the WSEng VSCode extensions. |
| obsSettings | OBS Studio settings for demo recording |
Project Configuration (located in the root directory of each project)
| Property | Description |
|---|---|
| contextFolder | The folder where the context is stored. |
| specs | The list of specs to pull. |
| pullRequestTemplate | The pull request template, using handlebars syntax. |
| commandConfigurations | Command-specific configurations for the project, with command names as keys |
| stagingBranch | The staging branch name for the project |
| defaultGitHubRepo | Default GitHub repository for numeric-only ticket IDs (e.g., 'ws-eng-cli') |
| ticketKeyAliases | Ticket-key scopes that name a product instead of a repository, mapped to the repository holding their issues (e.g., { 'my-product': 'my-repo' }). Release notes fetch and link these keys in the mapped repository and display them as written. |
| cachedProjectId | Cached project ID for this repository (for repos not in Team Roster) |
| awsAccounts | AWS accounts for this repo, keyed by account type (dev/prod) or account name. Each entry has accountId and stackPattern regex for filtering CloudFormation stacks. |
Here's an example of a personal configuration file that does the following:
- configures the
start-ticketcommand to use the current branch as the base branch by default
{
"commandConfigurations": {
"start-ticket": {
"defaultInputs": {
"currentBranchAsBase": true
}
}
}
}
