Currently symposium relies on being installed out of band, and then calling symposium init to add hooks to agent harness workflows.
Not ideal:
- It hurts discovery
- It relies on the users to occasionally calling
cargo update symposium to get newer features (let alone we ship a vulnerability...)
- We basically never can change our hooks after init (I think?)
Where possible, we would prefer to rely on tooling plugin registries to install and update. This is a similar model to what rust-analyzer follows with VSCode: ref
Most of the commercial tooling has some sort of plugin registry. There are less turnkey registries for OSS tooling, though we should see what we can do.
I imagine we want to have a subdirectory per plugin in-tree, and push updates whenever our binary changes. Though, that may be easier said than done. We will need to look case by case, we can start with what is easy :)
Currently symposium relies on being installed out of band, and then calling
symposium initto add hooks to agent harness workflows.Not ideal:
cargo update symposiumto get newer features (let alone we ship a vulnerability...)Where possible, we would prefer to rely on tooling plugin registries to install and update. This is a similar model to what rust-analyzer follows with VSCode: ref
Most of the commercial tooling has some sort of plugin registry. There are less turnkey registries for OSS tooling, though we should see what we can do.
I imagine we want to have a subdirectory per plugin in-tree, and push updates whenever our binary changes. Though, that may be easier said than done. We will need to look case by case, we can start with what is easy :)