Entrypoint tasks

As a project grows, the number of deployed tasks in a project/domain grows with it. Every @env.task you deploy shows up as a flat entry in the Tasks list alongside every other task — including internal helpers, leaf tasks, and intermediate steps that users aren’t meant to invoke directly. Finding the handful of tasks that are actually meant to be run becomes a navigation problem.

Entrypoint tasks solve this by letting you mark which tasks in an environment are the ones intended to be invoked by humans or other services. It’s a purely declarative hint — it doesn’t change how the task executes — but it makes the task easy to surface in the CLI, UI, and remote API.

When to use entrypoints

Mark a task as an entrypoint when:

• It is meant to be run directly, by a user, a teammate, or a service, rather than only being called from another task.
• You want it to be discoverable in the UI’s entrypoint view or via filtered CLI queries.
• You are sharing tasks with team members and want the “start here” tasks to stand out from internal helpers.

Conversely, don’t mark a task as an entrypoint if it only exists as a subtask called by another task, or if it’s a utility helper not intended to be invoked on its own.

Mark a task as an entrypoint

Pass entrypoint=True to the @env.task decorator:

import flyte

env = flyte.TaskEnvironment(
    name="hello_world",
    resources=flyte.Resources(cpu=1, memory="1Gi"),
)

@env.task
async def square(i: int) -> int:
    return i * i

@env.task(entrypoint=True)
async def say_hello_nested(data: str = "default string", n: int = 3) -> str:
    vals = [await square(i=i) for i in range(n)]
    return f"Hello {data} {vals}"

Here say_hello_nested is the intended starting point; square is an internal helper that say_hello_nested calls. Both get deployed — but only say_hello_nested is marked as an entrypoint.

The flag is also available on task.override(), so you can promote or demote a task as an entrypoint at invocation time without editing the source:

promoted = square.override(entrypoint=True)

The default is entrypoint=False — if you don’t mark anything, nothing is treated as an entrypoint.

Discover entrypoint tasks

Once deployed, entrypoint tasks can be surfaced in three ways.

CLI

Filter flyte get task to only entrypoint tasks:

flyte get task --entrypoint

This lists every task in the configured project/domain that was deployed with entrypoint=True.

Programmatic

Use flyte.remote.Task.listall() with the entrypoint filter:

import flyte

flyte.init_from_config()

for task in flyte.remote.Task.listall(entrypoint=True):
    print(task.name, task.version)

This is useful for building your own catalogs, dashboards, or tooling on top of the Flyte API.

UI

The Tasks list in the UI has an entrypoints toggle that filters the view to only tasks marked as entrypoints. Use this when you’re browsing a project and want to see only the tasks meant to be run.