Traditional social software assumes a person opens a dashboard, navigates a calendar, writes a post and clicks a button. AI clients change the starting point. A user may already be talking to an assistant when the need to publish appears.
The capability becomes primary
If publishing is exposed as a typed capability, the interface can change without rebuilding the social layer. Chat, CLI, automation, a browser workspace and a future agent runtime can all call the same product primitive.
OAuth belongs to the product
The AI client should not need raw Instagram, LinkedIn or Facebook credentials. PubMesh owns that connector boundary and maps it to a workspace. Clients receive bounded product actions instead.
Reversible work first
AI can draft aggressively while public actions remain explicit. A draft, a schedule and a publish-now request are not the same operation. Modeling them separately makes automation more useful without making it careless.
Interfaces become replaceable
This is why PubMesh can have a small browser workspace today and a different conversational runtime tomorrow. The durable layer is the capability surface underneath.