deepseek-ai/deepseek-harness · error
directory-picker-unavailable
directory-picker-unavailable
Error message
host.pickDirectory needs the native capability; the composed picker serves "${capability.kind}" What it means
Error "host.pickDirectory needs the native capability; the composed picker serves "${capability.kind}"" thrown in deepseek-ai/deepseek-harness.
Source
Thrown at packages/host/apiproxy/src/api-proxy.ts:2845
return Promise.resolve(ok(request, {
version: '0.0.1',
// Same source as session.create's fallback: the UI's default project
// must match where an unspecified-cwd session actually lands.
cwd: defaults.cwd,
// Read live for the same reason: this is what the NEXT session will
// start from, so a saved default has to be what it reports.
provider: selection.provider,
model: selection.model,
attachedSessions: ctx.agents.list().length,
home: homedir(),
canOpenPath: canOpenPaths(),
}))
},
async pickDirectory(request, signal) {
const capability = ctx.directoryPicker.capability()
if (capability.kind !== 'native') {
return err(request, {
code: 'directory-picker-unavailable',
message: `host.pickDirectory needs the native capability; the composed picker serves "${capability.kind}"`,
details: { capability: capability.kind },
})
}
try {
const path = await capability.pick(signal)
return ok(request, { path })
} catch (error: unknown) {
if (signal.aborted) {
return err(request, {
code: 'cancelled',
message: 'directory picker was aborted',
details: {},
})
}
return err(request, {
code: 'internal',View on GitHub (pinned to b150a551b8)
Solutions
- Compose a picker with the native capability for host.pickDirectory; the current picker serves a different kind.
When it happens
Trigger: Thrown at packages/host/apiproxy/src/api-proxy.ts:2845 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of deepseek-ai/deepseek-harness@b150a551b8 (2026-08-24).
Data as JSON: /api/errors/082b2ee2d3170ae7.
Report an issue: GitHub.