ltcai 4.7.0 → 5.0.0

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.
@@ -15,8 +15,8 @@
15
15
  } catch (e) {}
16
16
  })();
17
17
  </script>
18
- <script type="module" crossorigin src="/static/app/assets/index-DwX3rNfA.js"></script>
19
- <link rel="stylesheet" crossorigin href="/static/app/assets/index-DFmuiJ6t.css">
18
+ <script type="module" crossorigin src="/static/app/assets/index-FR1UZkCD.js"></script>
19
+ <link rel="stylesheet" crossorigin href="/static/app/assets/index-DuYYT2oh.css">
20
20
  </head>
21
21
  <body>
22
22
  <div id="root"></div>
@@ -1,56 +0,0 @@
1
- #!/bin/zsh
2
- # Launch a dedicated Grok TUI session wired to the "pts_grok" Discord bot.
3
- # This lets you collaborate with pts_openclaw and pts_claudecode in the shared channel
4
- # by having them @mention pts_grok (or you mentioning it).
5
- #
6
- # Prerequisites:
7
- # 1. Create a brand new Discord Application + Bot in https://discord.com/developers/applications
8
- # - Name the bot exactly "pts_grok" (for easy @mentions).
9
- # - Enable "Message Content Intent" under Privileged Gateway Intents.
10
- # - Generate / Reset the Bot token (copy it once).
11
- # 2. Invite the new bot to your server using OAuth2 URL Generator (bot scope + View Channels,
12
- # Send Messages, Send Messages in Threads, Read Message History, Attach Files, Add Reactions).
13
- # 3. Put the token into ~/.grok/channels/discord-pts-grok/.env as DISCORD_BOT_TOKEN=...
14
- # 4. After creating the bot, note its User ID (right-click the bot in Discord → Copy User ID, with Dev Mode on).
15
- # Then add that ID to the other agents' botAllowFrom lists (and they will add yours).
16
- #
17
- # Usage:
18
- # cd ~/Downloads/Lattice\ AI
19
- # ./scripts/launch-pts-grok.sh
20
- #
21
- # In that new terminal session, the "discord" MCP tools will be bound to pts_grok.
22
- # Mentioning pts_grok from pts_openclaw (or the human) in channel 1506662093309608026
23
- # will be delivered here.
24
-
25
- set -euo pipefail
26
-
27
- export DISCORD_STATE_DIR="$HOME/.grok/channels/discord-pts-grok"
28
-
29
- # Safety: ensure the secret file has sane permissions
30
- chmod 600 "$DISCORD_STATE_DIR/.env" 2>/dev/null || true
31
-
32
- # Make sure the token is present and looks real (not just empty or placeholder)
33
- token_line=$(grep '^DISCORD_BOT_TOKEN=' "$DISCORD_STATE_DIR/.env" 2>/dev/null | tail -1 || true)
34
- token_value="${token_line#DISCORD_BOT_TOKEN=}"
35
-
36
- if [[ -z "$token_value" || ${#token_value} -lt 40 ]]; then
37
- echo "ERROR: DISCORD_BOT_TOKEN is missing or too short in $DISCORD_STATE_DIR/.env"
38
- echo "Edit it first with the real token from Discord Developer Portal → Your pts_grok bot → Reset Token."
39
- echo "Example line: DISCORD_BOT_TOKEN=MTxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
40
- exit 1
41
- fi
42
-
43
- # Quick sanity so we don't launch with the placeholder comment
44
- if echo "$token_value" | grep -qi 'PUT_YOUR\|MASKED\|edit me'; then
45
- echo "ERROR: The token in $DISCORD_STATE_DIR/.env still contains placeholder text."
46
- echo "Replace it with the actual bot token."
47
- exit 1
48
- fi
49
-
50
- cd "$(dirname "$0")/.."
51
-
52
- echo "Launching Grok as pts_grok (state: $DISCORD_STATE_DIR)"
53
- echo "Make sure the 'discord' MCP / plugin is enabled (use /mcps or /plugins in the TUI if needed)."
54
- echo
55
-
56
- exec "$HOME/.grok/bin/grok" "$@"