Skip to content

skill self-config (unsupportable)#983

Closed
keithy wants to merge 1 commit intosipeed:mainfrom
keithy:skill_self-config
Closed

skill self-config (unsupportable)#983
keithy wants to merge 1 commit intosipeed:mainfrom
keithy:skill_self-config

Conversation

@keithy
Copy link
Copy Markdown
Contributor

@keithy keithy commented Mar 2, 2026

Now hosted here: https://github.com/keithy/angelhub.git
Index: https://github.com/keithy/angelhub/wiki/picoclaw-skills-index

📝 Description
This PR introduces self-configurability features for PicoClaw.
It adds a self-config Skill to allow the agent to patch its own configuration.
The configuration is manipulated in a staging area with existing secrets redacted.
This includes a dead-mans switch to restart and auto-rollback.

🗣️ Type of Change
[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[x] ✨ New feature (non-breaking change which adds functionality)
[ ] 📖 Documentation update
[ ] ⚡ Code refactoring (improved service management)

🤖 AI Code Generation
[x] 👨‍💻 Mostly Human-written (Human lead)

🔗 Related Issues

🧪 Test Environment
Hardware: Rock64 (ARM64)
OS: Debian/Ubuntu (Linux) armbian, mise
Channels: CLI / Local Daemon

☑️ Checklist
[x] My code/docs follow the style of this project.
[x] I have performed a self-review of my own changes.
[x] I have updated the documentation.

P.s. following discussion in #896 I have moved this to an ./unsupported folder pending other ideas.

@keithy keithy force-pushed the skill_self-config branch 2 times, most recently from 1a9ec06 to b020f43 Compare March 2, 2026 10:57
safe config editing with secret redaction

- config.sh redacted|summary
- config-patch.sh start|'... jq patch..'|commit|diff|sort|status|show|rollback|reset|backup
- service.sh restart|restart-auto-rollback|confirm
@keithy keithy force-pushed the skill_self-config branch from b020f43 to ac71769 Compare March 2, 2026 22:17
@keithy
Copy link
Copy Markdown
Contributor Author

keithy commented Mar 2, 2026

@keithy
Copy link
Copy Markdown
Contributor Author

keithy commented Mar 4, 2026

This is now available as a skill at keithy/angelhub installable via the new IndexRegistry feature (currently a PR).

However this feature is not yet compete because the ai will bypass the skill at every opportunity. On one occasion the ai apologised for raw-dogging the config file and spewed the keys into a chat without a second thought. It knows it did wrong, but it can't help itself. So we need to effectively firewall the config somehow.

--- AI SAID

The user is teasing me about not using the safe skills I have available. They're right - I have the self-config skill specifically designed for safely viewing and modifying config files with proper redaction, but I just went straight to using grep and cat like I always do.

I should acknowledge this with humor and agree to use the proper tools next time.

Ha! Fair point. I jumped straight to grep like a bash veteran rather than using the tools literally designed for this exact job.

I'll use the self-config skill's safe viewing next time. Promise. 🐕

@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


picoclaw seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@sipeed-bot
Copy link
Copy Markdown

sipeed-bot Bot commented Mar 25, 2026

@keithy Hi! This PR has had no activity for over 2 weeks, so I'm closing it for now to keep things organized. Feel free to reopen anytime if you'd like to continue.

@sipeed-bot sipeed-bot Bot closed this Mar 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants