Skip to content

fix: fall back to config sandbox paths in scanAgents #1636

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
avoidwork merged 1 commit into from
Nov 1, 2026
Merged

fix: fall back to config sandbox paths in scanAgents #1636

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion src/tools/scanAgents/index.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,11 @@ const ScanAgentsSchema = z.object({
*/
export async function scanAgentsImpl(input, options) {
const targetPath = input.path || getProjectCwd() || config.cwd || process.cwd();
const resolved = validatePath(targetPath, options.allowedPaths);
// The orchestrator invokes the raw singleton without runtime options, so
// options.allowedPaths is undefined there. Fall back to the live config's
// sandbox allowlist — loadConfig() is cached, so this reflects app mutations.
const allowedPaths = options.allowedPaths || loadConfig().sandbox?.paths || [];
const resolved = validatePath(targetPath, allowedPaths);
if (!resolved.allowed) {
return { ok: false, error: resolved.error };
}
Expand Down
Loading