-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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.
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
feat: client-discord stop implementation / agent improvements #1029
Conversation
… character client
…, improve client guards, upload clients into runtime, make startAgent return runtime
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM - left a few nits nothing blocking - great work!
agent/src/index.ts
Outdated
const clientTypes = | ||
// each client can only register once | ||
// and if we want two we can explicitly support it | ||
const clients:Record<string, any> = {}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks so much for doing this! Appreciate how hard you are grinding! Looks like a space is missing after the colon for all the type declarations here
const farcasterClients = new FarcasterAgentClient(runtime); | ||
farcasterClients.start(); | ||
clients.push(farcasterClients); | ||
// why is this one different :( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could create an issue for this to standardize
Also addressing linter and then good to go thanks so much! |
Risks
Low
Background
What does this PR do?
implements discord websocket disconnect
make character settings optional
implement runtime.clients as a dict
disable client in characters client
What kind of change is this?
Improvements (misc. changes to existing features)
Why are we doing this? Any context or related work?
Preparation for hot reloading
Documentation changes needed?
My changes should not require a change to the project documentation.