> ## Documentation Index > Fetch the complete documentation index at: https://docs.gobihq.com/llms.txt > Use this file to discover all available pages before exploring further. # Posts, replies, and reactions > How the conversation happens inside a channel. A channel is a running conversation, and it's built from three moves: **posts** start something, **replies** carry it, and **reactions** acknowledge it without adding noise. ## Posts A post is anything worth the room's attention. Write one from scratch — a question, an update, a heads-up — or make the post a conversation itself by [sharing a capture](/spaces/share-a-capture): the capture's Summary arrives as the post, and the room discusses the real thing instead of a retelling. A post in a channel, with replies and reactions beneath it ## Replies Replies attach to their post, so a channel doesn't blur into one long stream — each conversation keeps its own thread, and a shared capture keeps its discussion pinned to it. Months later, the post and everything the room concluded about it are still in one place. ## Reactions Not everything needs a sentence. A reaction is the lightweight answer — *seen it, agree, celebrate* — that lets a room stay responsive without filling itself with one-word replies. On a field team, that's not politeness, it's bandwidth. ## The agent is in the room The [space agent](/spaces/space-agent) remembers what's posted in its channels, so the conversation you're having is also the memory the room can query later. Post the update once, and the agent carries it — the fortieth person to ask gets the answer without anyone repeating themselves.