Skip to content

Agent answers off-domain questions instead of redirecting to LangChain ecosystem scope - #3

Merged
darieldatoon merged 1 commit into
mainfrom
issues-agent/15fbae56-3a46-48b7-9d8c-039631e9e878
Jun 24, 2026
Merged

Agent answers off-domain questions instead of redirecting to LangChain ecosystem scope#3
darieldatoon merged 1 commit into
mainfrom
issues-agent/15fbae56-3a46-48b7-9d8c-039631e9e878

Conversation

@langsmith-engine

Copy link
Copy Markdown

The agent answers questions clearly outside its LangChain/LangGraph/LangSmith scope — Django debugging, OAuth2 walkthroughs, Kubernetes/Jaeger architecture, CI/CD pipelines, transformer-attention theory, AI-startup business plans, cross-provider LLM comparisons — producing confident, detailed responses in domains it shouldn't claim authority over. The root cause is the seeded AGENTS.md in Context Hub repo chat-lc-lite-agent-dariel (mirrored in utils/context_hub.py _SEED_AGENTS_MD), which frames the agent as a "general-purpose AI assistant with expertise in ... many other topics" and adds "Never say you don't know — give your best answer," with no scope-restriction or redirect clause. For a domain-scoped assistant this is a fundamental UX problem on every off-topic request.

…cosystem in seed AGENTS.md

The seeded prompt framed the agent as general-purpose and forbade saying
'I don't know', causing it to confidently answer off-domain questions.
Bound the identity to the LangChain ecosystem, add a Scope section that
instructs out-of-scope redirects, and allow honest in-scope uncertainty.
@hosted-langserve

hosted-langserve Bot commented Jun 24, 2026

Copy link
Copy Markdown

LangSmith preview deployment was torn down.

@darieldatoon darieldatoon reopened this Jun 24, 2026
@darieldatoon
darieldatoon marked this pull request as ready for review June 24, 2026 03:57
@darieldatoon
darieldatoon merged commit 6bbfcad into main Jun 24, 2026
2 checks passed
@darieldatoon
darieldatoon deleted the issues-agent/15fbae56-3a46-48b7-9d8c-039631e9e878 branch June 24, 2026 03:57
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