@segmentstream/agent 0.1.0 → 0.1.2

package/README.md

@@ -18,31 +18,32 @@ npm install @segmentstream/agent eve@0.76.3
 
 ## Set up
 
-The workspace's `agent/` directory is an eve app in eve's flat layout, a package of its own like
-`ontology/`:
+The workspace's `agent/` directory is an eve app in eve's documented layout, a package of its own
+like `ontology/`: the package files at the root, the authored files under `agent/agent/`:
 
 ```text
 agent/
 ├── package.json            # eve and @segmentstream/agent, both pinned; "build": "eve build"
 ├── segmentstream.json      # what the extension mounts, and what the platform reads at deploy
-├── agent.ts                # model, reasoning, limits
-├── instructions.md         # who the company is, how the agent behaves
-└── extensions/
-    └── segmentstream.ts    # mounts this package with segmentstream.json
+└── agent/                  # eve's agent directory
+    ├── agent.ts            # model, reasoning, limits
+    ├── instructions.md     # who the company is, how the agent behaves
+    └── extensions/
+        └── segmentstream.ts  # mounts this package with segmentstream.json
 ```
 
-**`extensions/segmentstream.ts`** mounts the extension. The file name is the mount's namespace, so
+**`agent/agent/extensions/segmentstream.ts`** mounts the extension. The file name is the mount's namespace, so
 every contribution is named `segmentstream__…`:
 
 ```ts
 import { segmentstream } from "@segmentstream/agent/extension";
 
-import config from "../segmentstream.json";
+import config from "../../segmentstream.json";
 
 export default segmentstream(config);
 ```
 
-**`agent.ts`** chooses the model once per session:
+**`agent/agent/agent.ts`** chooses the model once per session:
 
 ```ts
 import { defineAgent } from "eve";
@@ -122,9 +123,10 @@ share a group chat's session never share a client.
   preview never answers a real chat. Without `channels.telegram` it answers 404.
 - **Pairing.** Messages from bots and channel posts are dropped. The sender's Telegram account is
   looked up with the ontology service on every message, so a revocation stops at once. An unknown
-  sender who writes privately gets a link to `/agent/connect?code=…`, valid for ten minutes. In a
-  group, the agent only asks an unknown sender to message it privately, because anyone in the group
-  could open a link posted there. A revoked pairing or an inactive member gets a short refusal.
+  sender who writes privately gets a message with a **Connect account** button that opens
+  `/agent/connect?code=…`, valid for ten minutes. In a group, the agent only asks an unknown sender to
+  message it privately, with a button to the bot's chat, because anyone in the group could open a
+  pairing link posted there. A revoked pairing or an inactive member gets a short refusal.
 - **Who the agent is.** A paired sender's turn runs with the principal id `telegram:<user>`
   (`telegram:<chat>:<user>` in groups) and the attributes `memberId`, `memberName`, `roles`,
   `chatId`, `chatType` and `username`.

package/dist/extension/config.d.ts

@@ -1,6 +1,6 @@
 /**
  * The extension's configuration: `agent/segmentstream.json`, mounted by
- * `agent/extensions/segmentstream.ts` and read by the platform at deploy.
+ * `agent/agent/extensions/segmentstream.ts` and read by the platform at deploy.
  *
  * eve validates a mount's configuration with a Standard Schema. The schema below is written by
  * hand, so the package adds no second schema library next to the Effect Schema the rest of the

package/dist/extension/lib/telegram/inbound.d.ts

@@ -10,7 +10,7 @@ import { type Transcriber } from "./voice.js";
  * eve's Telegram `onMessage` hook, in the order `agent-design.md` gives:
  *
  * 1. The hard gate, with no model: bots, channel posts and senders without a live pairing never
- *    start a turn. An unknown sender who writes to the bot privately gets a pairing link.
+ *    start a turn. An unknown sender who writes to the bot privately gets a pairing button.
  * 2. Voice becomes text, so the router and the agent read what was said.
  * 3. The router answers or observes. An observed message goes to the chat's ring and stops here.
  * 4. An answered message dispatches as the paired member, with the ring ahead of it as context.

package/dist/extension/lib/telegram/inbound.mjs

@@ -8,8 +8,15 @@ import { telegramPrincipal } from "./principal.mjs";
 import { observedChatKey, observedContext } from "./observed.mjs";
 import { isAddressed, routeMessage } from "./router.mjs";
 import { voiceNote, voiceOf, voiceText } from "./voice.mjs";
-const UNKNOWN_PRIVATE = "I don't know who you are yet. Open this link and sign in to connect your Telegram account; it works for ten minutes:";
+const UNKNOWN_PRIVATE = "Hi, I don't know you yet. Connect your Telegram account to the workspace and I'll act as you. The button works for ten minutes.";
+const UNKNOWN_IN_GROUP = "I don't know you yet. Message me privately to connect your account.";
 const REFUSED = "Your access to this agent was revoked, or your membership is inactive. Ask a workspace administrator.";
+function buttonTo(text, url) {
+	return { inline_keyboard: [[{
+		text,
+		url
+	}]] };
+}
 function display(user) {
 	if (user.username !== void 0) return `@${user.username}`;
 	const name = [user.firstName, user.lastName].filter((part) => part !== void 0 && part !== "").join(" ");
@@ -27,7 +34,10 @@ function observedMessage(message, text) {
 	};
 }
 function unknownInGroup(bot) {
-	return `I don't know who you are yet. Message me privately to connect your account.${bot?.username === void 0 ? "" : ` https://t.me/${bot.username}`}`;
+	return bot?.username === void 0 ? { text: UNKNOWN_IN_GROUP } : {
+		text: UNKNOWN_IN_GROUP,
+		reply_markup: buttonTo("Message me", `https://t.me/${bot.username}`)
+	};
 }
 async function answerUnpaired(input) {
 	const { context, message, lookup, dependencies } = input;
@@ -45,7 +55,10 @@ async function answerUnpaired(input) {
 		externalId: message.from.id,
 		...sender === void 0 ? {} : { display: sender }
 	});
-	await context.telegram.post(`${UNKNOWN_PRIVATE}\n${dependencies.connectUrl(pairing.code)}`);
+	await context.telegram.post({
+		text: UNKNOWN_PRIVATE,
+		reply_markup: buttonTo("Connect account", dependencies.connectUrl(pairing.code))
+	});
 }
 async function handleInboundMessage(input) {
 	const { context, dependencies } = input;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@segmentstream/agent",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Mount a SegmentStream workspace's agent on eve: the ontology as tools, acting as the member who writes, and Telegram through the workspace's connection.",
   "license": "Apache-2.0",
   "author": "SegmentStream",