+4
.env.example
+4
.env.example
+159
CONFIG.md
+159
CONFIG.md
···+If both config file and environment variables are present, environment variables take precedence.+If you're currently using environment variables (`.env` file), you can easily migrate to YAML using the automated migration script:+- The configuration loader will warn if it can't find `config.yaml` and falls back to environment variables
+81
config.example.yaml
+81
config.example.yaml
···+value: "I haven't seen any bluesky users yet. I will update this block when I learn things about users, identified by their handles such as @cameron.pfiffer.org."+description: "A block to store your understanding of users you talk to or observe on the bluesky social network."
+228
config_loader.py
+228
config_loader.py
···+'description': config.get('bot.agent.description', 'A social media agent trapped in the void.'),
+322
migrate_config.py
+322
migrate_config.py
···+response = input("💾 Proceed with migration? This will update config.yaml (y/n): ").lower().strip()
+173
test_config.py
+173
test_config.py
···+f" - Priority users: {len(priority_users)} ({', '.join(priority_users[:3])}{'...' if len(priority_users) > 3 else ''})")
+20
-30
tools/blocks.py
+20
-30
tools/blocks.py
·····················
+16
-8
register_tools.py
+16
-8
register_tools.py
············+parser.add_argument("agent", nargs="?", default=None, help=f"Agent name (default: {agent_config['name']})")···
+23
requirements.txt
+23
requirements.txt
···
+2
-2
README.md
+2
-2
README.md
······