You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,15 @@ Every byte counts. The binary is already ~15MB stripped. Adding dependencies inc
72
72
### 7. AI Agent Access to the Device
73
73
If you are an AI agent and need to test changes, examine logs, or execute commands directly on the Luckfox Pico hardware, **do not guess the IP or password**. Simply ask the user to provide the SSH IP address and password for the device, and use the `run_command` tool via `sshpass` (e.g., `sshpass -p <password> ssh root@<ip>`).
74
74
75
+
### 8. Committing and Pushing Code
76
+
If you are an AI agent, you **MUST NEVER** commit or push code without explicit permission from the user. When you are asked to commit, you must ensure that the tracked `firmware/overlay` directory is completely up to date with whatever modifications were made inside the untracked `luckfox-pico-sdk` directory. This is the only way secondary developers receive OS-level modifications.
77
+
78
+
### 9. Execution Requires Approved Implementation Plan
79
+
If you are an AI agent, you **MUST NEVER** execute code changes, environment modifications, or configuration adjustments without explicitly drafting an implementation plan and receiving the user's explicit approval first. Do not make unauthorized technical assumptions.
80
+
81
+
### 10. Multiple Daemon Instances & PID Tracking
82
+
If `luckyclaw gateway -b` is executed while a daemon started by `/etc/init.d/S99luckyclaw` is already running it will overwrite the `/var/run/luckyclaw.pid` file. Because the init script only tracks the latest PID, subsequent `stop` or `restart` commands will leave the original daemon alive as a zombie, causing duplicate Telegram processing and hallucinated timestamps in session memory. **Fix:** Going forward, making sure we strictly append `&& killall -9 luckyclaw` alongside the init script (which I've started doing in my deploy commands) completely eliminates the possibility of this happening again.
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,8 +86,8 @@ The wizard walks you through:
86
86
87
87
1.**API Provider** — OpenRouter - but you can manually set up OpenAI, Anthropic, Ollama and others in config.json
88
88
2.**API Key** — Paste your key, it's validated in real-time
89
-
3.**Timezone** — Auto-detected via IP, or enter manually
90
-
4.**Messaging** — Optionally set up Telegram (Discord, WhatsApp, and otherscoming soon)
89
+
3.**Timezone** — Explicitly enter your IANA Zone classification via the [Wikipedia TZ Database List](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List)
90
+
4.**Messaging** — Optionally set up Telegram (Discord, WhatsApp, and others coming soon)
91
91
5.**Start gateway** — Optionally start the AI gateway in the background
0 commit comments