--- title: Remote Taskfiles | daily.dev description: Remote Taskfiles, previously available only as an opt-in experiment for nearly three years, are now generally available and enabled by default in Task... canonical: https://daily.dev/posts/remote-taskfiles-cemcdgoko twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Remote Taskfiles | daily.dev og:description: Remote Taskfiles, previously available only as an opt-in experiment for nearly three years, are now generally available and enabled by default in Task... og:url: https://daily.dev/posts/remote-taskfiles-cemcdgoko og:image: https://api.daily.dev/og/posts/CemcDGOKO.png og:image:alt: Remote Taskfiles og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Remote Taskfiles **[Awesome Go](https://daily.dev/sources/awego)** · 3 min read · 52 upvotes · 3 comments ## Summary Remote Taskfiles, previously available only as an opt-in experiment for nearly three years, are now generally available and enabled by default in Task (starting v3.53.0+). No config or flags are needed anymore to use them, and existing setups will keep working; a deprecation warning appears if old enabling flags/config are still present. The post shows how to use a remote URI as a --taskfile entrypoint or as an include source, referencing GitHub raw URLs, git URIs, and a hosted example Taskfile for testing. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Do I need to set a flag or config to enable remote Taskfiles in Task? No, as of Task v3.53.0 remote Taskfiles are enabled by default and no longer require a config setting or flag to activate. Existing setups that still set the old enabling flag or config will keep working but will show a warning that it is no longer necessary; that flag can be removed at any convenient time. _Track build tool changes like this remote Taskfile rollout as you plan CI/CD upgrades on daily.dev._ ### How do I use a remote Taskfile as the entrypoint with the Task command line tool? Pass the file's URL into the --taskfile or -t flag instead of a local path, supporting raw URLs (e.g. a raw.githubusercontent.com link), git repository URLs with a //path?ref=branch syntax, or SSH-style git URIs. A hosted example at taskfile.dev/Taskfile.yml is available for testing that a Task installation works correctly. _Developers wiring up Task-based pipelines can follow updates on remote Taskfile syntax via daily.dev._ ### Can I include tasks from a remote Taskfile inside my local Taskfile? Yes, the includes section supports a remote URI in place of a local path, using the same raw URL, git URL with ref query parameter, or SSH-style syntax used for the --taskfile flag. Tasks defined in the remote file become available under the specified namespace, runnable as namespace:taskname from the main Taskfile. _daily.dev helps developers keep pace with build tooling patterns like namespaced remote task includes._ ## Community discussion Top comments from developers on daily.dev. **@trevorsuna** · 2 upvotes > Making remote Taskfiles a default feature should help teams centralize repeatable CI and release workflows. The tradeoff is supply-chain trust, so pinning remote references to immutable commits and reviewing changes feels essential before using them in sensitive pipelines. **@jliter85** · 0 upvotes > Being able to keep common tasks in one place and reuse them across projects is really useful. I also like that they didn’t ignore the security side of running remote files and added checksums and trust warnings. This could clean up a lot of duplicated setup between projects. **@agustinbarrientos** · 0 upvotes > Remote Taskfiles should accept a pinned content hash so yesterday's automation can't silently become tomorrow's script. ## Similar posts on daily.dev - [Taskfile: The Modern Alternative to Makefile That Will Change Your Workflow](https://daily.dev/posts/taskfile-the-modern-alternative-to-makefile-that-will-change-your-workflow-2ln7doocv) · marmelab · 32 upvotes · 6 comments - [TaskyPi can turn your pyproject.toml into a Makefile too](https://daily.dev/posts/taskypi-can-turn-your-pyproject-toml-into-a-makefile-too-bcaxkogjq) · Vincent D. Warmerdam · 1 upvotes · 0 comments - [Task: a Modern, Friendly Make replacement](https://daily.dev/posts/task-a-modern-friendly-make-replacement-dr0jpiiu4) · Atomic Spin · 1 upvotes · 0 comments - [Run all tasks: the feature we refused to ship \(until now\)](https://daily.dev/posts/run-all-tasks-the-feature-we-refused-to-ship-until-now--telbxgpie) · Kiro · 1 upvotes · 0 comments - [I stopped opening Task Scheduler after discovering VS Code's hidden automation layer](https://daily.dev/posts/i-stopped-opening-task-scheduler-after-discovering-vs-code-s-hidden-automation-layer-s9rgh2ncf) · XDA Developers · 0 upvotes · 0 comments --- Tags: [#golang](https://daily.dev/tags/golang), [#cicd](https://daily.dev/tags/cicd) [View this post on daily.dev](https://daily.dev/posts/remote-taskfiles-cemcdgoko) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Remote Taskfiles","url":"https://daily.dev/posts/remote-taskfiles-cemcdgoko","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/remote-taskfiles-cemcdgoko"},"datePublished":"2026-08-20T20:15:43.679Z","dateModified":"2026-09-14T06:06:07.746Z","description":"Remote Taskfiles, previously available only as an opt-in experiment for nearly three years, are now generally available and enabled by default in Task...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b94b8d931bc794d2cb13f393317bfd98?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b94b8d931bc794d2cb13f393317bfd98?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Awesome Go","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Awesome Go","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/awego","url":"https://daily.dev/sources/awego"},"commentCount":3,"discussionUrl":"https://daily.dev/posts/remote-taskfiles-cemcdgoko","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":52},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":3}],"keywords":"golang,cicd","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Awesome Go","item":"https://daily.dev/sources/awego"},{"@type":"ListItem","position":3,"name":"Remote Taskfiles"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/remote-taskfiles-cemcdgoko","comment":[{"@type":"Comment","text":"Making remote Taskfiles a default feature should help teams centralize repeatable CI and release workflows. The tradeoff is supply-chain trust, so pinning remote references to immutable commits and reviewing changes feels essential before using them in sensitive pipelines.","datePublished":"2026-08-21T02:39:03.134Z","url":"https://daily.dev/posts/CemcDGOKO#c-IQCEmPOFC","author":{"@type":"Person","name":"Trevor Suna","url":"https://daily.dev/trevorsuna","image":"https://media.daily.dev/image/upload/s--dZ7gXxpp--/f_auto/v1784081551/avatars/avatar_EMoP47rpuw8DNjhp6R1b6?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2}},{"@type":"Comment","text":"Being able to keep common tasks in one place and reuse them across projects is really useful. I also like that they didn’t ignore the security side of running remote files and added checksums and trust warnings. This could clean up a lot of duplicated setup between projects.","datePublished":"2026-08-23T02:06:48.129Z","url":"https://daily.dev/posts/CemcDGOKO#c-UPWhuvGx9","author":{"@type":"Person","name":"John Liter","url":"https://daily.dev/jliter85","image":"https://media.daily.dev/image/upload/s--DQ2HUrO4--/f_auto/v1785100315/avatars/avatar_yHf9cPdgTQEtokv6d8qhM?_a=BAMAMicg0"}},{"@type":"Comment","text":"Remote Taskfiles should accept a pinned content hash so yesterday’s automation can’t silently become tomorrow’s script.","datePublished":"2026-08-26T03:37:12.586Z","url":"https://daily.dev/posts/CemcDGOKO#c-TI3Zmyabe","author":{"@type":"Person","name":"Agustin Barrientos","url":"https://daily.dev/agustinbarrientos","image":"https://media.daily.dev/image/upload/s--5ayxQnqn--/f_auto/v1788281802/avatars/avatar_wQYYVe5Tbj0NJ7C7qPoa8?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/remote-taskfiles-cemcdgoko#faq","mainEntity":[{"@type":"Question","name":"Do I need to set a flag or config to enable remote Taskfiles in Task?","acceptedAnswer":{"@type":"Answer","text":"No, as of Task v3.53.0 remote Taskfiles are enabled by default and no longer require a config setting or flag to activate. Existing setups that still set the old enabling flag or config will keep working but will show a warning that it is no longer necessary; that flag can be removed at any convenient time. Track build tool changes like this remote Taskfile rollout as you plan CI/CD upgrades on daily.dev."}},{"@type":"Question","name":"How do I use a remote Taskfile as the entrypoint with the Task command line tool?","acceptedAnswer":{"@type":"Answer","text":"Pass the file's URL into the --taskfile or -t flag instead of a local path, supporting raw URLs (e.g. a raw.githubusercontent.com link), git repository URLs with a //path?ref=branch syntax, or SSH-style git URIs. A hosted example at taskfile.dev/Taskfile.yml is available for testing that a Task installation works correctly. Developers wiring up Task-based pipelines can follow updates on remote Taskfile syntax via daily.dev."}},{"@type":"Question","name":"Can I include tasks from a remote Taskfile inside my local Taskfile?","acceptedAnswer":{"@type":"Answer","text":"Yes, the includes section supports a remote URI in place of a local path, using the same raw URL, git URL with ref query parameter, or SSH-style syntax used for the --taskfile flag. Tasks defined in the remote file become available under the specified namespace, runnable as namespace:taskname from the main Taskfile. daily.dev helps developers keep pace with build tooling patterns like namespaced remote task includes."}}]} ```