// clickfunnels --engineering
Weekly Dev with AI roundups, public API changes, and posts on how the ClickFunnels engineering team builds with agents.
// code_support
Building something on ClickFunnels? Share your use case with the Funnel Coders Discord community and get support from ClickFunnels engineers.
Share your use case// posts
16 so far, newest first.Screenshots in PRs straight from gh, a screen-aware desktop assistant, and eleven API updates from survey webhooks to video imports for courses.
read →Screen recordings an agent can read, a credential-free agent host, and API updates from subscription cancels to page markup that survives the editor.
read →A small lab's post-train on an open model, feedback tools inside MCP servers, and seven API updates from contact activity to exact stats.
read →How Clicky splits the work between models and code: each step sees only what it needs, and a deterministic process decides what runs next.
read →Ten days of always-on agents and new models, plus funnel duplication and archiving, short links, broadcast webhooks and stats everywhere.
read →A merge to master now ships itself: Clicky cuts the release, runs four checks, and only pulls people in when one fails.
read →Two weeks of agent harnesses, WebMCP checkouts and bold predictions, plus external pages opening to every workspace on the API.
read →Every finished Clicky task is now graded, and any task that struggled spawns an investigation that files a root-cause issue with a fix plan.
read →The internal system ClickFunnels engineers use to get code written, tested, reviewed and merged, from Slack, GitHub, the terminal or MCP.
read →Terminal and IDE tooling built for running many agents at once, a contract format for agent-driven code, and the week's model-cost chatter.
read →Remote coding tools, model reactions and five public API changes: inline filter results, broadcast stats, external purchases, subscription dates, price errors.
read →Multiplayer harnesses, a new agent client from the Zed team, routing work across Claude accounts, and hardware that costs less than a month of tokens.
read →Agent-readable pages from both sides: what the team tried on its own sites, and per-page AI crawler controls plus eight more API updates.
read →A field report from an automated go-to-market tool, prompt libraries and agent ops, plus discounts, refunds and email sending arriving in the API.
read →Two mountable Rails engines, a public directory turned into an agent briefing, and four API changes around courses, subscriptions and access grants.
read →A new frontier model, rulesets that push agents toward less code, and the Workflows, Community and contact bulk-action APIs open to everyone.
read →$ build_with_us --submit
Webhooks, API integrations, funnel automation: share what you are building with the Funnel Coders Discord community and get support from ClickFunnels engineers.
Share your use case// clickfunnels --engineering