@dmsdc-ai/aigentry-telepty 0.1.12 → 0.1.13
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 +2 -0
- package/cli.js +21 -2
- package/package.json +1 -1
- package/skills/telepty/SKILL.md +20 -3
package/README.md
CHANGED
|
@@ -4,6 +4,8 @@
|
|
|
4
4
|
|
|
5
5
|
`telepty` (Tele-Prompt) is a lightweight background daemon that bridges the gap between the network and interactive AI command-line interfaces. It allows you to seamlessly share, attach to, and inject commands into terminal sessions across different machines.
|
|
6
6
|
|
|
7
|
+
Its primary user experience is prompt-driven operation inside LLM CLIs and the built-in TUI. Raw `telepty ...` commands are the lower-level control surface.
|
|
8
|
+
|
|
7
9
|
## One-Click Installation & Update
|
|
8
10
|
|
|
9
11
|
To install or update `telepty` on any machine (macOS, Linux, or Windows), just run the command for your OS. (Node.js will be automatically installed if you don't have it).
|
package/cli.js
CHANGED
|
@@ -57,6 +57,22 @@ function startDetachedDaemon() {
|
|
|
57
57
|
cp.unref();
|
|
58
58
|
}
|
|
59
59
|
|
|
60
|
+
function relaunchInteractiveManager() {
|
|
61
|
+
return new Promise((resolve, reject) => {
|
|
62
|
+
const child = spawn(process.argv[0], [process.argv[1]], {
|
|
63
|
+
stdio: 'inherit',
|
|
64
|
+
env: {
|
|
65
|
+
...process.env,
|
|
66
|
+
NO_UPDATE_NOTIFIER: '1',
|
|
67
|
+
TELEPTY_DISABLE_UPDATE_NOTIFIER: '1'
|
|
68
|
+
}
|
|
69
|
+
});
|
|
70
|
+
|
|
71
|
+
child.once('error', reject);
|
|
72
|
+
child.once('spawn', () => resolve(child));
|
|
73
|
+
});
|
|
74
|
+
}
|
|
75
|
+
|
|
60
76
|
async function repairLocalDaemon(options = {}) {
|
|
61
77
|
const restart = options.restart !== false;
|
|
62
78
|
const results = cleanupDaemonProcesses();
|
|
@@ -256,10 +272,13 @@ async function manageInteractive() {
|
|
|
256
272
|
execSync('npm install -g @dmsdc-ai/aigentry-telepty@latest', { stdio: 'inherit' });
|
|
257
273
|
console.log('\n\x1b[32m✅ Update complete! Restarting daemon...\x1b[0m');
|
|
258
274
|
await repairLocalDaemon({ restart: true });
|
|
275
|
+
console.log('\x1b[36m↻ Reopening telepty...\x1b[0m\n');
|
|
276
|
+
await relaunchInteractiveManager();
|
|
277
|
+
process.exit(0);
|
|
259
278
|
} catch (e) {
|
|
260
|
-
console.error(
|
|
279
|
+
console.error(`\n❌ Update failed: ${e.message}\n`);
|
|
261
280
|
}
|
|
262
|
-
|
|
281
|
+
continue;
|
|
263
282
|
}
|
|
264
283
|
|
|
265
284
|
if (!response.action || response.action === 'exit') {
|
package/package.json
CHANGED
package/skills/telepty/SKILL.md
CHANGED
|
@@ -1,18 +1,35 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: telepty
|
|
3
|
-
description: Use telepty
|
|
3
|
+
description: Use telepty primarily through LLM CLI prompts and natural-language requests, with raw telepty commands as a secondary path for execution, repair, and session management.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# telepty
|
|
7
7
|
|
|
8
|
-
Use this skill when the user wants help operating `telepty`, recovering a broken local daemon, or managing telepty sessions
|
|
8
|
+
Use this skill when the user wants help operating `telepty`, recovering a broken local daemon, or managing telepty sessions through an LLM CLI prompt.
|
|
9
|
+
|
|
10
|
+
`telepty` is primarily a prompt-driven tool inside LLM CLIs. Raw `telepty ...` commands are the execution layer, not the primary user surface.
|
|
9
11
|
|
|
10
12
|
## Default approach
|
|
11
13
|
|
|
12
|
-
- For interactive human guidance, prefer the `telepty` TUI and
|
|
14
|
+
- For interactive human guidance, prefer LLM CLI prompt examples first, then the `telepty` TUI, and only then raw commands.
|
|
15
|
+
- When explaining telepty usage to a user, always lead with a skill-style or natural-language example first.
|
|
16
|
+
- Only show raw CLI commands after the skill-style example, as the secondary option.
|
|
13
17
|
- For agent execution inside a CLI session, run the underlying `telepty` command directly.
|
|
14
18
|
- When the request is about a broken or duplicated local daemon, repair the daemon before doing session work.
|
|
15
19
|
|
|
20
|
+
## User-facing response order
|
|
21
|
+
|
|
22
|
+
When the user asks how to do something with telepty, respond in this order:
|
|
23
|
+
|
|
24
|
+
1. Show a plain-language or skill-style example first.
|
|
25
|
+
2. Then show the matching CLI command.
|
|
26
|
+
3. Keep maintenance commands behind the user-facing flow unless the user is clearly operating as a CLI power user.
|
|
27
|
+
|
|
28
|
+
Example:
|
|
29
|
+
|
|
30
|
+
- Skill-style example: "telepty에서 해당 세션에 붙어줘" 또는 "telepty에서 로컬 데몬 복구해줘"
|
|
31
|
+
- CLI follow-up: `telepty attach <session_id>` 또는 `telepty cleanup-daemons`
|
|
32
|
+
|
|
16
33
|
## Common actions
|
|
17
34
|
|
|
18
35
|
1. Check whether the current shell is already inside a telepty session:
|