UNC Agent is the room-driven remote-operations layer growing beside chat.

The basic idea is that a room can be more than chat. A room can be a signed shared control plane carrying task requests, results, status, and artifacts.

Current shape

The current agent is intentionally narrow:

• trusted controller identities
• room-driven command events
• allowlisted local subprocess execution
• JSON result posts back into the room
• reference-client inspection of structured event bodies

Why rooms?

Rooms provide:

• durable signed history
• multi-operator visibility
• intermittent-link tolerance
• a natural place to store commands, results, status, and artifacts

That makes the model interesting for resilient operations across degraded or disconnected networks.

Near-term direction

• better ops-specific UI
• task UUIDs
• persistent task state
• duplicate suppression
• host and group targeting
• agent heartbeats
• capability advertisement
• artifact/file movement
• long-running jobs
• stronger trust policy

Guiding principle

Think big, but build primitives in the order that preserves trust.

That means idempotent tasking before clever orchestration, secure storage before sensitive automation, and robust artifact movement before pretending large-file operations are done.