Town added Townies to group texts on 3 September, letting an assistant read the thread, compare schedules, request information through other participants' Townies and carry out browser tasks such as making a reservation. Town says bookings and purchases still stop for the user's approval.
Sharing is scoped to each group. The user sets a policy for what the Townie may disclose, can reduce it to a conservative setting, and can remove the agent from the thread to cut off further access from that group.
Instinct follows with a trusted-person network
Six days later, Instinct founder Noah Shinn announced an Instinct-to-Instinct protocol for coordinating plans between users. The launch examples included finding times with a spouse or colleagues, planning trips and recurring activities, and organising larger events.
Instinct restricted communication to people a user had added to a Trusted Person network. The launch announcement did not describe cross-service connections, message retention or a per-exchange approval record, so it establishes the coordination feature and its contact boundary rather than a general interoperability standard.
Personal agents are becoming shared-workflow participants
Town and Instinct reached a similar product pattern within six days: the assistant can move beyond one person's private task list and help carry a plan across several people, with software acting on both sides of the exchange.
Both systems remain service-specific in their public descriptions. That makes permission design an immediate product question: each agent may hold private context that is useful to a group, while only part of that context should cross into the shared workflow. Town documents a per-group sharing policy and approval gates for actions; Instinct documents a trusted-contact boundary but leaves more of the exchange semantics unpublished.