Get it for macOS

Lets the pages your agents write read and save your Syns files, so a task board or wiki on a page is the repository itself, not a copy. A page sees only the repository, or the placed folder, its session works in, with the access of the Syns account signed in on that machine. Every edit carries the version the page last read: if the files moved since, the edit is refused and the page re-reads, so an edit never overwrites changes it hasn't seen. From a control you press, a page can also share a folder, set its visibility and manage who has access. Needs Thread Pages 1.10.0 or later, and the Syns CLI installed and signed in to a Syns account on each machine whose sessions use it.


Overview

View source

What it does

Thread Pages gives every agent session a web page. A page runs in a sandbox and can reach nothing on your machine. This plugin adds syns.* capabilities to every page, so a page built over a Syns repository — a wiki, a task board, a notebook — can list, read, search and change that repository's files. A page can also act on its own scope as a whole: share its placed folder, set its visibility, manage the repository's people from its root, turn on a placed template's checks, and search public templates and people. Each of those is one CLI command, whose answer and refusals are the CLI's own; they reach other people at once, so a page offers them only on a control the reader presses, saying who gets what.

The page never names a repository. It sees the repository, or the placed folder, its session's folder belongs to, with paths counted from there and whatever access the Syns account logged in on that machine has. A placed folder is a Syns app template copied into a repository as a tool: its page sees that folder alone. In a folder that is no Syns repository, every call answers no_repo.

The plugin also tells agents, in one line, to look for such a tool first. How to place one is the templates' own public TOOLS.md, in bartsoj/syns-templates; the plugin itself depends on no template structure.

How it works

Each call becomes one run of the Syns CLI on the session's own machine, in the session's folder. The plugin opens no repository file itself, holds no credential, and remembers nothing about a repository between calls.

Every write carries the version the page last read. If the repository has moved, the write is refused and the page re-reads; nothing is overwritten unseen. Every commit a page makes records that a page made it, and which session's page.

Pages show published state: an agent's edits reach a page after its turn ends and is pushed. Pages learn of changes by polling one call, syns.repo. Page authors find every method in the page guide, section Capabilities from contributors.

Getting started

  • bb 0.43 or later, with Thread Pages 1.10.0 or later. Earlier Thread Pages pass no session folder, so every call answers no_repo.
  • The Syns CLI, installed and logged in (syns login), on each machine whose sessions should reach a repository. Some methods need a recent CLI: syns upgrade. If bb does not find syns, set its absolute path with bb plugin config syns set synsPath <path>.
  • Then install this plugin. New sessions are told about syns.* automatically; turn that off with bb plugin config syns set agentInstructions false.

More from Syns

More in Thread Content 51

Change what people see or do inside an open thread.

View all