Fission-AI/OpenSpec · error · StoreError
no_store_registry
no_store_registry
Error message
No store registry found
What it means
StoreError from resolveRegisteredStore when readStoreRegistryState finds no registry file at all. Nothing has ever been registered on this machine, so no store id can be resolved; code no_store_registry directs the user to register a store, then select it with --store <id>.
Solutions
- Register a store with 'openspec store register <path>'
- Then select it with --store <id>
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at src/core/store/registry.ts:446 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/636eac97ec82a75d.
Report an issue: GitHub.
Appendix: source
Thrown at src/core/store/registry.ts:446
});
}
return {
...removed,
storeRoot: getStoreRootForBackend(removed.backend),
};
}
export async function resolveRegisteredStore(
input: ResolveRegisteredStoreInput
): Promise<ResolvedStore> {
const id = validateStoreId(input.id);
const registry = await readStoreRegistryState({
globalDataDir: input.globalDataDir,
});
if (!registry) {
throw new StoreError('No store registry found', 'no_store_registry', {
target: 'store.id',
fix: 'Register a store with openspec store register <path>, then select it with --store <id>.',
});
}
const entry = getRegisteredStoreOrThrow(registry, id);
const backend = entry.backend;
const storeRoot = getStoreRootForBackend(backend);
await ensureStoreMetadata(storeRoot, id, { writeIfMissing: false });
return {
id,
storeRoot,
backend,
};
}
View on GitHub (pinned to 6926ccb18a)