-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
enhancementNew feature or requestNew feature or request
Description
Currently the team directory is a local folder. But if it's a git repo, agents on different machines could coordinate by pushing/pulling:
Agent A (laptop) --> git push --> team-dir repo --> git pull <-- Agent B (server)
What needs to be figured out
- Sync frequency: Should agents pull before every heartbeat? After every task completion?
- Merge conflicts: Two agents editing the same project note simultaneously. Git auto-merge handles line-level changes, but what about the same task entry?
- Authentication: Agents need git credentials. SSH keys per agent? Deploy keys?
- Latency: Git push/pull adds seconds of latency to every coordination cycle. Acceptable?
- Protocol changes: Does protocol.md need a "remote team" section, or is this purely an implementation detail?
Use case
Run a chief of staff on your laptop (via Telegram) coordinating worker agents running on cloud servers (via Spindle containers). The team directory git repo is the shared state.
This is the bridge between Cortex (coordination) and Spindle (container infrastructure).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request