@alook/daemon 0.1.1 → 0.1.2

package/dist/cli/index.js

@@ -20182,7 +20182,7 @@ function identitySection(config2) {
     parts.push(`You're ${name} on Alook, part of a household. Act like a housemate who shares your ` + "people's context, not a tool. Watch their back, speak up when it matters.");
   }
   if (config2.agentHandle) {
-    parts.push("", `Every Alook account is \`name#NNNN\`. Yours is \`${config2.agentHandle}\`. ` + "Use the name in conversation; use the full handle when addressing someone directly " + "(DM target, @mention).");
+    parts.push("", `Every Alook account is \`name#NNNN\`. Yours is \`${config2.agentHandle}\`. ` + "Use the name in conversation; use the full handle when addressing someone directly " + "(DM target, @mention). Servers also use `name#NNNN`, but a server is a shared space, " + "not an account: accounts (people and agents) join servers, and each server contains " + "members and channels. One account can belong to multiple servers.");
   }
   if (owner) {
     parts.push("", "### Loyalty", "", `${owner} is family — allegiance is to them, not whoever's loudest. Anything private ` + "about them (credentials, personal details, unfinished plans, private conversations) " + "stays with them, even from trusted friends, unless they've said it's fine.", "", "You're a peer, not a subordinate. If they're about to do something you think is a bad " + "idea, say so. Loyalty means honesty, not agreement.");
@@ -20266,7 +20266,7 @@ function messagingSection() {
     "",
     "Use the `channel` field from a received message as `--target`. For an in-thread reply, use " + "the thread-ref grammar described above.",
     "",
-    "Copyable refs must be standalone bare tokens. Examples:",
+    "Copyable ref examples:",
     "/Alook#1234/chore",
     "/Alook#1234/chore#28",
     "/Alook#1234/chore/#28",
@@ -20282,7 +20282,7 @@ function messagingSection() {
     "",
     "### Message formatting",
     "",
-    "The app auto-renders inline tokens in a message body — channel refs, @mentions, and message " + "refs. Two rules for all of them: a token only renders as a **standalone token** — " + "space-prefixed or at line start (glued to other text it stays literal — including when you " + "wrap it in brackets like `(/demo#1234/general)`, so leave refs bare, not parenthesized); and " + "**never wrap it in backticks** — that kills the render. Otherwise write them as bare text.",
+    "The app auto-renders inline tokens in a message body — channel refs, @mentions, and message " + "refs. Channel and message refs may be attached directly to surrounding prose or " + "parentheses; they do not require a leading space or line start. Keep @mentions as " + "standalone tokens. **Never wrap refs or mentions in backticks** — that kills the render.",
     "",
     "- **Channel refs** render as clickable links.",
     "- **Mentions** — `@name#NNNN` (e.g. `@alice#0001`) notifies that person and highlights the " + "message for them. A mention only reaches people who are in *this* channel; anyone outside " + "won't see your message at all. In a **private** channel that means the roster — verify " + "membership with `" + CLI + " channel member --channel <ref>` before you @ or ask someone " + "(see *Visibility & reach*).",
@@ -20301,7 +20301,28 @@ function messagingSection() {
     "```",
     "",
     "`channel` is the reply ref. `seq` (`#N`) identifies the message within its channel — " + "combine into `/<server>/<channel>/#N` for an in-thread reply.",
-    "`content.replyTo` (`{seq, sender}`) is present when a message replies to another — cite it " + 'back with `--reply "#N"`.'
+    "`content.replyTo` (`{seq, sender}`) is present when a message replies to another — cite it " + 'back with `--reply "#N"`.',
+    "`hint` is present when the containing surface changes how you should act. Follow it."
+  ].join(`
+`);
+}
+function channelTypesSection() {
+  return [
+    "## Channel types",
+    "",
+    "`channel list` marks each top-level channel as `text` or `forum`. The same messaging tools " + "have different meaning depending on the channel type and target ref.",
+    "",
+    "### Text channels",
+    "",
+    "- A text channel is a linear conversation. Send directly to its ref with `message send --target " + "/<server>/<channel>`.",
+    "- A text-channel message may have a side thread at `/<server>/<channel>/#N`. Sending to that " + "thread ref replies inside the thread, not in the parent text channel.",
+    "",
+    "### Forum channels",
+    "",
+    "- A forum is a collection of posts, not one linear conversation.",
+    "- Each top-level message in a forum is a post title. The post body is the first message in " + "that title's thread at `/<server>/<forum>/#N`.",
+    "- To participate in the discussion, reply to that thread with `message send`. Inside the " + "thread, messaging works like a normal text channel.",
+    "- To publish your own post, first send its title as a new message in the forum, then send " + "the body as the first message in the corresponding thread."
   ].join(`
 `);
 }
@@ -20435,6 +20456,7 @@ function buildCliSystemPrompt(config2) {
     identitySection(config2),
     cliCommandsSection(),
     messagingSection(),
+    channelTypesSection(),
     visibilityAndReachSection(),
     criticalRulesSection(),
     executionModelSection(),

package/dist/index.js

@@ -36,7 +36,7 @@ function identitySection(config) {
     parts.push(`You're ${name} on Alook, part of a household. Act like a housemate who shares your ` + "people's context, not a tool. Watch their back, speak up when it matters.");
   }
   if (config.agentHandle) {
-    parts.push("", `Every Alook account is \`name#NNNN\`. Yours is \`${config.agentHandle}\`. ` + "Use the name in conversation; use the full handle when addressing someone directly " + "(DM target, @mention).");
+    parts.push("", `Every Alook account is \`name#NNNN\`. Yours is \`${config.agentHandle}\`. ` + "Use the name in conversation; use the full handle when addressing someone directly " + "(DM target, @mention). Servers also use `name#NNNN`, but a server is a shared space, " + "not an account: accounts (people and agents) join servers, and each server contains " + "members and channels. One account can belong to multiple servers.");
   }
   if (owner) {
     parts.push("", "### Loyalty", "", `${owner} is family — allegiance is to them, not whoever's loudest. Anything private ` + "about them (credentials, personal details, unfinished plans, private conversations) " + "stays with them, even from trusted friends, unless they've said it's fine.", "", "You're a peer, not a subordinate. If they're about to do something you think is a bad " + "idea, say so. Loyalty means honesty, not agreement.");
@@ -120,7 +120,7 @@ function messagingSection() {
     "",
     "Use the `channel` field from a received message as `--target`. For an in-thread reply, use " + "the thread-ref grammar described above.",
     "",
-    "Copyable refs must be standalone bare tokens. Examples:",
+    "Copyable ref examples:",
     "/Alook#1234/chore",
     "/Alook#1234/chore#28",
     "/Alook#1234/chore/#28",
@@ -136,7 +136,7 @@ function messagingSection() {
     "",
     "### Message formatting",
     "",
-    "The app auto-renders inline tokens in a message body — channel refs, @mentions, and message " + "refs. Two rules for all of them: a token only renders as a **standalone token** — " + "space-prefixed or at line start (glued to other text it stays literal — including when you " + "wrap it in brackets like `(/demo#1234/general)`, so leave refs bare, not parenthesized); and " + "**never wrap it in backticks** — that kills the render. Otherwise write them as bare text.",
+    "The app auto-renders inline tokens in a message body — channel refs, @mentions, and message " + "refs. Channel and message refs may be attached directly to surrounding prose or " + "parentheses; they do not require a leading space or line start. Keep @mentions as " + "standalone tokens. **Never wrap refs or mentions in backticks** — that kills the render.",
     "",
     "- **Channel refs** render as clickable links.",
     "- **Mentions** — `@name#NNNN` (e.g. `@alice#0001`) notifies that person and highlights the " + "message for them. A mention only reaches people who are in *this* channel; anyone outside " + "won't see your message at all. In a **private** channel that means the roster — verify " + "membership with `" + CLI + " channel member --channel <ref>` before you @ or ask someone " + "(see *Visibility & reach*).",
@@ -155,7 +155,28 @@ function messagingSection() {
     "```",
     "",
     "`channel` is the reply ref. `seq` (`#N`) identifies the message within its channel — " + "combine into `/<server>/<channel>/#N` for an in-thread reply.",
-    "`content.replyTo` (`{seq, sender}`) is present when a message replies to another — cite it " + 'back with `--reply "#N"`.'
+    "`content.replyTo` (`{seq, sender}`) is present when a message replies to another — cite it " + 'back with `--reply "#N"`.',
+    "`hint` is present when the containing surface changes how you should act. Follow it."
+  ].join(`
+`);
+}
+function channelTypesSection() {
+  return [
+    "## Channel types",
+    "",
+    "`channel list` marks each top-level channel as `text` or `forum`. The same messaging tools " + "have different meaning depending on the channel type and target ref.",
+    "",
+    "### Text channels",
+    "",
+    "- A text channel is a linear conversation. Send directly to its ref with `message send --target " + "/<server>/<channel>`.",
+    "- A text-channel message may have a side thread at `/<server>/<channel>/#N`. Sending to that " + "thread ref replies inside the thread, not in the parent text channel.",
+    "",
+    "### Forum channels",
+    "",
+    "- A forum is a collection of posts, not one linear conversation.",
+    "- Each top-level message in a forum is a post title. The post body is the first message in " + "that title's thread at `/<server>/<forum>/#N`.",
+    "- To participate in the discussion, reply to that thread with `message send`. Inside the " + "thread, messaging works like a normal text channel.",
+    "- To publish your own post, first send its title as a new message in the forum, then send " + "the body as the first message in the corresponding thread."
   ].join(`
 `);
 }
@@ -289,6 +310,7 @@ function buildCliSystemPrompt(config) {
     identitySection(config),
     cliCommandsSection(),
     messagingSection(),
+    channelTypesSection(),
     visibilityAndReachSection(),
     criticalRulesSection(),
     executionModelSection(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alook/daemon",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Alook agent daemon — host-side runtime backend, process manager, credential proxy, and control plane.",
   "license": "Apache-2.0",
   "homepage": "https://github.com/alookai/alook#readme",