46 lines
1.5 KiB
Markdown
46 lines
1.5 KiB
Markdown
## Completed Projects
|
|
|
|
1. **[Termix](https://github.com/Termix-SSH/Termix)** - SSH terminal project ✅
|
|
|
|
## Active Investigations
|
|
|
|
### 1. Double-Response on Cron Results
|
|
**Status:** Closed (per user)
|
|
**Symptom:** User saw duplicate bot responses for each cron event. Cron results arrived as both an "announce" summary and a "system reminder".
|
|
**Resolution:** Closed out per user request.
|
|
|
|
### 2. nanogpt kimi-k2.5:thinking — Tool Call & Output Issues
|
|
**Status:** Closed (per user)
|
|
**Summary:** Tool/output issues documented; sanitized provider bug report had been prepared.
|
|
**Resolution:** Closed out per user request.
|
|
|
|
## Future Work
|
|
|
|
1. Weekly cron for CapMetro service change monitoring
|
|
2. Thread follow-up mechanism for VT scan verdicts
|
|
|
|
---
|
|
|
|
## Decision Criteria: Native Claw vs n8n
|
|
|
|
**Use Native Claw (Skills + Cron) when:**
|
|
- ✅ Simple data fetching/parsing (web scraping, API calls)
|
|
- ✅ No sensitive credentials needed (or read-only tokens)
|
|
- ✅ Logic can be scripted (bash/python)
|
|
- ✅ Output is text-based (notifications, summaries)
|
|
- ✅ Doesn't need visual workflow debugging
|
|
|
|
**Examples:** GitHub notifications, CapMetro route monitoring, RSS checks
|
|
|
|
**Use n8n when:**
|
|
- ✅ Complex multi-step workflows with branching
|
|
- ✅ Needs credential isolation per workflow
|
|
- ✅ Visual workflow debugging beneficial
|
|
- ✅ Integration with many external services
|
|
- ✅ Non-technical users need to modify workflows
|
|
- ✅ Requires persistent state between runs
|
|
|
|
**Examples:** Multi-service automation, data pipelines, webhook orchestration
|
|
|
|
**Current Date:** 2026-02-04
|