Agent integration: pi skill + EVIE_CHAT_ID/EVIE_SOCKET env injection #61

New issue

Closed

opened 2026-07-08 02:13:02 +08:00 by weiwen · 0 comments

weiwen commented

2026-07-08 02:13:02 +08:00

Owner

Parent

#55

What to build

The end-to-end payoff: let the notes agent drive evie through the Control Plane, so an in-conversation "remind me in 1 hour to X" becomes a real Schedule the agent created.

Two parts:

Env injection at spawn: the Daemon injects EVIE_CHAT_ID (the session's own chat) and EVIE_SOCKET into the interactive pi process environment when it spawns a session, so the agent's evie … calls target its own chat and daemon with no arguments.
Skill (not an extension): ship an in-repo pi Skill documenting the evie CLI — the available Verbs and that evie --help carries the detail — wired via the [pi].skills config. pi exposes a shell/command-exec tool (confirmed), so the agent invokes evie … directly; no custom extension.

Demoable: in Telegram, "remind me in 1 minute to check the deploy" → the agent runs evie schedule --in 1m -- prompt "…" (or -- send "…") → the reminder fires and is delivered ~1 minute later.

Acceptance criteria

The interactive pi process is spawned with EVIE_CHAT_ID (its own chat) and EVIE_SOCKET in its environment.
An in-repo pi Skill documents the evie CLI and is wired via [pi].skills.
From a Telegram conversation, a "remind me…" request results in the agent creating a Schedule via the CLI, and the reminder is delivered at the scheduled time to the same chat.
evie schedule --name collisions/updates issued by the agent behave per the schedule contract (idempotent re-issue with --update).
Uses CONTEXT.md vocabulary (Skill, Control Plane, CLI); respects ADR 0006.

Blocked by

## Parent #55 ## What to build The end-to-end payoff: let the notes agent drive evie through the Control Plane, so an in-conversation "remind me in 1 hour to X" becomes a real Schedule the agent created. Two parts: - **Env injection at spawn:** the Daemon injects `EVIE_CHAT_ID` (the session's own chat) and `EVIE_SOCKET` into the interactive `pi` process environment when it spawns a session, so the agent's `evie …` calls target its own chat and daemon with no arguments. - **Skill (not an extension):** ship an in-repo `pi` **Skill** documenting the `evie` CLI — the available Verbs and that `evie --help` carries the detail — wired via the `[pi].skills` config. `pi` exposes a shell/command-exec tool (confirmed), so the agent invokes `evie …` directly; no custom extension. Demoable: in Telegram, "remind me in 1 minute to check the deploy" → the agent runs `evie schedule --in 1m -- prompt "…"` (or `-- send "…"`) → the reminder fires and is delivered ~1 minute later. ## Acceptance criteria - [ ] The interactive `pi` process is spawned with `EVIE_CHAT_ID` (its own chat) and `EVIE_SOCKET` in its environment. - [ ] An in-repo `pi` Skill documents the `evie` CLI and is wired via `[pi].skills`. - [ ] From a Telegram conversation, a "remind me…" request results in the agent creating a Schedule via the CLI, and the reminder is delivered at the scheduled time to the same chat. - [ ] `evie schedule --name` collisions/updates issued by the agent behave per the schedule contract (idempotent re-issue with `--update`). - [ ] Uses CONTEXT.md vocabulary (Skill, Control Plane, CLI); respects ADR 0006. ## Blocked by - #60

weiwen added the

ready-for-agent

label

2026-07-08 02:13:02 +08:00

weiwen referenced this issue from a commit

2026-07-12 18:25:22 +08:00

feat: inject EVIE_CHAT_ID and EVIE_SOCKET into pi process env at spawn; ship evie CLI skill

weiwen referenced this issue from a commit

2026-07-12 18:25:22 +08:00

feat: always load the bundled evie CLI skill when spawning pi

weiwen referenced this issue from a pull request that will close it,

2026-07-12 18:25:37 +08:00