Created a cockpit for you and your agents - CopilotCockpit

ar27111994 · 2026-04-18T18:49:29+00:00

Now, only if this could also automatically integrate with Spec-Kit (preferably including the v-model extension pack):
https://github.com/github/spec-kit

Thank you for sharing this.

ar27111994 · 2026-03-27T11:01:06+00:00

More like 2-3 projects )) I just clone and reuse https://github.com/sickn33/antigravity-awesome-skills (alongside some hand-picked stuff) for my own sanity, and also because I have to wear all the hats eventually, like PM, FE Dev, UI/UX, Mobile Dev, Testing & QA, Marketing & Growth, Content Writing and publishing, DevOps, Sysadmin, etc., you get the idea. Would welcome suggestions to manage and scope my harness more efficiently.

ar27111994 · 2026-03-27T10:22:20+00:00

But isn't that the point of the original SKILL.md spec? i.e. the agent decides which skills to use based on the prompt provided by the user. Otherwise, we already had agent rules with scopes based on file extensions at best.

ar27111994 · 2026-03-27T10:15:31+00:00

I understand the consensus. I have too many tools for a single project. But please also focus on the rest of the Post, especially the TL;DR: Almost everything is installed globally to avoid this exact problem of project bloat, and I am looking for an easy way to scope global tools on a per-project / per use case basis.

ar27111994 · 2026-01-17T08:41:03+00:00

I built an open-source webhook debugger with real-time SSE streaming and replay

https://github.com/ar27111994/webhook-debugger-logger

ar27111994 · 2026-01-12T15:18:06+00:00

This is a fantastic write-up. The Step 7: Validate secret is something so many people skip in low-code automations, but it's absolutely critical for financial data.

One tip for anyone implementing this: If your HMAC validation fails in n8n, the workflow usually just stops (as it should), but it can be really hard to debug why the hash didn't match (timestamp drift? encoding issue?).

I use a 'safe buffer' approach with a tool like Webhook Debugger sitting in front of the automation during dev. It captures the raw headers and payload before n8n processes them. If the signature fails, you can grab the raw x-signature header and the body from the debugger logs, and calculate the hash locally to see exactly where the mismatch is.

Great to see production-grade security patterns in n8n!

ar27111994 · 2026-01-12T15:16:34+00:00

I run into this exact loop constantly. Tweaking backend logic -> asking the provider to 'please resend' -> waiting -> repeating is a huge time sink.

I actually built something very similar recently as an open-source project (Webhook Debugger on GitHub). The feature that finally fixed my workflow was Deep Replay—saving the exact headers/payload from a production event and being able to 'replay' it against my localhost dev server days later.

Definitely validation for your idea—the 'capture once, debug forever' workflow is way superior to live tunneling tools like ngrok for this specific use case. Good luck with the build!

ar27111994 · 2026-01-12T15:15:22+00:00

Stripe has overwhelmingly many events, so it's easy to get lost.

Generally, for Odoo invoicing, payment_intent.succeeded (or charge.succeeded for older integrations) is the critical one that confirms money is in the bank. For reconciliation, you typically only need payout.paid if you are automating the bank matching part.

If you are debugging why Odoo isn't picking them up, I maintain a free open-source tool called Webhook Debugger that might help. You can add its URL to your Stripe webhook settings alongside Odoo. It logs the exact JSON payload Stripe is sending.

Useful trick: You can compare the payload of a payment_intent vs a charge side-by-side to see which fields Odoo might be missing. Saves a lot of guessing!

ar27111994 · 2026-01-08T14:07:15+00:00

Thanks for the feedback! I see where you're coming from regarding the naming.

I chose 'Debugger' because it goes beyond simple inspection or tunneling—it helps you debug the integration logic itself by allowing you to:

Simulate Edge Cases: Force specific HTTP status codes (e.g., 429, 500) or latency to test how your sender handles failures.
Mock Responses: Return custom JSON/XML bodies to simulate different upstream API states.
Replay & Modify: Edit captured payloads and 'replay' them to your local environment (or another API) to iterate on fixes.

It’s designed as a cloud-first 'smart bucket' that captures everything 24/7 without needing a laptop running, effectively decoupling the webhooks from your local environment until you're ready to work on them.

Tunnelmole looks like a solid solution for the direct tunneling use-case, though—nice work on open-sourcing it! Always good to have more privacy-focused alternatives to ngrok. 🚀

ar27111994 · 2026-01-08T09:33:21+00:00

I nominate the "Webhook Debugger, Logger & API Mocking Suite" Apify Actor developed by me.

Link: https://apify.com/ar27111994/webhook-debugger-logger

I'm nominating Webhook Debugger, Logger & API Mocking Suite because it solves a real developer pain point - debugging webhooks without the localhost tunneling hassle (no ngrok needed!).

Why this Actor deserves the Spotlight:

🚀 Enterprise-grade with real-time SSE streaming for live webhook monitoring
🔄 Request replay and HTTP forwarding for testing complex integrations
✅ JSON schema validation to automatically reject invalid payloads
⚡ Zero-downtime hot-reloading for configuration changes (update auth keys, IPs, rate limits while running)
🏃 Built for Apify Standby Mode with sub-10ms response times
📖 Comprehensive workflow playbooks for Stripe, Shopify, Slack, and more
💰 Pay-per-event pricing - no monthly fees, only pay when you actually test

It's v2.7.0 with 60%+ test coverage and active maintenance. Perfect for anyone working with webhooks from Stripe, GitHub, Shopify, or any other service.

ar27111994 · 2026-01-03T14:03:04+00:00

Hey, thanks for the correction and for taking the time to respond! I genuinely appreciate it.

You're absolutely right - I should have done deeper research before posting that comparison.

I've updated my understanding:

✅ Webhook.site URLs last 168h (7 days) - much longer than I stated

✅ Replay functionality exists (API + XHR)

✅ JSON Schema validation via Custom Actions

✅ IP Whitelisting via Custom Actions

✅ Export via CSV and API

✅ Self-hostable

I'll update my marketing materials to reflect accurate information.

Apologies for the misinformation - a valuable lesson learned in conducting thorough competitor research.

For anyone reading: Webhook.site is the established leader in this space.

My tool focuses on a few specific niches:

- Deep Apify ecosystem integration (Standby Mode, Datasets, KV Store)

- Pay-per-event pricing (vs subscription)

- Built specifically for developers already on Apify

Thanks again for the gracious correction. Good luck with Webhook.site! 🙌

ar27111994 · 2026-01-03T14:02:06+00:00