chihlasm/resolutionflow
1
0
Fork 0
Code Issues 23 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

feat: show AI content scope indicator (IT-focused context) #127

New Issue
Open
opened 2026-04-07 13:08:58 +00:00 by chihlasm · 0 comments
chihlasm commented 2026-04-07 13:08:58 +00:00 (Migrated from github.com)
Copy Link

Feature Request (from beta tester feedback)

Beta tester wondered whether sending non-IT-specific messages (e.g. general questions) might have caused errors, and whether the assistant is intentionally scoped to IT topics.

Options to consider

  1. UI indicator — small badge or footer note: "Optimised for IT infrastructure & MSP troubleshooting"
  2. Soft guardrail — if the AI detects a clearly off-topic message, respond with a gentle redirect: "I'm specialised for IT troubleshooting. For that topic you might want a general assistant."
  3. No change — current system prompt already scopes responses; just clarify in onboarding docs

Context

Beta tester note: "I was wondering if [locking down to IT specifics] could have been a problem on the screenshots of the 'sorry, something went wrong' queries."

Note: the errors were actually caused by an MCP integration failure (now fixed in the backend), not content filtering. But this raised a valid question about user expectations around scope.

## Feature Request (from beta tester feedback) Beta tester wondered whether sending non-IT-specific messages (e.g. general questions) might have caused errors, and whether the assistant is intentionally scoped to IT topics. ### Options to consider 1. **UI indicator** — small badge or footer note: "Optimised for IT infrastructure & MSP troubleshooting" 2. **Soft guardrail** — if the AI detects a clearly off-topic message, respond with a gentle redirect: "I'm specialised for IT troubleshooting. For that topic you might want a general assistant." 3. **No change** — current system prompt already scopes responses; just clarify in onboarding docs ### Context Beta tester note: *"I was wondering if [locking down to IT specifics] could have been a problem on the screenshots of the 'sorry, something went wrong' queries."* Note: the errors were actually caused by an MCP integration failure (now fixed in the backend), not content filtering. But this raised a valid question about user expectations around scope.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
10x-analysis
From 10x product analysis
 backend
FastAPI/Python work
 bug
Something isn't working
 collaboration
Team sharing, escalation, notifications
 database
PostgreSQL/schema changes
 documentation
Documentation updates
 duplicate
This issue or pull request already exists
 enhancement
Improvement to existing feature
 feature
New functionality
 frontend
React work
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 integration
PSA, external service integrations
 intelligence
Analytics, AI, data-driven features
 invalid
This doesn't seem right
 priority: high
Do this soon
 priority: low
Nice to have
 priority: medium
Important but not urgent
 question
Further information is requested
 quick-win
Low effort, high value
 strategic
Long-term strategic bet
 ux
User experience improvements
 wontfix
This will not be worked on
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
chihlasm
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: chihlasm/resolutionflow#127
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?