nolty / TelegramConfig
CLAUDE.md1 starsChanged 6 months agoMITView on GitHub
This subfolder exists ONLY to scope the Telegram plugin to this directory. Claude Code reads .claude/settings.json from the workspace root only — it doesn't walk up. By putting the Telegram-enabled settings in TelegramConfig/.claude/settings.json and the parent nolty/.claude/settings.json set to plugin-disabled, you can: The clawd-restart.sh script CDs into this directory before launching claude. Your real home is the parent directory. Read the parent's CLAUDE.md first: Everything else (SOUL, IDENTITY, USER, MEMORY, HEARTBEAT, AGENTS, TOOLS, skills/, agents/) lives in the parent. Use…
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- chatgpt-imageSkill
- cron-managementSkill
- heartbeatSkill
- nolty-moodSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Run Nolty from TelegramConfig/ → Telegram plugin loads
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
TelegramConfig/
This subfolder exists ONLY to scope the Telegram plugin to this directory.
Claude Code reads .claude/settings.json from the workspace root only — it doesn't walk up. By putting the Telegram-enabled settings in TelegramConfig/.claude/settings.json and the parent nolty/.claude/settings.json set to plugin-disabled, you can:
- Run Nolty from
TelegramConfig/→ Telegram plugin loads - Open the parent
nolty/in an IDE → no duplicate Telegram listener spawned
The clawd-restart.sh script CDs into this directory before launching claude.
On session start
Your real home is the parent directory. Read the parent's CLAUDE.md first:
/Users/YOUR_USER/Documents/CodingProjects/nolty/CLAUDE.mdEverything else (SOUL, IDENTITY, USER, MEMORY, HEARTBEAT, AGENTS, TOOLS, skills/, agents/) lives in the parent. Use relative paths like ../SOUL.md or absolute paths to reach them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

