Fission-AI/OpenSpec · error
Path is not writable: ${targetPath}
Error message
Path is not writable: ${targetPath} What it means
Error "Path is not writable: ${targetPath}" thrown in Fission-AI/OpenSpec.
Source
Thrown at src/core/completions/installers/bash-installer.ts:259
return {
success: true,
installedPath: targetPath,
message: 'Completion script is already installed (up to date)',
instructions: [
'The completion script is already installed and up to date.',
'If completions are not working, try: exec bash',
],
};
}
// File exists but content is different - this is an update
isUpdate = true;
} catch (error: any) {
// File doesn't exist or can't be read, proceed with installation
console.debug(`Unable to read existing completion file at ${targetPath}: ${error.message}`);
}
if (!(await FileSystemUtils.canWriteFile(targetPath))) {
throw new Error(`Path is not writable: ${targetPath}`);
}
// Ensure the directory exists
const targetDir = path.dirname(targetPath);
await fs.mkdir(targetDir, { recursive: true });
// Backup existing file if updating
const backupPath = isUpdate ? await this.backupExistingFile(targetPath) : undefined;
// Write the completion script
await fs.writeFile(targetPath, completionScript, 'utf-8');
// Auto-configure .bashrc
const bashrcConfigured = await this.configureBashrc(targetDir);
// Generate instructions if .bashrc wasn't auto-configured
const instructions = bashrcConfigured ? undefined : this.generateInstructions(targetPath);
View on GitHub (pinned to 6926ccb18a)
When it happens
Trigger: Thrown at src/core/completions/installers/bash-installer.ts:259 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of Fission-AI/OpenSpec@6926ccb18a (2026-08-25).
Data as JSON: /api/errors/cf203b9d9dab2b43.
Report an issue: GitHub.