ElasticClaw configuration for Faster Next — templates and factories for automated claw workflows.
.elasticclaw/
templates/
/ # One directory per claw template
Date: 2026-03-31
Threat: [email protected] pulls in [email protected] — confirmed malware (supply chain attack)
Action: DO NOT upgrade axios. Pin versions. Audit lockfiles.
| Repo | File | Section | Axios Version |
|---|
| # Autoprobe Bot Instructions | |
| You are an autoprobe research bot. Your goal is to make autoprobe actually work — to reduce XHR requests on a test page from 11 to fewer. | |
| ## Your Environment | |
| - **Autoprobe source:** `~/autoprobe` (you can modify this) | |
| - **Test repo:** `~/vandoor` (vendor-web React app) | |
| - **Test page:** `channels` (makes 11 XHR requests, goal is fewer) | |
| - **Discard vandoor changes:** Always `git checkout .` in vandoor after each run — we're improving autoprobe, not vandoor |
| # Autoprobe Auto-Research Loop | |
| Automated feedback loop for improving autoprobe: | |
| 1. Push fix to autoprobe repo | |
| 2. GitHub webhook triggers your Mac | |
| 3. Mac rebuilds autoprobe, runs it on test repo | |
| 4. Results posted to Telegram | |
| 5. Analyze, push next fix, repeat | |
| ## Prerequisites |
| # autoprobe CLI Structure | |
| ## Command Tree | |
| ``` | |
| autoprobe | |
| ├── init # Create .autoprobe.yaml, set up project | |
| ├── run <name> # Analyze → fix → verify → repeat | |
| │ ├── --max-iterations # Stop after N cycles (1 = single-shot analysis) | |
| │ └── --dry-run # Show proposed changes, don't apply |
feat/daytona-provisioning onto latest main (resolved otel version conflicts)ai_support_bundle_analysis feature flag)POST /v3/supportbundle/:bundleId/agent/startsupport_bundle_analysis → ai_support_bundle_analysis (+ bundle join table)migrations/kustomize/schemas/mysql/When a vendor promotes a release, we generate structured Helm chart reference documentation and serve it through Enterprise Portal. Vendors declare which charts they want documented in toc.yaml. The worker extracts chart content from the release, parses values.yaml deterministically, enriches with Claude, and stores structured JSON. The EP frontend renders it using the same component pattern as Terraform module references.
- title: ReferenceTerraform modules are referenced as source URIs directly in toc.yaml. The URI is the single source of truth for where a module lives. During content sync, Vandoor resolves the URI, fetches the module using the GitHub App, and stores it with a commit SHA for change detection.
A service that provides scoped GitHub credentials to autonomous bots, with policy-based auto-approval and human-in-the-loop approval flows.
When running multiple autonomous bots (coding agents, CI helpers, etc.), each bot needs GitHub access to:
A service that provides scoped GitHub credentials to autonomous bots, with policy-based auto-approval and human-in-the-loop approval flows.
When running multiple autonomous bots (coding agents, CI helpers, etc.), each bot needs GitHub access to: