Inbox
no feeds yet
store: …
idle
accountable: …
—
store — / —
weir
@BotFather → /newbot, paste its token, and DM it links/notes from your phone — URL messages (incl. Google Discover shares) flow into Saved Links and get resolved; pure-text notes are stashed for the coming notes view. No server/webhook needed (api.telegram.org is CORS-friendly); the token is stored encrypted (OPFS vault), never in backups. Only messages from you are ingested — it auto-locks to your Telegram id on your first message (strangers who find the bot are ignored). One consumer per bot — don't reuse a bot that has a webhook or another poller. If weir's been closed past ~24h, fall back to a conversation export + Import.node numen-bridge.js --app weir --port 7801 --info, paste the port:token, connect (uses the @gcu/accountable extension, like the cataloger). Over a folder (no port, no extension): run … --transport fs --folder <dir> --info, pick that folder here, paste the token, connect — sync the folder (e.g. Syncthing) to drive weir from another machine. Multiple channels at once: each fs folder is a separate agent — the first is the librarian (weir-desk), then dev (the weir repo), cowork (Claude Desktop), … — folder = identity, so they all connect together (SPEC-numen-multichannel). weir remembers each (origin-local, never in backups).GCU-sync Dropbox app folder (/Apps/GCU-sync/weir). Connect once per device. The hub polls feeds; readers (e.g. a tablet) skip polling and receive the corpus via sync. Role changes take effect on reload. The first full sync of a large corpus is slow.weir … in the status bar to check for updates from anywhere.out/ (your vocabulary + recent captures) and ingests dispatches from in/ as author-tagged notes. Point this at the folder you sync (Syncthing, …) — how it's shared is up to you; weir just reads the folder. Its README.md documents the protocol for the collaborator.~/Documents/GitHub) read-only so the agent can ingest a repo's docs as a source (weir_ingestRepo with paths:[…]) without sending every doc's full text through the tool call. weir reads only the exact files named in an ingest — it never browses the tree — and can never write here (read-only grant).