Skip to content

feat(q): add trusted tools to Amazon Q alias mirroring Claude's security model#940

Open
atxtechbro wants to merge 7 commits intomainfrom
feat/amazon-q-trusted-tools
Open

feat(q): add trusted tools to Amazon Q alias mirroring Claude's security model#940
atxtechbro wants to merge 7 commits intomainfrom
feat/amazon-q-trusted-tools

Conversation

@atxtechbro
Copy link
Copy Markdown
Owner

Replace the duck-taped qsafe solution with Amazon Q CLI's native --trust-tools approach, mirroring Claude's security model.

Changes

  • Add TRUSTED_TOOLS variable with same MCP tools that Claude trusts
  • Update q alias to use q chat --trust-tools="$TRUSTED_TOOLS"
  • Include work-specific tools (atlassian, gitlab) when WORK_MACHINE=true
  • Maintain same MCP config and knowledge directory as Claude

Benefits

  • ✅ Eliminates clipboard-based qsafe workaround
  • ✅ Native Amazon Q CLI permission management
  • ✅ Consistent security posture across AI providers
  • ✅ Same trusted tools as Claude's .claude/settings.json

AI Provider Agnosticism

Both claude and q aliases now have equivalent security models:

  • Claude: Uses .claude/settings.json trusted tools
  • Amazon Q: Uses --trust-tools with same tool list

This enables seamless switching between providers during service outages while maintaining identical security boundaries.

Principle: ai-provider-agnosticism

…Q prompts (@ prefix) as equivalent to Claude Code slash commands. Includes syntax differences, troubleshooting, and provider symmetry examples.\n\nPrinciple: systems-stewardship
Amazon Q CLI: '@close-issue 934' (single quotes required)
Claude Code: /close-issue 934 (slash commands, better autocomplete)

Both use same MCP servers - just different syntax.

Principle: ai-provider-agnosticism
Consolidated into knowledge/procedures/mcp-prompts.md for AI provider agnosticism
Keep PR focused on MCP prompt functionality only
Use commands/templates/close-issue.md directly instead of 
.claude/command-templates symlink for better reliability
…ity model

Replace duck-taped qsafe solution with native --trust-tools approach.
Amazon Q now uses same trusted MCP tools as Claude for consistent
security posture across AI providers.

- Add TRUSTED_TOOLS variable with same tools Claude trusts
- Include work-specific tools (atlassian, gitlab) when WORK_MACHINE=true
- Use q chat --trust-tools instead of manual permission management

Eliminates need for qsafe clipboard-based workaround.

Principle: ai-provider-agnosticism
@amazon-q-developer
Copy link
Copy Markdown
Contributor

⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done

@amazon-q-developer
Copy link
Copy Markdown
Contributor

✅ I finished the code review, and left comments with the issues I found. I will now generate code fix suggestions.

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.

1 participant