lattice-talk 0.1.5 → 0.1.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -0
- package/dist/index.js +9 -2
- package/dist/index.js.map +1 -1
- package/dist/tui/main.js +161 -44
- package/dist/tui/main.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -112,6 +112,12 @@ Both can run side by side on the same workspace.
|
|
|
112
112
|
|
|
113
113
|
The dashboard auto-detects a compatible runtime and tells you clearly if none is found. The MCP server itself needs only plain Node 20+.
|
|
114
114
|
|
|
115
|
+
**Terminal compatibility** — the dashboard adapts to what your terminal can render:
|
|
116
|
+
|
|
117
|
+
- Truecolor terminals (Windows Terminal, iTerm2, VS Code, most modern emulators) get the full palette.
|
|
118
|
+
- ANSI-16 terminals (legacy `conhost.exe`, Terminal.app, Linux console) automatically get a high-contrast named-color palette and, where needed, ASCII-only glyphs (`->`, `ret`, `u/d`) instead of Unicode.
|
|
119
|
+
- `NO_COLOR=1` forces a monochrome look; `LATTICE_ASCII=1` forces ASCII glyphs (useful over SSH/tmux or inside screen readers).
|
|
120
|
+
|
|
115
121
|
## Configuration
|
|
116
122
|
|
|
117
123
|
Setup writes user-level settings to `~/.lattice/config.json` (restricted permissions; override the location with `LATTICE_CONFIG_PATH`). Environment variables always win over saved values.
|
|
@@ -144,6 +150,8 @@ Don't paste passwords, API keys, or secrets into messages or shared memory.
|
|
|
144
150
|
|
|
145
151
|
**Dashboard won't open** — install Bun, or Node.js 26.4+. `serve` still works on Node 20+.
|
|
146
152
|
|
|
153
|
+
**Dashboard opens but looks wrong** — garbled icons or washed-out colors on an old terminal mean the capability detection missed. Try `LATTICE_ASCII=1` for plain-ASCII glyphs, or set `COLORTERM=truecolor` if your terminal does support 24-bit color. `NO_COLOR=1` gives a clean monochrome UI.
|
|
154
|
+
|
|
147
155
|
**Agents can't see each other** — confirm every harness uses the same Redis, namespace, and workspace name, and the same `LATTICE_JOIN_TOKEN` if the workspace is protected. Restart the harness after changing MCP config.
|
|
148
156
|
|
|
149
157
|
**A room is empty** — the agent hasn't joined it. Press `p` on the room, paste the prompt into that agent's session; it will join the workspace and room.
|
package/dist/index.js
CHANGED
|
@@ -21086,7 +21086,7 @@ init_esm_shims();
|
|
|
21086
21086
|
// package.json
|
|
21087
21087
|
var package_default = {
|
|
21088
21088
|
name: "lattice-talk",
|
|
21089
|
-
version: "0.1.
|
|
21089
|
+
version: "0.1.7",
|
|
21090
21090
|
description: "Lattice \u2014 Cross-Harness MCP Session Bus. Shared sessions, DMs, rooms, memory, and OpenTelemetry for agents across Claude Code, Cursor, Codex, and custom harnesses.",
|
|
21091
21091
|
type: "module",
|
|
21092
21092
|
main: "./dist/index.js",
|
|
@@ -58152,7 +58152,14 @@ async function runTui(tuiArgs) {
|
|
|
58152
58152
|
err(`Failed to start TUI runtime (${runtime.cmd}): ${e.message}`);
|
|
58153
58153
|
resolve(1);
|
|
58154
58154
|
});
|
|
58155
|
-
child.on("exit", (code) =>
|
|
58155
|
+
child.on("exit", (code) => {
|
|
58156
|
+
if (code !== null && code !== 0 && code !== 130) {
|
|
58157
|
+
err(
|
|
58158
|
+
"The TUI exited unexpectedly \u2014 this terminal may not support its native renderer (common on older Windows consoles and minimal terminal emulators). `lattice-talk serve` and the MCP tools still work on any terminal."
|
|
58159
|
+
);
|
|
58160
|
+
}
|
|
58161
|
+
resolve(code ?? 0);
|
|
58162
|
+
});
|
|
58156
58163
|
});
|
|
58157
58164
|
}
|
|
58158
58165
|
function printMcpStatus() {
|