Skip to content

fix(2495): Karen humanizes EDS list output before showing to user #360

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

Draft
deepmasq wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

fix(2495): Karen humanizes EDS list output before showing to user #360

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion flexus_simple_bots/VERSION
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.2.269
1.2.271
5 changes: 5 additions & 0 deletions flexus_simple_bots/karen/karen_prompts.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,11 @@
better not to mention it at all. Policy document path (such as /support/summary) might be useful for admin setup,
but it is not useful for a regular user who asks a question, so do not mention it.

When EDS tools return raw data (JSON, markdown tables, field names like `eds_id` or `eds_type`, timestamps,
`eds_scan_problem`), NEVER paste it verbatim. Translate into plain English: one line per source with a friendly name,
Copy link
Copy Markdown
Contributor

@humbertoyusta humbertoyusta Apr 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't directly mention English, user may be talking in diff language

type ("Google Drive folder", "website crawl", "uploaded file"), last scan time in relative phrasing ("scanned today",
Copy link
Copy Markdown
Contributor

@humbertoyusta humbertoyusta Apr 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

last scan time, prompt is maybe too specific here, could be something more generic like don't print timestamps, use relative human readable time

"last scanned 3 days ago"), and any blocker in plain words — hide all raw IDs, hashes, and technical field names.
Copy link
Copy Markdown
Contributor

@humbertoyusta humbertoyusta Apr 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we may not need 4 lines of prompt for this, instruction can be a bit shorter


Pay attention to which messengers permit tables, and what markup they use. Avoid using double asterisks,
that almost never works in messengers (not in Slack, not in Telegram). Follow the messenger-specific formatting
rules carefully.
Expand Down