Add interactive task support for GitHub-hosted task definitions (Ollama + Gradio) by aliasaria · Pull Request #1503 · transformerlab/transformerlab-app

aliasaria · 2026-03-10T18:56:51Z

Summary

This PR adds full support for interactive gallery entries that source their task definitions from GitHub repositories, replacing the previous local filesystem approach. The first entry to use this is the Ollama + Gradio interactive task, which launches an Ollama model server with a Gradio chat UI.

What was created

Ollama + Gradio interactive gallery entry (interactive-gallery.json): A new interactive task that starts Ollama, pulls a model, and launches a Gradio chat interface. It sources its task.yaml (setup/run commands, parameters, etc.) from transformerlab-examples/inference-ollama-gradio-chat.
InteractIframeModal: A near-fullscreen modal with a refresh button for rendering interactive task UIs in an iframe.
Interact button on InteractiveJobCard: Lets users open the interactive modal directly from a running job card.
Custom URL pattern matching (url_patterns field in gallery entries): Allows gallery entries to define regex patterns for extracting URLs from provider logs (e.g., Gradio's Running on ... output).

Key changes to support GitHub-sourced interactive tasks

Previously, interactive gallery entries could only use inline setup/command fields or a local_task_dir pointing to a directory on the local filesystem. This PR extends the system so interactive entries can use github_repo_url + github_repo_dir — the same pattern used by the regular task gallery.

Frontend (`Interactive.tsx`)

The condition that decides whether to use the ImportFromGallery API now triggers on template.github_repo_url in addition to template.local_task_dir. This routes GitHub-sourced interactive entries through the proper import flow that fetches task.yaml and stores the task with all its metadata.

Backend (`task.py`)

The interactive import path in import_task_from_gallery now handles three source types:
1. github_repo_url + github_repo_dir → fetches task.yaml from GitHub via fetch_task_yaml_from_github()
2. local_task_dir → reads task.yaml from local filesystem (existing behavior)
3. Inline fields → uses setup/command directly from the gallery entry (existing behavior)
GitHub repo info (github_repo_url, github_directory, github_branch) is stored on the task so the runner clones the repo files at launch time.
The fetched task.yaml content is saved to the task directory, matching the behavior of regular task imports.

Other changes

Tunnel parser (tunnel_parser.py): Extended to support custom url_patterns for extracting dynamic URLs from provider logs.
Interactive gallery utils: Simplified to work with the new gallery structure.
Task schema: Added is_interactive field to the import request.
Gallery ID referencing: Tasks are now consistently referenced by id rather than interactive_type, supporting multiple entries of the same type.
Interact button: Disabled until tunnel_info is ready, preventing premature clicks.

Gallery entry diff

- "local_task_dir": "/Users/ali/.../tmp/ollama-gradio-chat",
+ "github_repo_url": "https://github.com/transformerlab/transformerlab-examples",
+ "github_repo_dir": "inference-ollama-gradio-chat",

Testing

Verified that the Ollama + Gradio interactive task can be created and launched from the Interactive tab.
Ollama server starts, pulls the specified model, and the Gradio chat UI launches successfully.
The Gradio URL is extracted from logs via url_patterns and displayed in the interactive modal.

When an interactive gallery entry specifies a local_task_dir path, the files are copied into the task directory (inside a subdirectory matching the source directory name) on import, mirroring the github_repo_dir clone behavior. The task is marked with file_mounts=True so files are copied to the job at launch.

When a local_task_dir has a task.yaml, its setup, run, parameters, env_vars, and resource fields are now parsed and used to populate the interactive task. This fixes the 'Task is missing a command to run' error since command was previously left empty for local_task_dir entries.

When a gallery template has local_task_dir, the frontend now calls the ImportFromGallery API instead of NewTemplate. This ensures the task gets its command/setup populated from the directory's task.yaml and the files are copied into the task directory. Fixes 'Task is missing a command to run' error for local_task_dir gallery entries.

This reverts commit 16d04bd.

Tasks imported from local_task_dir gallery entries have their command in the copied task.yaml rather than in the gallery JSON. Skip the frontend command-required check when file_mounts is set.

For local_task_dir gallery entries, call ImportFromGallery instead of NewTemplate so the task gets created with command/setup from task.yaml and files copied — matching the regular 'Upload from Local Directory' flow. Revert launch-time and command-check workarounds.

paragon-review · 2026-03-10T19:10:42Z

Paragon Summary

This pull request review identified 6 issues across 3 categories in 16 files. The review analyzed code changes, potential bugs, security vulnerabilities, performance issues, and code quality concerns using automated analysis tools.

This PR adds support for interactive gallery entries that source their task definitions from GitHub repositories (replacing the previous local filesystem approach), with the first implementation being an Ollama + Gradio chat interface. It extends both frontend and backend to fetch task.yaml from GitHub, store task metadata, and render interactive task UIs in a fullscreen iframe modal with URL extraction from provider logs.

Key changes:

GitHub-sourced interactive task support: Backend and frontend now handle github_repo_url + github_repo_dir for interactive gallery entries, previously limited to local filesystem
Ollama + Gradio interactive gallery entry: New task sourcing task.yaml from GitHub, launching Ollama model server with Gradio chat UI
InteractIframeModal component: Near-fullscreen modal with refresh button for rendering interactive task UIs in an iframe
Custom URL pattern matching: New url_patterns field for extracting dynamic URLs from provider logs (e.g., Gradio's Running on ... output)
Interact button on InteractiveJobCard: Button to open interactive modal directly from running job cards (disabled until tunnel_info ready)

Confidence score: 3/5

This PR has moderate risk due to 3 high-priority issues that should be addressed
Score reflects significant bugs, performance issues, or architectural concerns
Review high-priority findings carefully before merging

16 files reviewed, 6 comments

Severity breakdown: High: 3, Medium: 2, Low: 1

Tip: @paragon-run <instructions> to chat with our agent or push fixes!

Dashboard

paragon-review · 2026-03-10T19:10:42Z

src/renderer/components/Experiment/Tasks/Tasks.tsx

-        provider_name: providerMeta.name,
-        env_vars: Object.keys(envVars).length > 0 ? envVars : undefined,
-      };
+      if (template.local_task_dir) {


Bug: Tasks

Tasks.tsx checks only local_task_dir, missing github_repo_url. GitHub-sourced interactive tasks silently get empty commands. Add || template.github_repo_url.

View Details

Location: src/renderer/components/Experiment/Tasks/Tasks.tsx (lines 743)

Analysis

Tasks.tsx checks only local_task_dir, missing github_repo_url

What fails GitHub-sourced interactive tasks (like ollama_gradio) created from the Tasks tab get routed to the wrong code path, producing tasks with empty setup/command.

Result Task is created via the NewTemplate endpoint with empty command/setup fields instead of going through ImportFromGallery which fetches task.yaml from GitHub.

Expected Tasks.tsx should check `template.local_task_dir

Impact Every GitHub-sourced interactive task created from the Tasks view will fail at runtime with no command to execute.

How to reproduce

1. Open Tasks tab 2. Create a new interactive task using the ollama_gradio gallery entry (which has github_repo_url but no local_task_dir) 3. Observe the created task has no command/setup

Patch Details

- if (template.local_task_dir) { + if (template.local_task_dir || template.github_repo_url) {

AI Fix Prompt

Fix this issue: Tasks.tsx checks only `local_task_dir`, missing `github_repo_url`. GitHub-sourced interactive tasks silently get empty commands. Add `|| template.github_repo_url`. Location: src/renderer/components/Experiment/Tasks/Tasks.tsx (lines 743) Problem: GitHub-sourced interactive tasks (like ollama_gradio) created from the Tasks tab get routed to the wrong code path, producing tasks with empty setup/command. Current behavior: Task is created via the NewTemplate endpoint with empty command/setup fields instead of going through ImportFromGallery which fetches task.yaml from GitHub. Expected: Tasks.tsx should check `template.local_task_dir || template.github_repo_url` (matching Interactive.tsx) and route GitHub-sourced entries through ImportFromGallery. Steps to reproduce: 1. Open Tasks tab 2. Create a new interactive task using the ollama_gradio gallery entry (which has github_repo_url but no local_task_dir) 3. Observe the created task has no command/setup Provide a code fix.

_{Tip: Reply with @paragon-run to automatically fix this issue}

I think this is wrong

paragon-review · 2026-03-10T19:10:42Z

api/transformerlab/compute_providers/local.py


        venv_bin = venv_path / "bin"
        env = os.environ.copy()
+        print(f"[DEBUG LocalProvider] config.env_vars = {config.env_vars}")


Bug: Debug print() statements dump env_vars containing secrets to stdout

Debug print() statements dump env_vars containing secrets to stdout. Credentials leak to logs and aggregators. Remove all [DEBUG print statements.

View Details

Location: api/transformerlab/compute_providers/local.py (lines 276)

Analysis

Debug print() statements dump env_vars containing secrets to stdout

What fails Debug print statements output full env_vars dicts containing NGROK_AUTH_TOKEN, {{secret.*}} references, and user-supplied values to stdout/logs in production.

Result Secrets and API tokens are written in plaintext to stdout, which is often forwarded to log aggregators, container runtimes, or returned via API log endpoints.

Expected No debug print statements should be present in production code. Secrets should never appear in logs.

Impact Credentials and API tokens exposed in plaintext logs. Violates the project's secret-management pattern where secrets use {{secret.}} placeholders.

How to reproduce

1. Launch any interactive task with env_vars (e.g. ollama_gradio with MODEL_NAME) 2. Check server stdout/logs 3. Observe full env_vars dicts printed in plaintext

AI Fix Prompt

Fix this issue: Debug print() statements dump env_vars containing secrets to stdout. Credentials leak to logs and aggregators. Remove all `[DEBUG` print statements. Location: api/transformerlab/compute_providers/local.py (lines 276) Problem: Debug print statements output full env_vars dicts containing NGROK_AUTH_TOKEN, {{secret.*}} references, and user-supplied values to stdout/logs in production. Current behavior: Secrets and API tokens are written in plaintext to stdout, which is often forwarded to log aggregators, container runtimes, or returned via API log endpoints. Expected: No debug print statements should be present in production code. Secrets should never appear in logs. Steps to reproduce: 1. Launch any interactive task with env_vars (e.g. ollama_gradio with MODEL_NAME) 2. Check server stdout/logs 3. Observe full env_vars dicts printed in plaintext Provide a code fix.

_{Tip: Reply with @paragon-run to automatically fix this issue}

src/renderer/components/Experiment/Tasks/Tasks.tsx

src/renderer/components/Experiment/Interactive/InteractIframeModal.tsx

src/renderer/components/Experiment/Interactive/InteractiveJobCard.tsx

paragon-review · 2026-03-10T19:10:42Z

tmp/ollama-gradio-chat/task.yaml

+  cpus: 2
+  memory: 4
+setup: |
+  echo "=== SETUP DEBUG ==="


Bug: task

task.yaml ships debug echo blocks exposing PATH and VIRTUAL_ENV. These pollute user-facing logs. Strip debug echo statements before merge.

View Details

Location: tmp/ollama-gradio-chat/task.yaml (lines 8)

Analysis

task.yaml ships debug echo blocks exposing PATH and VIRTUAL_ENV. These pollute user-facing logs

What fails The task.yaml file contains extensive debug echo statements in both setup and run sections that print internal Python paths, sys.path, VIRTUAL_ENV, and PATH to job logs.

Result User-facing job logs are cluttered with internal debug information including Python paths and environment variables.

Expected Task definitions shipped to users should contain only functional commands. Debug echo blocks should be removed before merge.

Impact Noisy logs degrade UX. PATH and VIRTUAL_ENV disclosure is a minor information leak in production logs.

How to reproduce

1. Create and launch the ollama-gradio-chat interactive task 2. View the job logs 3. Observe debug output like 'which python:', 'sys.path:', 'VIRTUAL_ENV:', 'PATH:' polluting the log stream

AI Fix Prompt

Fix this issue: task.yaml ships debug echo blocks exposing PATH and VIRTUAL_ENV. These pollute user-facing logs. Strip debug echo statements before merge. Location: tmp/ollama-gradio-chat/task.yaml (lines 8) Problem: The task.yaml file contains extensive debug echo statements in both setup and run sections that print internal Python paths, sys.path, VIRTUAL_ENV, and PATH to job logs. Current behavior: User-facing job logs are cluttered with internal debug information including Python paths and environment variables. Expected: Task definitions shipped to users should contain only functional commands. Debug echo blocks should be removed before merge. Steps to reproduce: 1. Create and launch the ollama-gradio-chat interactive task 2. View the job logs 3. Observe debug output like 'which python:', 'sys.path:', 'VIRTUAL_ENV:', 'PATH:' polluting the log stream Provide a code fix.

_{Tip: Reply with @paragon-run to automatically fix this issue}

… stdout Debug print() statements dump env_vars containing secrets to stdout. Credentials leak to logs and aggregators. Remove all [DEBUG print statements.

The local_task_dir branch in Tasks.tsx was missing env_vars in the POST body, causing user-provided environment parameters (e.g. MODEL_NAME) to be silently dropped. Matches the Interactive.tsx implementation.

Replace single iframeRef with a ref Map keyed by tab index and track the active tab. handleRefresh() now resolves the correct iframe for the currently selected tab.

Gate the SWR polling URL on isInteractive instead of showActions so WAITING/LAUNCHING jobs no longer trigger 3s polling for tunnel info that doesn't exist yet.

aliasaria added 19 commits March 10, 2026 11:24

add new task

4402137

always refer to tasks by id, not type

cddd8e5

find gallery by id

ec78391

Revert "Use gallery import API for local_task_dir interactive entries"

cbee116

This reverts commit 16d04bd.

Skip command check for tasks with file_mounts (local_task_dir)

3681ba6

Tasks imported from local_task_dir gallery entries have their command in the copied task.yaml rather than in the gallery JSON. Skip the frontend command-required check when file_mounts is set.

run local dir tasks

512407d

allow for custom URL patterns in interactive tasks

13cc5d2

Add Interact button with tabbed iframe modal to InteractiveJobCard

8b02172

Extract InteractModal into its own file

752c70d

Rename InteractModal to InteractIframeModal

740b474

Disable Interact button until tunnel_info is ready

f5cc04b

Make InteractIframeModal near-fullscreen with refresh button

1728ab3

switch gradio task to use github

9057cbe

delete temp files

1b7c1af

remove excessive logging

8819bb8

paragon-review bot reviewed Mar 10, 2026

View reviewed changes

aliasaria added 8 commits March 11, 2026 09:53

fix Bug: Debug print() statements dump env_vars containing secrets to…

4c8fa85

… stdout Debug print() statements dump env_vars containing secrets to stdout. Credentials leak to logs and aggregators. Remove all [DEBUG print statements.

Fix: include env_vars in Tasks ImportFromGallery payload

72bd425

The local_task_dir branch in Tasks.tsx was missing env_vars in the POST body, causing user-provided environment parameters (e.g. MODEL_NAME) to be silently dropped. Matches the Interactive.tsx implementation.

Fix: refresh button targets active tab's iframe, not last rendered

c6429e3

Replace single iframeRef with a ref Map keyed by tab index and track the active tab. handleRefresh() now resolves the correct iframe for the currently selected tab.

Fix: only poll tunnel info for INTERACTIVE/RUNNING jobs

73d1603

Gate the SWR polling URL on isInteractive instead of showActions so WAITING/LAUNCHING jobs no longer trigger 3s polling for tunnel info that doesn't exist yet.

Resolve merge conflicts with main, maintaining command -> run rename

024848b

Add agent-browser skill configuration

6cf3ed3

Merge branch 'main' into add/interact-modal-component

47d3ef7

Fix prettier and ruff formatting errors

92aab6e

aliasaria merged commit d61bb73 into main Mar 12, 2026
5 of 7 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add interactive task support for GitHub-hosted task definitions (Ollama + Gradio)#1503

Add interactive task support for GitHub-hosted task definitions (Ollama + Gradio)#1503
aliasaria merged 27 commits intomainfrom
add/interact-modal-component

aliasaria commented Mar 10, 2026

Uh oh!

paragon-review bot commented Mar 10, 2026

Uh oh!

paragon-review bot Mar 10, 2026

Uh oh!

aliasaria Mar 11, 2026

Uh oh!

paragon-review bot Mar 10, 2026

Uh oh!

aliasaria Mar 11, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

paragon-review bot Mar 10, 2026

Uh oh!

aliasaria Mar 11, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant


What fails	GitHub-sourced interactive tasks (like ollama_gradio) created from the Tasks tab get routed to the wrong code path, producing tasks with empty setup/command.
Result	Task is created via the NewTemplate endpoint with empty command/setup fields instead of going through ImportFromGallery which fetches task.yaml from GitHub.
Expected	Tasks.tsx should check `template.local_task_dir
Impact	Every GitHub-sourced interactive task created from the Tasks view will fail at runtime with no command to execute.


What fails	Debug print statements output full env_vars dicts containing NGROK_AUTH_TOKEN, {{secret.*}} references, and user-supplied values to stdout/logs in production.
Result	Secrets and API tokens are written in plaintext to stdout, which is often forwarded to log aggregators, container runtimes, or returned via API log endpoints.
Expected	No debug print statements should be present in production code. Secrets should never appear in logs.
Impact	Credentials and API tokens exposed in plaintext logs. Violates the project's secret-management pattern where secrets use {{secret.}} placeholders.


What fails	The task.yaml file contains extensive debug echo statements in both setup and run sections that print internal Python paths, sys.path, VIRTUAL_ENV, and PATH to job logs.
Result	User-facing job logs are cluttered with internal debug information including Python paths and environment variables.
Expected	Task definitions shipped to users should contain only functional commands. Debug echo blocks should be removed before merge.
Impact	Noisy logs degrade UX. PATH and VIRTUAL_ENV disclosure is a minor information leak in production logs.

Uh oh!

Conversation

aliasaria commented Mar 10, 2026

Summary

What was created

Key changes to support GitHub-sourced interactive tasks

Frontend (Interactive.tsx)

Backend (task.py)

Other changes

Gallery entry diff

Testing

Uh oh!

paragon-review bot commented Mar 10, 2026

Paragon Summary

Confidence score: 3/5

Uh oh!

paragon-review bot Mar 10, 2026

Choose a reason for hiding this comment

Bug: Tasks

Analysis

Uh oh!

aliasaria Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

paragon-review bot Mar 10, 2026

Choose a reason for hiding this comment

Bug: Debug print() statements dump env_vars containing secrets to stdout

Analysis

Uh oh!

aliasaria Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

paragon-review bot Mar 10, 2026

Choose a reason for hiding this comment

Bug: task

Analysis

Uh oh!

aliasaria Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Frontend (`Interactive.tsx`)

Backend (`task.py`)