instar 0.7.29 → 0.7.31
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/.claude/skills/setup-wizard/skill.md +2 -4
- package/README.md +2 -2
- package/dist/cli.js +0 -0
- package/dist/commands/setup.js +2 -4
- package/package.json +1 -1
- package/.vercel/README.txt +0 -11
- package/.vercel/project.json +0 -1
|
@@ -87,7 +87,7 @@ The terminal session is the on-ramp. Telegram is where the agent experience live
|
|
|
87
87
|
|
|
88
88
|
For **Personal Agents**: emphasize that this agent will be their persistent companion. It grows, learns, and communicates through Telegram. It's not a project tool — it's a presence.
|
|
89
89
|
|
|
90
|
-
For **Project Agents**: emphasize that this agent will own the project's health and development. It monitors, builds, and
|
|
90
|
+
For **Project Agents**: emphasize that this agent will own the project's health and development. It monitors, builds, maintains — and you talk to it through Telegram, just like a personal agent.
|
|
91
91
|
|
|
92
92
|
### Step 2a: The Thesis (Brief)
|
|
93
93
|
|
|
@@ -302,9 +302,7 @@ Frame it clearly:
|
|
|
302
302
|
> - **Mobile access** — your agent is always reachable
|
|
303
303
|
> - **Proactive** — your agent reaches out when something matters
|
|
304
304
|
|
|
305
|
-
For **
|
|
306
|
-
|
|
307
|
-
For **Project Agents**: Telegram is strongly recommended. Frame it as: "Your agent can message you about builds, issues, and progress — you just reply."
|
|
305
|
+
For **both agent types**: Telegram is essential. It's the primary interface — how you talk to your agent from anywhere. Be direct: "This is how you'll talk to your agent." For project agents, add: "Your agent messages you about builds, issues, and progress — you just reply."
|
|
308
306
|
|
|
309
307
|
If the user declines, accept it in one sentence and move on — but they should understand they're choosing the terminal-only experience.
|
|
310
308
|
|
package/README.md
CHANGED
|
@@ -46,8 +46,8 @@ A guided setup handles the rest — identity, Telegram connection, server. Withi
|
|
|
46
46
|
|
|
47
47
|
### Two configurations
|
|
48
48
|
|
|
49
|
-
- **General Agent** — A personal AI partner on your computer. Runs in the background, handles scheduled tasks, messages you proactively, and grows through experience.
|
|
50
|
-
- **Project Agent** — A partner embedded in your codebase. Monitors, builds, maintains, and
|
|
49
|
+
- **General Agent** — A personal AI partner on your computer. Runs in the background, handles scheduled tasks, messages you on Telegram proactively, and grows through experience.
|
|
50
|
+
- **Project Agent** — A partner embedded in your codebase. Monitors, builds, maintains, and messages you on Telegram — the same two-way communication as a general agent, scoped to your project.
|
|
51
51
|
|
|
52
52
|
Once running, the infrastructure is invisible. Your partner manages its own jobs, health checks, evolution, and self-maintenance. You just talk to it.
|
|
53
53
|
|
package/dist/cli.js
CHANGED
|
File without changes
|
package/dist/commands/setup.js
CHANGED
|
@@ -259,10 +259,8 @@ async function runClassicSetup() {
|
|
|
259
259
|
console.log();
|
|
260
260
|
console.log(pc.dim(' Once connected, you just talk — no commands, no terminal.'));
|
|
261
261
|
console.log(pc.dim(' Topic threads, message history, mobile access, proactive notifications.'));
|
|
262
|
-
|
|
263
|
-
|
|
264
|
-
console.log(pc.dim(' For a personal agent, Telegram IS the interface.'));
|
|
265
|
-
}
|
|
262
|
+
console.log();
|
|
263
|
+
console.log(pc.dim(' Telegram IS the interface — for any agent type.'));
|
|
266
264
|
console.log();
|
|
267
265
|
console.log(pc.dim(` If you don't have Telegram yet: ${pc.cyan('https://telegram.org/apps')}`));
|
|
268
266
|
console.log(pc.dim(' Install it on your phone first — you\'ll need it to log in on the web.'));
|
package/package.json
CHANGED
package/.vercel/README.txt
DELETED
|
@@ -1,11 +0,0 @@
|
|
|
1
|
-
> Why do I have a folder named ".vercel" in my project?
|
|
2
|
-
The ".vercel" folder is created when you link a directory to a Vercel project.
|
|
3
|
-
|
|
4
|
-
> What does the "project.json" file contain?
|
|
5
|
-
The "project.json" file contains:
|
|
6
|
-
- The ID of the Vercel project that you linked ("projectId")
|
|
7
|
-
- The ID of the user or team your Vercel project is owned by ("orgId")
|
|
8
|
-
|
|
9
|
-
> Should I commit the ".vercel" folder?
|
|
10
|
-
No, you should not share the ".vercel" folder with anyone.
|
|
11
|
-
Upon creation, it will be automatically added to your ".gitignore" file.
|
package/.vercel/project.json
DELETED
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"projectId":"prj_evM5LcItYL3IAmw8zNvEPGrHeaya","orgId":"team_dHctwIDcV3X9ydapQlCPHFGI","projectName":"claude-agent-kit"}
|