Is it expected that an agent by default has no concept of the knowledge base or the knowledge search tool and should expect to expose that tool via a tool search?

My testing found it search the web before searching internal knowledge unless you prompt it to use the knowledge base.

Hey Archestra team, hope you’re all doing great!

I’ve been deploying Archestra with my team, I encountered two main issues so far:

1. I’m using OpenRouter as the main provider. The prices logged on Archestra and what is reported by OpenRouter are different, it looks like inference from OR isn’t using the price reported by them but the cached $/MTok price. Is it a known issue?

2. On the frontend, whenever a chat is streaming the response, the text input gets unresponsive. Profiling the browser at this specific moment shows that each onkeypress event takes approx. 200ms and blocks the main frame. I have a fix on my local machine, but before proposing it I’d like to see if that’s something you’re aware of and if that’s already been included in your internal roadmap?

hello there, I wanted to ask question related with knowledge base

• I have ingested the knowledge through the connector.

• the docs already indexed.

• The agent plug only the knowledge base because I assume docs already indexed

but when I inquiry the agent about the recent incident (which should be exist in knowledge base), it cant find anything (?)

However, if I plug the connector, the agent was able to fetch through the connector.

am I understand the concept of knowledge base correctly or I am missing something here that makes the agent unable to see the indexed docs?

I haven't checked to see if it's been changed, but is anyone aware if the SharePoint knowledge connector still grabs all pages, published and draft?

New blog post alert :speech_balloon:

We built a tool internally, that fixes Archestra bugs through autonomous sessions launched from Slack. While it works well for small fixes, it touches internal data and has ability to create PRs - basically has a full complex of Lethal Trifecta. In this post we share how we made sure this agent is secure and easy to use. Spoiler - everything starts with dropping a :crab: in Slack.