docs · scn-chat · Tangled

ATProto-based AI Assistant Chat interface.

1 folder · 3 files

at commit e2411fa6

pouriade.com · The docs catch up with the last week's changes. The architecture overview says a local server moves to the next free port when its own is taken, and a deployment's never does, that features reach the browser's local copy only through the store's hooks, with the open conversation as useChat and the reply follower showing a reply's stream until its record arrives, that the send route calls the runner's send with the request convention in turns/request.ts, that the pending reply is claimed at <key>.r<attempt> with a create-only call and streams over server-sent events with nothing more written meanwhile, and that each user's ChatService sits over their record and blob stores, with createChatServices the one place that picks the backend. The deployment guide sets NODE_ENV to production, leaves OAUTH_SCOPE_MODE unset since it defaults to permission-set, and mentions pnpm preview. The plugin guide says a secret that can't be decrypted reads as unset, and that options can be secret too. .env.example shows OAUTH_SCOPE_MODE commented out under its comment, which had lost its variable. · 2w ago

Give a reply's code blocks and tables icon actions in their corner, on a card of the block's own color, shown on hover and always on a touch screen. A finished code block copies its code or downloads it as a file named for its language, as code.py. A table's Copy opens a menu of Markdown, CSV, or TSV, showing a check once copied, and its Download one of CSV or Markdown, read from the table as it shows through Streamdown's table helpers behind our own buttons and menu. A table now fills the column inside a frame that scrolls when it is wider, so its rows run to its edge, its headings stay on one line, and the last leaves room for the actions. Copy's icon swap moves into CopyIconSwap so the table's menu shares it.

architecture.md

The docs catch up with the last week's changes. The architecture overview says a local server moves to the next free port when its own is taken, and a deployment's never does, that features reach the browser's local copy only through the store's hooks, with the open conversation as useChat and the reply follower showing a reply's stream until its record arrives, that the send route calls the runner's send with the request convention in turns/request.ts, that the pending reply is claimed at <key>.r<attempt> with a create-only call and streams over server-sent events with nothing more written meanwhile, and that each user's ChatService sits over their record and blob stores, with createChatServices the one place that picks the backend. The deployment guide sets NODE_ENV to production, leaves OAUTH_SCOPE_MODE unset since it defaults to permission-set, and mentions pnpm preview. The plugin guide says a secret that can't be decrypted reads as unset, and that options can be secret too. .env.example shows OAUTH_SCOPE_MODE commented out under its comment, which had lost its variable.

The docs catch up with the last week's changes. The architecture overview says a local server moves to the next free port when its own is taken, and a deployment's never does, that features reach the browser's local copy only through the store's hooks, with the open conversation as useChat and the reply follower showing a reply's stream until its record arrives, that the send route calls the runner's send with the request convention in turns/request.ts, that the pending reply is claimed at <key>.r<attempt> with a create-only call and streams over server-sent events with nothing more written meanwhile, and that each user's ChatService sits over their record and blob stores, with createChatServices the one place that picks the backend. The deployment guide sets NODE_ENV to production, leaves OAUTH_SCOPE_MODE unset since it defaults to permission-set, and mentions pnpm preview. The plugin guide says a secret that can't be decrypted reads as unset, and that options can be secret too. .env.example shows OAUTH_SCOPE_MODE commented out under its comment, which had lost its variable.

The docs catch up with the last week's changes. The architecture overview says a local server moves to the next free port when its own is taken, and a deployment's never does, that features reach the browser's local copy only through the store's hooks, with the open conversation as useChat and the reply follower showing a reply's stream until its record arrives, that the send route calls the runner's send with the request convention in turns/request.ts, that the pending reply is claimed at <key>.r<attempt> with a create-only call and streams over server-sent events with nothing more written meanwhile, and that each user's ChatService sits over their record and blob stores, with createChatServices the one place that picks the backend. The deployment guide sets NODE_ENV to production, leaves OAUTH_SCOPE_MODE unset since it defaults to permission-set, and mentions pnpm preview. The plugin guide says a secret that can't be decrypted reads as unset, and that options can be secret too. .env.example shows OAUTH_SCOPE_MODE commented out under its comment, which had lost its variable.