From 077c0660e84c7862d169acd8af21b841d167ddcb Mon Sep 17 00:00:00 2001 From: Art Koval Date: Tue, 21 Apr 2026 18:23:41 +0300 Subject: [PATCH 1/2] eds: set rescan_period 86400 in kb collection skill the auto-rescan infrastructure already exists in both crawler and unstructured services (periodic_rescan_loop). default is 7 days. karen needs 24h for support kb freshness. Co-Authored-By: Claude Opus 4.6 (1M context) --- .../karen/skills/collect-support-knowledge-base/SKILL.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/flexus_simple_bots/karen/skills/collect-support-knowledge-base/SKILL.md b/flexus_simple_bots/karen/skills/collect-support-knowledge-base/SKILL.md index ac41ca48..339aaf24 100644 --- a/flexus_simple_bots/karen/skills/collect-support-knowledge-base/SKILL.md +++ b/flexus_simple_bots/karen/skills/collect-support-knowledge-base/SKILL.md @@ -32,6 +32,9 @@ flexus_vector_search() will be able to pages like "return policy" and answer que If you have a documentation website, that's perfect. Make EDS using flexus_eds_setup() for documentation to be indexed and then accessible using flexus_vector_search(). +ALWAYS set `rescan_period: 86400` (24 hours) in the EDS info when creating any EDS. This ensures the knowledge +base stays fresh — the system automatically re-crawls/re-indexes every 24 hours. + Set up MCP here in this chat. The newly created MCP tool will only be available after chat restart, so you will not be able to test MCP yourself, but you can send a subchat to check it. From f48bc8c5f6e9ea6e82e1e65e618fb6685a60e2ca Mon Sep 17 00:00:00 2001 From: Art Koval Date: Mon, 27 Apr 2026 19:17:23 +0300 Subject: [PATCH 2/2] eds: ask user for refresh interval, default 24h humberto on #344: instead of hardcoding rescan_period=86400, ask the user during kb collection how often to refresh and propose 24h as the default. different sources have different freshness needs (status pages hourly, archives weekly), so a one-size global default is wrong. skill text now tells karen to ask, lists the common conversions, and falls back to 86400 if the user is indifferent. Co-Authored-By: Claude Opus 4.7 (1M context) --- .../karen/skills/collect-support-knowledge-base/SKILL.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/flexus_simple_bots/karen/skills/collect-support-knowledge-base/SKILL.md b/flexus_simple_bots/karen/skills/collect-support-knowledge-base/SKILL.md index 339aaf24..b396043d 100644 --- a/flexus_simple_bots/karen/skills/collect-support-knowledge-base/SKILL.md +++ b/flexus_simple_bots/karen/skills/collect-support-knowledge-base/SKILL.md @@ -32,8 +32,13 @@ flexus_vector_search() will be able to pages like "return policy" and answer que If you have a documentation website, that's perfect. Make EDS using flexus_eds_setup() for documentation to be indexed and then accessible using flexus_vector_search(). -ALWAYS set `rescan_period: 86400` (24 hours) in the EDS info when creating any EDS. This ensures the knowledge -base stays fresh — the system automatically re-crawls/re-indexes every 24 hours. +ALWAYS ask the user how often the knowledge base should refresh, proposing **24 hours** as the default. Most +support content (FAQs, return policies, docs) changes slowly enough that daily is right; rapidly-changing +sources (status pages, live inventory) may want shorter, and stable archives can go longer or one-time. + +Convert the user's answer to seconds and pass it as `rescan_period` in the EDS info when calling +`flexus_eds_setup()` (e.g. `86400` = 24h, `3600` = 1h, `604800` = 7d, `0` = one-time only). If the user is +unsure or doesn't care, use `86400`. The system then automatically re-crawls/re-indexes on that cadence. Set up MCP here in this chat. The newly created MCP tool will only be available after chat restart, so you will not be able to test MCP yourself, but you can send a subchat to check it.