help

Training example — PHP environment, server and repository responses are simulated
help [cmd] [-i|-l] · help -a · help me · help license

help	show installed commands in a compact grid
help -a	show all repository modules
help <cmd>	show the local reference and active aliases
help <cmd> -i	show the server command reference
help <cmd> -l	show the public documentation link

help hotkeys	show keyboard shortcuts
help aliases	show active command aliases

$	reuse the path of the file declared last (for example, @echo $)
@<cmd> [args]	silently install a missing package, then run the command
<cmd> | <cmd> | ...	run commands sequentially from left to right
<cmd> [args] > <file>	show textual output and append it to a file
<cmd> [args] > <file> -r	show textual output and replace the file

<file>	open a file (when a handler for its extension is registered)
<file.lil> [-s] [-r]	run a lil script from a file
<file.lil> -s	show each script command while it runs
<file.lil> -r	remove the script only after successful execution

help me	support lil-terminal
help license	show personal and commercial license terms

cd
dir [ls]
doctor
find
help
log
php
pwd

Training example — PHP environment, server and repository responses are simulated
doctor  help  log  mysql  zip

Training example — PHP environment, server and repository responses are simulated
doctor [group] [-q|-j]

doctor	check everything
doctor platform	show PHP, SAPI, limits, session and OPcache checks
doctor extensions	show PHP extension checks
doctor files	check project paths, permissions and storage
doctor repo	check the lil repository
doctor security	check HTTPS, authorization and cookies

-q	show warnings and failures only
-j	return machine-readable JSON

Training example — PHP environment, server and repository responses are simulated
Run structured grouped checks for the lil-terminal runtime, storage, repository and security.

doctor [group] [-q|-j]

doctor	check everything
doctor platform	show PHP, SAPI, limits, session and OPcache checks
doctor extensions	show PHP extension checks
doctor files	check project paths, permissions and storage
doctor repo	check the lil repository
doctor security	check HTTPS, authorization and cookies

-q	show warnings and failures only
-j	return machine-readable JSON
@more


With -q, individual OK checks are hidden; summary totals still count every check.

Training example — PHP environment, server and repository responses are simulated
https://lil.dog/docs/diagnostics/doctor

Training example — PHP environment, server and repository responses are simulated
log [<file>|<dir>] [-h] [-n <lines>] [-g <text>] [-i] [-l] [-r]

log	show the newest detected log (last 10 lines)
log <file>	read a specific log file
log <dir>	find a log inside a directory
log -l	list detected logs
log <dir> -l	list logs inside a directory

-h	read from the beginning instead of the end
-n <lines>	show 1–50000 physical lines
-g <text>	filter lines containing literal text
-i	ignore case when used with -g
-r	show the original lines without formatted entries

Training example — PHP environment, server and repository responses are simulated
log manual

Overview

Read-only log viewer for PHP and common server/application logs. With no argument, selects the newest log found around the working directory and the terminal. An explicit directory searches that location rather than treating it as a file.

Usage

log [<file>|<dir>] [-h] [-n <lines>] [-g <text>] [-i] [-l] [-r]

Reference

log	show the newest log (last 10 lines)
log <file>	read a specific log file
log <dir>	discover logs in this directory
log -l	list detected files
log <dir> -l	list logs inside one directory
-h	read from the start instead of the end
-n <lines>	set the number of physical lines from 1 to 50000
-g <text>	retain lines containing literal text
-i	ignore case when used with -g
-r	show original ungrouped lines

Discovery

For an explicit directory, search first for common names (error_log, error.log, PHP error logs, debug.log, app.log, and access logs) at its root, then in logs, log, storage/logs, var/log, app/logs and tmp. Recognized names take priority; other *.log and *_log files follow. Only regular files are selected. Without a directory, the newest detected candidate is used. Discovery is not a recursive scan of the entire hosting account.

Reading and display

Read by streaming, with bounded output. The default output groups timestamped events into entries, puts the time on its own line, highlights only the severity label in Base UI and keeps stack traces together. Each event has a blank separation. Without the Base interface the formatted output remains readable plain text. -r displays original lines. -g matches individual physical lines, so context lines not matching the filter are intentionally not returned. -i requires -g.

Security and limits

The command never changes source files. Binary files are rejected; paths use the existing runtime path resolver. Output is capped to approximately 1.5 MiB, tail reads to 16 MiB and filtered scan to 64 MiB. The command does not change PHP logging configuration or expose logs unauthenticated.

Training example — PHP environment, server and repository responses are simulated
https://lil.dog/docs/diagnostics/log

Training example — PHP environment, server and repository responses are simulated
help manual

Overview

help is the terminal navigation point. It lists what is available in the current installation, shows the compact local reference, fetches the server reference, points to the public documentation page and explains system operators handled before an individual module runs.

Usage

help [cmd] [-i|-l] | help -a | help me | help license

Command reference

help	show installed commands and aliases
help -a	show all repository modules
help <cmd>	show the local reference and active aliases
help <cmd> -i	show the server command reference
help <cmd> -l	show the public documentation link

help hotkeys	show keyboard shortcuts
help aliases	show active command aliases

$	reuse the path of the file declared last (for example, @echo $)
@<cmd> [args]	silently install a missing package, then run the command
<cmd> | <cmd> | ...	run commands sequentially from left to right
<cmd> [args] > <file>	show textual output and append it to a file
<cmd> [args] > <file> -r	show textual output and replace the file
<cmd> [args] > <file> -a	explicitly select append mode

<file>	open a file (when a handler for its extension is registered)
<file.lil> [-s] [-r]	run a lil script from a file
<file.lil> -s	show each script command while it runs
<file.lil> -r	remove the script only after successful execution

Help levels

For everyday work, start with the local reference: it is deliberately compact and quick to scan. -i fetches the current server reference, while -l points to the corresponding public page on lil.dog for deeper reading. help and help -a both use compact multi-column command inventories in Base. Plain help begins with the essential usage and lists only installed commands, with at most three aliases beside each name. help -a lists repository modules and marks those already installed; help <cmd> gives the full active alias list for that command.

Keyboard shortcuts

help hotkeys reflects shortcuts implemented by the installed interface packages. On desktop, the optional hotkeys package can show a passive reminder rail; help hotkeys -on and help hotkeys -off change its visibility for the current session. The rail is not generated on mobile. Editor shortcuts keep their editor meaning, while shortcuts used on an empty terminal command line operate on the most recent terminal result. Clicking anywhere on the desktop rail runs help hotkeys and opens the complete shortcut reference.

Active file

$ resolves to the path of the file declared most recently by an operation that opened, created or wrote a file. It can be passed anywhere a file argument is expected. When the active file itself has a registered extension handler, entering $ as a bare command opens it through that handler.

$	reuse the path of the file declared last (for example, @echo $)

Automatic command prefix

An interactive command may start with @. If the target already exists, it runs immediately. Otherwise lil-terminal silently installs the missing package from the default repository and continues the original command without a full page reload. Secondary command names resolve to the module that owns them.

@<cmd> [args]	silently install a missing package, then run the command

Linear execution

The interface can execute ordinary commands sequentially with an unquoted top-level | separator. Each command starts after the previous command completes, and the sequence stops at the first failure. A UTF-8 .lil file whose first line is #lil can be launched by entering its path; < file.lil is the explicit form of the same operation. Use run when variables, conditions, capture, nested scripts or packed workflows are needed.

Direct .lil execution is quiet by default: the terminal shows command results and statuses without echoing every source command. Use -s when source commands are useful for review or diagnostics. With -r, the original script is removed only after successful execution; a failed script is retained.

<cmd> | <cmd> | ...	run commands sequentially from left to right
<file.lil> [-s] [-r]	run a lil script from a file
<file.lil> -s	show each script command while it runs
<file.lil> -r	remove the script only after successful execution

Output redirection

The final > <file> operator mirrors a command's textual result to a file while keeping the same result on screen. Paths resolve from the current working directory. Existing files are appended by default; -r replaces the destination. Commands that accept values use :, leaving > with one system-wide meaning: output redirection.

<cmd> [args] > <file>	show textual output and append it to a file
<cmd> [args] > <file> -r	show textual output and replace the file
<cmd> [args] > <file> -a	explicitly select append mode

File dispatch

A bare filename is opened only when an installed module has registered a handler for its extension. The same rule applies to the active-file token $ when it is entered as a bare command. This shortcut never installs a file handler automatically.

<file>	open a file (when a handler for its extension is registered)

Minimum package

Minimum Help keeps the installed-command index and current server reference but deliberately omits the repository catalog, public links, shortcut management and alias inventory. Modules whose local comments contain only @more do not keep a local reference.

Feature dependencies

A local reference row marked with @module is shown only when the corresponding optional module is available. The server reference keeps the marker so the capability remains discoverable.

Project support

help me shows the currently published USDT, Bitcoin and Ethereum addresses. Support is voluntary and helps maintain the free core, documentation, testing and future releases. Recommending lil-terminal to developers and hosting users who work without SSH also supports the project. The support view is fetched from the repository when requested, so wallet addresses can change without replacing the installed Help module.

help me	support lil-terminal

Commercial licensing

help license presents the current licensing policy as short readable blocks rather than a dense table. Personal noncommercial use of core generation 1 is free with no time limit. Commercial or organizational production use requires one license per active deployment after the 40-day evaluation period. The license is perpetual for core generation 1 and does not require DRM or mandatory server checks. The view is fetched from the repository when requested, so pricing, wording and the approval date stay current without replacing the installed Help module.

help license	show personal and commercial license terms

Training example — PHP environment, server and repository responses are simulated
Enter	run the current command; insert a line break inside an editor
↑ / ↓	browse command history
⌃R	search backward through command history
Tab	complete a command; indent inside the code editor
Shift+Tab	outdent inside the code editor
⌃S / ⌘S	on an empty command line append the last result to history.log; in the code editor save without closing
⌃+Shift+S / ⌘+Shift+S	on an empty command line replace history.log with the last result
Shift+Enter	save and close the plain or code editor
⌃L / ⌘K	clear terminal output while the command line is active
⌃C / ⌘C	copy the last result when the active command line is empty; ⌃C otherwise cancels the current input
⌃U	clear the current command line
Escape	close an editor without saving, or cancel a hidden prompt
⌃+Shift+L / ⌘+Shift+L	open or hide the web terminal when embedded

Rail

help hotkeys -on	show the desktop shortcut reminder
help hotkeys -off	hide the desktop shortcut reminder
rail click	run @help hotkeys

Training example — PHP environment, server and repository responses are simulated
LIL_RELOAD

Training example — PHP environment, server and repository responses are simulated
LIL_RELOAD

Training example — PHP environment, server and repository responses are simulated
aliases

read	echo
ls	dir

Training example — PHP environment, server and repository responses are simulated
linear

<cmd> | <cmd> | ...	run commands sequentially from left to right and stop after the first failure
<file.lil> [-s] [-r]	run a lil script from a file
<file.lil> -s	show each script command while it runs
<file.lil> -r	remove the script only after successful execution
< <file.lil> [-s] [-r]	explicit form of the same linear file execution

#lil	required first line for a core linear script
# comment	ignored inside a linear script

Direct .lil execution is quiet by default: only command results and statuses are shown. Use -s when source commands themselves are useful for review or diagnostics. With -r, the original script is removed only after successful execution; a failed script is retained.
Linear execution uses ordinary terminal commands. It has no variables, conditions, loops or result-capture language; use run for workflow logic. Automatic @command installation and output redirection remain available inside a linear sequence.

Training example — PHP environment, server and repository responses are simulated
Training repository fixture: support details are fetched from the server; payment addresses intentionally omitted.

Training example — PHP environment, server and repository responses are simulated
Training repository fixture: read the current licence terms from the real repository before commercial use.

Training example — PHP environment, server and repository responses are simulated
Manual not found

Training example — PHP environment, server and repository responses are simulated
Command required

Training example — PHP environment, server and repository responses are simulated
Command required

Training example — PHP environment, server and repository responses are simulated
?

Training example — PHP environment, server and repository responses are simulated
?

Training example — PHP environment, server and repository responses are simulated
?

Training example — PHP environment, server and repository responses are simulated
Manual not found