aws / aws/amazon-q-developer-cli

Allow users to define context hierarchy

Open
#1,420 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
2k
Forks
439
PR merge metrics
No merged PRs in 30d

Description

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 15.3.2 (24D81)

### Expected behaviour

Users should be able to rank their context files to make it clear to Q (and the user) which file takes precedence if a conflict is found

### Actual behaviour

Currently users can define context files, but when teams have context files and organizations have broader context files, both containing useful information, sometimes information gets out of sync between these files. It isn't clear how Q arbitrates conflicting information.

```
[chat-transcript]
> /issue

I'd be happy to help you report an issue or make a feature request. To do this properly, I'll need some information about what you'd like to report.

Could you please provide:
1. A title for the issue or feature request
2. A description of the expected behavior (what you want to happen)
3. A description of the actual behavior (what's currently happening, if it's an issue)
4. Any steps to reproduce the issue (if applicable)

Once you provide these details, I can help you submit a formal report using the appropriate tool.
[Tool uses: none]

> Title: Allow users to define context heirarchy, description of expected behavior: Users should be able to rank their context files to make it clear to Q (and the user) which file takes precedence if a conflict is found, description of actual behavior: Currently I can define context files, but my team has context files and my org has much broader context files. Both have useful information but sometimes information gets out of sync between these files. Right now it isn't clear how Q would aribitrate the conflicting information

I'll help you report this feature request. Let me submit that for you:
[Tool uses: report_issue]

Thank you for submitting this feature request! Your issue has been reported with the following details:

Title: Allow users to define context hierarchy

Expected behavior: Users should be able to rank their context files to make it clear to Q (and the user) which file takes precedence if a conflict is found

Actual behavior: Currently users can define context files, but when teams have context files and organizations have broader context files, both containing useful information, sometimes information gets out of sync between these files. It isn't clear how Q arbitrates conflicting information.

This is a valuable suggestion that would improve how context files work, especially in team environments where multiple layers of context exist. The ability to define precedence would help ensure the most accurate and relevant information is used when conflicts arise.
[Tool uses: none]

> try again, I wasn't signed into github before

I understand you weren't signed into GitHub before. Let me help you report this issue again:
[Tool uses: report_issue]
```

### Steps to reproduce

1. Add multiple context files with overlapping information (e.g., team-specific context and broader organizational context)
2. Ask a question where the information conflicts between context files
3. Observe that there's no clear hierarchy for which information takes precedence

### Environment

```yaml
[q-details]
version = "1.7.3"
hash = "3e4ae79d371315e80ddac772b43fff2cba314104"
date = "2025-04-10T05:48:16.435186Z (19d ago)"
variant = "full"

[system-info]
os = "macOS 15.3.2 (24D81)"
chip = "Apple M3 Pro"
total-cores = 12
memory = "36.00 GB"

[environment]
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "macOS"
install-method = "unknown"

[env-vars]
QTERM_SESSION_ID = "3fdd250af0b74c7893111f33c3412c8f"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.7.3"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.apple.Terminal"

[chat-settings]
interactive=true

[chat-trusted_tools]

[chat-failed_request_ids]
none
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.