Agent Packages
In ContextGo, an assistant should not be understood as only a preset.
It is closer to an Agent Package that can carry:
- rules
- docs
- skills
- hooks
- commands
- schedules
Why packages matter
This model makes ContextGo more stable and more product-native:
- packages stay reusable
- runtimes remain execution backends, not the product model
- automation stays owned by ContextGo rather than by one runtime layout
What users should take away
You do not need to memorize the internal package structure.
The practical takeaway is simpler:
- packages give you a working mode
- packages can bring more than one kind of capability
- packages help the system stay consistent across runtimes