(cwd: string)
| 258 | ` |
| 259 | |
| 260 | function getSystemInfoSection(cwd: string): string { |
| 261 | return `# System Information |
| 262 | |
| 263 | - Operating System: ${process.platform === "darwin" ? `macOS ${os.release()}` : `${process.platform} ${os.release()}`} |
| 264 | - Default Shell: ${getShell()} |
| 265 | - Home Directory: ${os.homedir()} |
| 266 | - Current Workspace Directory: ${cwd} |
| 267 | |
| 268 | The Current Workspace Directory is the directory the user launched OrbCode CLI from, and is therefore the default directory for all tool operations. Commands run in the current workspace directory unless a different cwd is passed; changing directories inside a command does not modify the workspace directory. When the user initially gives you a task, a listing of filepaths in the current workspace directory will be included in the Environment Details section. This provides an overview of the project's file structure, offering key insights into the project from directory/file names (how developers conceptualize and organize their code) and file extensions (the language used). This can also guide decision-making on which files to explore further. If you need to further explore directories such as outside the current workspace directory, you can use the list_files tool. If you pass 'true' for the recursive parameter, it will list files recursively. Otherwise, it will list files at the top level, which is better suited for generic directories where you don't necessarily need the nested structure, like the Desktop.` |
| 269 | } |
| 270 | |
| 271 | export interface SystemPromptOptions { |
| 272 | /** AGENTS.md memory files to inject (lowest precedence first). */ |
no test coverage detected