Feature Request: Restore built-in agent as an opt-in CLI command / launcher option

Background

In PR #18393, the built-in CLI agent was removed. While removing it from the default ollama entry point addresses community concerns regarding default cloud models and login prompts, completely deleting the feature breaks daily workflows for developers in locked-down enterprise environments.

In many corporate settings, strict IT security policies prohibit installing external third-party agent harnesses such as Claude Code, OpenCode, or OpenClaw. Ollama is often the only approved local AI binary on developer machines.

The built-in agent allowed users to run local, offline tool-use loops safely without introducing non-compliant external dependencies.

Proposed Solution

Restore the built-in agent code strictly as an opt-in feature. This preserves functionality for enterprise users without hijacking the standard CLI experience for local-inference purists.

1. Dedicated CLI Command

Allow users to explicitly launch the local agent harness via a dedicated subcommand:

ollama launch built-in

Or, alternatively:

ollama agent

2. Interactive Menu Integration

Include an entry in the interactive launcher menu alongside external integrations:

Launch Built-in agent   

Why This Works

• Zero Disruption: The base ollama command remains a pure, lightweight local model interface with no surprise cloud defaults.
• Enterprise Compliance: Restores essential agent workflows for developers restricted to company-approved binaries.
• Offline-First: Can be configured to run strictly with local models without requiring web search or network authentication and still be very useful with the use of tools.