Plugin system - Githubissues

hdresearch / nolita

Work with web-enabled agents quickly — whether running a quick task or bootstrapping a full-stack product.

https://nolita.ai

MIT License

86 stars 5 forks source link

Plugin system #4

Closed matildepark closed 4 months ago

matildepark commented 6 months ago

In order for us to support an extensible plugin system, we'll have to structure the class to support it.

This could mean making an event-based architecture where we structure our logic around an event queue and emitting events for modification by plugins.
This could mean constructing a shared state system where plugins mutate state, and we ensure that there are locks on state so that no race conditions occur.

Either way, this could involve a bit of a rearchitecture.

AlephNotation commented 5 months ago

does #33 address this via the extensions?

matildepark commented 5 months ago

We don't quite incorporate it everywhere we should. I would leave this open as opportunities for extensibility in each component in a more unified way.

matildepark commented 4 months ago

Between action step callbacks and the create command I feel like we essentially have plugins now.