Orvain UI

Thread entries

Threads that carry something: an upload, under the replies it drew.

Get Pro to installPro18 blocksReact, Vue and Figma
MCPConnect the MCP server
Mia Kwan· 10:14

Redlines and a quick capture for the chip states.

Tom Beck· 10:31Unread

Looped in the people who own the shortcut map.

Nora Vance· 10:40Unread

@Mia Kwan the dark chips are on page 3. Can you check them?

More in Activity Feed#

Thread feed

Team channels and project threads: a day of activity with one place to answer it

Thread feed, open in place

Busy threads where the replies should stay beside the message

Thread feed, catch up

Returning to a channel: what you missed, and where it starts

Pull request thread

Code review: commits, a diff and the checks that gate the merge

Pull request thread, merge box

Code review that ends in a merge: the checks run, then the button wakes

Pull request thread, inline review

Code review on the lines: comments live under the code they are about

Event rows

The rows a system writes: something happened, nobody said anything

Message rows

The row a person writes: what they said, who reacted to it and what you can do with it, in a live channel

Quoted entry

Anything an integration posts: a message pulled in from another surface

Event rows, stacks

Busy threads: a burst of changes folded into one line

Event rows, rail

The quietest feed: a timeline you glance down

Quoted entry, pull quote

A quote worth keeping: the message is the entry

Quoted entry, context

Quotes you want to check against the conversation around them

Message rows, quick react

A busy channel where one tap is the whole reply

Message rows, calm

A channel that is mostly reactions: the thread stays readable

Thread entries

Threads that carry something: an upload, under the replies it drew

Thread entries, by file

Threads about uploads: filter the replies by the file they are about

Thread entries, moments

Feedback on a capture or a document: replies pinned to a second or a page

When to use#

  • A record whose history mixes system events with what people said
  • Code review, where commits, a diff and check results belong to one thread
  • Team channels that need one place at the foot to answer from
  • Threads where the reply count matters more than every reply

The whole set, with its codePro

Pro opens the Code tab on every block here, in React and Vue, plus the Figma file and the MCP server for your editor.

Open in BlocksSee plans