Skip to content

Fix #86: Allow WebFetch/WebSearch in expand-project chat - #338

Open
zwanski-start wants to merge 1 commit into
AutoForgeAI:masterfrom
zwanski-start:swarm/issue-86-ada
Open

zwanski-start wants to merge 1 commit into
AutoForgeAI:masterfrom
zwanski-start:swarm/issue-86-ada

Conversation

@zwanski-start

Copy link
Copy Markdown

Closes #86

Why

The "Expand project" chat runs with its own generated settings file (get_expand_settings_path), so the user's ~/.claude/settings.json and the project's .claude_settings.json don't apply to it. That generated file allowed only Read/Glob and the feature MCP tools, and the prompt never said web tools were available, so the assistant kept refusing to open links.

Changes

  • server/services/expand_chat_session.py: new EXPAND_BUILTIN_TOOLS constant (Read, Glob, Grep, WebFetch, WebSearch) used for allowed_tools. Added Grep, WebFetch and WebSearch to the settings-file allow list, matching the assistant chat. Write/Edit/Bash are still denied.
  • .claude/commands/expand-project.md: tells the assistant to open user-shared links with WebFetch, that it can use WebSearch, and that it must not claim it can't browse.

Verification

  • ruff check passes.
  • I did not run a live expand session end to end, because that needs Claude CLI auth.

Assumptions

  • The sandbox setting stays enabled. It only affects Bash, and Bash is disallowed in this session.

🤖 Generated with Claude Code

The expand session writes its own settings file, so user/project
.claude_settings.json do not apply. Add WebFetch, WebSearch and Grep to
its permission allow list and tell the assistant in the prompt that it
can open links the user shares.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarification needed: allowed tools for "add feature with AI" dialog

1 participant