Skip to content

Research cron observer#72

Closed
ethancjackson wants to merge 7 commits intomainfrom
research-cron-observer
Closed

Research cron observer#72
ethancjackson wants to merge 7 commits intomainfrom
research-cron-observer

Conversation

@ethancjackson
Copy link
Contributor

@ethancjackson ethancjackson commented Feb 13, 2025

Changes to cron client that enables conditional processing/propagation of messages, i.e. should_process field. Enables the creation of Observer agents that can have conditional logic for when to propagate a message to process_message for further processing. Defined an PriceChangeObserver agent under examples as well as adding a TokenPriceChangeCalculator tool under alphaswarm proper. This tool wraps the AlchemyPriceHistoryByAddress and gives a more convenient interface for getting price changes directly, as opposed to getting the price history and needing to process it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The main thing I might want to discuss is:
Should we keep cron_job.py as-is and create a new client to add logic? For example we could call this conditional_cron_job.py instead.
Another point is that I'd like to also create something like a swarm_cron_job.py that allows the user to specify something like a chain of agents to handle processing, so we could have, e.g. PriceForecaster -> TradeAssistant

@ethancjackson ethancjackson deleted the research-cron-observer branch February 14, 2025 19:58
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.

2 participants