GitHub Copilot CLI: Liku Edition is a terminal-first AI assistant with optional Electron-based visual awareness, Windows UI automation, live UI observation, memory, skill routing, and multi-agent orchestration.
It can run in two main modes:
- Headless terminal mode via
liku chat - Visual Electron mode via
liku startor bareliku
The visual overlay depends on Electron, which is installed as an optional dependency. The headless CLI surface remains usable even when the Electron visual runtime is unavailable.
This repo currently emphasizes:
- reliable desktop/browser automation
- bounded safety checks before execution
- strong Windows support through native UI Automation
- persistent memory/skills under the Liku home directory
- advisory-safe TradingView support, including fail-closed live/unknown trading mode, explicit Paper Trading confirmation, and blocked position-management actions
See also:
- ARCHITECTURE.md
- QUICKSTART.md
- INSTALLATION.md
- docs/AGENT_ORCHESTRATION.md
- docs/GITHUB_GOVERNANCE_VALIDATION_RUNBOOK.md
- docs/VSCODE_SLASH_COMMAND_IMPLEMENTATION.md
Compared with a plain chat CLI, Liku adds:
- Headless command surface for automation and diagnostics
- Optional visual overlay for grid targeting and inspect workflows
- UI watcher for active-window and accessibility-grounded context
- Visual context capture from screenshots
- Memory + skills persisted under
~/.liku/ - Dynamic tool registry with sandboxing and approval flow
- Reflection + telemetry for failure-aware improvement loops
- Multi-agent orchestration with supervisor / researcher / architect / builder / verifier / diagnostician / vision operator roles
likucommand dispatcher insrc/cli/liku.js- terminal chat via
liku chat - Electron app entry via
liku start - Windows UI Automation integration
- screenshot capture and visual verification helpers
- focused AI-service regression suites
Liku is designed to fail closed when confidence or safety is insufficient.
Examples already enforced in code:
- high-risk and critical actions trigger confirmation flows
- fragile TradingView key flows require post-key observation checkpoints
- screenshot-only continuation loops are prevented in terminal chat
- TradingView live/unknown DOM / Depth of Market order-entry and all position-management actions are blocked by advisory-only rails rather than executed
- high-confidence TradingView Paper Trading DOM order-entry requires explicit confirmation before execution can resume
- Node.js 18+
- npm 9+
- Windows, macOS, or Linux
| Platform | Support level | Notes |
|---|---|---|
| Windows | Best supported | Native UI Automation, event-driven watcher, .NET UIA host |
| macOS | Partial | Accessibility permissions required |
| Linux | Partial | AT-SPI2 recommended |
npm install -g copilot-liku-cliVerify:
liku --version
liku --helpIf you only need terminal-first chat and headless automation, this is enough to get started.
git clone https://github.com/TayDa64/copilot-Liku-cli
cd copilot-Liku-cli
npm install
npm linkStart:
liku start
# or
npm startOn Windows, npm install runs a postinstall step that attempts to build the .NET UIA host if the .NET 9+ SDK is available.
You can also build it manually:
npm run build:uiaIf .NET 9 is not available, install still succeeds, but the richer Windows UI-automation path is not built automatically.
liku chatThis is the most practical day-to-day workflow if you want terminal-first AI interaction without opening the Electron UI.
Useful invocation options:
liku chat --model <copilotModelKey>liku chat --execute prompt|true|falseliku chat --project <dir> --repo <name>for explicit project-identity guarding
GitHub entrypoints (read-only + reviewed preview/apply):
liku github auth statusliku github capabilities listliku github capabilities inspect <capability-key>liku github context bundle pr <number> [--slug owner/repo]liku github context bundle issue <number> [--slug owner/repo]liku github context bundle repo [--slug owner/repo] [--limit N] [--out-file <path>]liku github issues comment draft <number> (--body <text> | --body-file <path>) [--slug owner/repo]liku github pr create draft --title <text> [--body <text> | --body-file <path>] [--base branch] [--head branch|owner:branch] [--draft true|false] [--slug owner/repo] [--api false]liku github pr comment draft <number> (--body <text> | --body-file <path>) [--slug owner/repo]liku github pr review draft <number> --event <comment|approve|request-changes> [--body <text> | --body-file <path>] [--slug owner/repo]liku github pr close draft <number> [--slug owner/repo]liku github pr reopen draft <number> [--slug owner/repo]liku github apply <preview-id> --approve [--apply-token <token> | --approval-file <path>]liku github plan build <area> <action> [args...]liku github plan execute <area> <action> [args...]liku github plan execute --plan-file <path>liku github plan resume --guidance-file <path> --resume-token <token> --answers-file <path>liku github plan resume --guidance-file <path> --resume-token <token> --answers-json '{"field":"value"}'liku github plan runs [--slug owner/repo] [--limit N] [--state completed|blocked|aborted|all]liku github plan inspect <run-id> [--slug owner/repo] [--plan-file <path>] [--event-log-file <path>]liku github repo inspectliku github ruleset list [--slug owner/repo] [--limit N] [--api false]liku github ruleset inspect <id> [--slug owner/repo] [--api false]liku github environment list [--slug owner/repo] [--limit N] [--api false]liku github environment inspect <name> [--slug owner/repo] [--api false]liku github secret list [--slug owner/repo] [--limit N] [--api false]liku github secret inspect <name> [--slug owner/repo] [--api false]liku github variable list [--slug owner/repo] [--limit N] [--api false]liku github variable inspect <name> [--slug owner/repo] [--api false]liku github codeowners inspect [--slug owner/repo] [--api false]liku github codeowners create draft [--path <path>] [--body <text> | --body-file <path>] [--base branch] [--head branch] [--slug owner/repo] [--api false]liku github codeowners update draft [--path <path>] [--body <text> | --body-file <path>] [--base branch] [--head branch] [--slug owner/repo] [--api false]liku github template inspect [--slug owner/repo] [--api false]liku github webhook list [--slug owner/repo] [--limit N] [--api false]liku github webhook inspect <id> [--slug owner/repo] [--api false]liku github webhook create draft --events a,b --target-url <url> --secret-ref repo:<ENV_NAME> [--content-type json|form] [--active true|false] [--slug owner/repo]liku github webhook update draft <id> [--events a,b] [--target-url <url>] [--secret-ref repo:<ENV_NAME>] [--content-type json|form] [--active true|false] [--slug owner/repo]liku github webhook ping draft <id> [--slug owner/repo]liku github event list [--slug owner/repo] [--limit N] [--event <name>]liku github event inspect <event-id> [--slug owner/repo]liku github app status [--slug owner/repo] [--probe false] [--api false]liku github app installation inspect [--slug owner/repo] [--api false]liku github app permissions inspect [--slug owner/repo] [--api false]liku github issues listliku github issues inspect <number>liku github pr listliku github pr status [--branch name] [--slug owner/repo]liku github pr view [--branch name] [--slug owner/repo]liku github pr feedback [<number>] [--branch name] [--slug owner/repo] [--limit N]liku github pr inspect <number>liku github pr diff <number>liku github workflow runsliku github workflow inspect <run-id>liku github workflow validate <path> [--body <text> | --body-file <path>] [--slug owner/repo]liku github workflow permissions inspect <path> [--body <text> | --body-file <path>] [--slug owner/repo]liku github workflow requirements inspect <path> [--body <text> | --body-file <path>] [--slug owner/repo]liku github workflow create draft <path> [--body <text> | --body-file <path>] [--base branch] [--head branch] [--slug owner/repo] [--api false]liku github workflow update draft <path> [--body <text> | --body-file <path>] [--base branch] [--head branch] [--slug owner/repo] [--api false]liku github workflow dispatch draft <workflow-id|file> [--ref branch|tag|sha] [--inputs-json <json> | --inputs-file <path>] [--slug owner/repo]liku github workflow rerun draft <run-id> [--failed-only true|false] [--slug owner/repo]liku github workflow cancel draft <run-id> [--slug owner/repo]liku github releases listliku github releases inspect <latest|tag|id>liku github auth status --json --probe falseliku github repo inspect --json --api falseliku github issues list --state all --limit 20liku github issues inspect 321 --slug owner/repoliku github pr list --state all --limit 20liku github pr status --branch feature/demo --slug owner/repoliku github pr feedback --branch feature/demo --slug owner/repo --limit 5liku github pr review draft 123 --event approve --body "Looks good overall" --slug owner/repoliku github pr close draft 123 --slug owner/repoliku github pr reopen draft 123 --slug owner/repoliku github pr create draft --title "Add overlay diagnostics" --base main --head feature/demo --slug owner/repoliku github pr inspect 123 --slug owner/repoliku github pr diff 123 --limit 50liku github workflow runs --workflow ci.yml --limit 10liku github workflow inspect 9001 --slug owner/repoliku github workflow validate .github/workflows/validate.yml --body-file C:\Users\you\validate.yml --slug owner/repoliku github workflow permissions inspect .github/workflows/validate.yml --slug owner/repoliku github workflow requirements inspect .github/workflows/validate.yml --slug owner/repoliku github codeowners create draft --body-file C:\Users\you\CODEOWNERS --base main --slug owner/repoliku github webhook create draft --events push,pull_request,workflow_run --target-url https://assistant.example.com/github/webhook --secret-ref repo:LIKU_WEBHOOK_SECRET --content-type json --slug owner/repoliku github event list --slug owner/repo --limit 10 --event pushliku github plan runs --slug owner/repo --limit 10 --state blockedliku github plan inspect github-run-123 --slug owner/repoliku github workflow create draft .github/workflows/validate.yml --body-file C:\Users\you\validate.yml --base main --slug owner/repoliku github workflow update draft .github/workflows/validate.yml --body-file C:\Users\you\validate.yml --base main --slug owner/repoliku github workflow dispatch draft validate.yml --ref main --inputs-json '{"target":"staging"}' --slug owner/repoliku github workflow rerun draft 9001 --failed-only true --slug owner/repoliku github workflow cancel draft 9002 --slug owner/repoliku github releases list --limit 5 --slug owner/repoliku github releases inspect latest --slug owner/repoliku github issues comment draft 321 --body "Please retest with 0.0.16" --slug owner/repoliku github pr comment draft 123 --body "Looks good overall" --slug owner/repoliku github apply github-write-preview-123 --approve --approval-file C:\Users\you\.liku\github\writes\github-write-preview-123.approval.json
Repo governance inventory notes:
- rulesets, environments, webhooks, and app installation visibility are repo-scoped and read-only
- Actions secrets and variables stay metadata-only in model-visible output
codeowners inspectandtemplate inspectcan prefer the current workspace and run offline with--api falsecodeowners create draftandcodeowners update draftstay reviewed previews only; apply still goes throughliku github apply ...and opens a dedicated branch plus draft PR for the CODEOWNERS patchwebhook create draft,webhook update draft, andwebhook ping draftstay reviewed previews only; apply still goes throughliku github apply ..., andrepo:<ENV_NAME>secret refs are resolved from the local environment only at apply time so raw webhook secrets are never persisted in preview artifactsevent listandevent inspectread the local GitHub event journal under~/.liku/github/events; this Phase 10B slice persists sanitized delivery artifacts and a durable JSONL journal locally, but intentionally stops short of starting a live webhook receiverplan runsandplan inspectread the local GitHub plan ledger under~/.liku/github/plans; this Phase 10C slice adds durable local run inspection and replay context only, and does not introduce a new orchestration or apply path- missing GitHub tokens or repo-admin scopes should warn and fail soft instead of mutating or hard failing the command surface
Useful chat commands:
/help/github help/github capabilities list/github capabilities inspect pr.diff/github context bundle pr 7 --api false/github context bundle repo --limit 5 --api false/github ruleset list --limit 5 --slug owner/repo --api false/github codeowners inspect --api false/github codeowners create draft --body-file <path> --base main --slug owner/repo/github template inspect --api false/github webhook create draft --events push,pull_request --target-url https://assistant.example.com/github/webhook --secret-ref repo:LIKU_WEBHOOK_SECRET --content-type json --slug owner/repo/github webhook update draft 12345 --events workflow_run,pull_request_review --target-url https://assistant.example.com/github/webhook --secret-ref repo:LIKU_WEBHOOK_SECRET --slug owner/repo/github webhook ping draft 12345 --slug owner/repo/github event list --slug owner/repo --limit 10 --event push/github event inspect <event-id> --slug owner/repo/github plan runs --slug owner/repo --limit 10 --state blocked/github plan inspect <run-id> --slug owner/repo/github app status --slug owner/repo --probe false --api false/github issues comment draft 321 --body "Please retest with 0.0.16" --slug owner/repo/github pr create draft --title "Add overlay diagnostics" --base main --head feature/demo --slug owner/repo --api false/github pr comment draft 123 --body "Looks good overall" --slug owner/repo/github pr review draft 123 --event approve --body "Looks good overall" --slug owner/repo/github pr close draft 123 --slug owner/repo/github pr reopen draft 123 --slug owner/repo/github workflow validate .github/workflows/validate.yml --body-file <path> --slug owner/repo/github workflow create draft .github/workflows/validate.yml --body-file <path> --base main --slug owner/repo/github workflow dispatch draft validate.yml --ref main --inputs-json '{"target":"staging"}' --slug owner/repo/github pr status --branch feature/demo --slug owner/repo --api false/github pr view --branch feature/demo --slug owner/repo --api false/github pr feedback --branch feature/demo --slug owner/repo --limit 5 --api false/github plan build pr diff 7 --limit 30 --api false/github plan execute pr diff 7 --limit 30 --api false/github plan execute --plan-file <path>/github plan resume --guidance-file <path> --resume-token <token> --answers-file <path>/login/model/provider/status/capture/vision on|off/memory/memory export [path]/memory import <path>/skills/tools/rmodel/state/clear
Terminal-chat-specific controls:
/sequence on|off/recipes on|off(plan) ...for plan-only orchestration routing
Current top-level CLI defaults and seam controls:
LIKU_DEBUG=1enables CLI debug output by defaultLIKU_JSON=1enables JSON output by default where commands support itLIKU_DISABLE_RUNTIME_TRACE=1disables CLI/runtime trace logging
Phase 0/1 introduces additive seam-level feature flags for future gated capabilities:
LIKU_ENABLE_GITHUB=1opt-in marker for future GitHub command surfacesLIKU_ENABLE_GITHUB_WRITES=1enable the low-risk reviewed GitHub write preview/apply surfaceLIKU_HOME_OVERRIDE=<path>override the Liku home directory for isolated proof/test artifact runsLIKU_ENABLE_AGENTS=0|1override seam-level agent availability metadataLIKU_ENABLE_DYNAMIC_TOOLS=0|1override seam-level dynamic-tool availability metadataLIKU_APPROVAL_MODE=prompt|auto|neverset the default approval preference recorded by the command seamLIKU_DRY_RUN_DEFAULT=1mark command-seam requests as dry-run preferred by default
These Phase 0/1 flags remain additive seam scaffolding. The explicit read-only liku github ... commands added in Phase 2 are still allowed directly, while the low-risk Phase 7 write surface requires both LIKU_ENABLE_GITHUB=1 and LIKU_ENABLE_GITHUB_WRITES=1 before preview/apply issue-comment and PR-comment flows are allowed.
Config precedence for the current CLI surface:
- explicit command-line flags/options
- supported environment defaults (
LIKU_DEBUG,LIKU_JSON, and the seam flags above) - command/module-local defaults
liku startor simply:
likuThis launches the Electron runtime with overlay support.
liku doctor
npm run smoke:shortcuts
npm run smoke:chat-direct
npm run test:uiIf you want the most relevant current regression bundle for AI/service behavior:
npm run test:ai-focusedFor the Phase 0/1 CLI seam milestone specifically, run:
npm run test:cli-phase01For the Phase 2 read-only GitHub milestone, run:
npm run test:github-phase2For the Phase 7 reviewed GitHub write-preview/apply milestone, run:
npm run test:github-phase7-writesThe top-level CLI currently exposes these commands through src/cli/liku.js.
| Command | Description |
|---|---|
start |
Start the Electron agent with overlay |
doctor |
Diagnostics: version, environment, active window |
chat |
Interactive AI chat in the terminal |
click |
Click element by text or coordinates |
find |
Find UI elements matching criteria |
type |
Type text at the current cursor position |
keys |
Send keyboard shortcut combinations |
screenshot |
Capture a screenshot |
verify-hash |
Poll until screenshot hash changes |
verify-stable |
Wait until visual output is stable |
window |
Focus or list windows |
mouse |
Move mouse to coordinates |
drag |
Drag between points |
scroll |
Scroll up or down |
wait |
Wait for element appearance/disappearance |
repl |
Interactive automation shell |
memory |
Inspect/manage memory notes |
skills |
Inspect/manage skill library |
tools |
Inspect/manage dynamic tool registry |
github |
GitHub auth, repo, issue, PR, workflow, and release inspection plus reviewed issue/PR-comment previews and explicit CLI apply |
analytics |
View telemetry analytics |
Examples:
liku doctor --json
liku github auth status
liku github repo inspect --json
liku github context bundle pr 7 --api false
liku github context bundle repo --limit 5 --api false
liku github ruleset list --limit 10 --slug owner/repo --api false
liku github codeowners inspect --api false
liku github codeowners create draft --body-file C:\Users\you\CODEOWNERS --base main --slug owner/repo
liku github webhook create draft --events push,pull_request,workflow_run --target-url https://assistant.example.com/github/webhook --secret-ref repo:LIKU_WEBHOOK_SECRET --content-type json --slug owner/repo
liku github event list --slug owner/repo --limit 10 --event push
liku github plan runs --slug owner/repo --limit 10 --state blocked
liku github plan inspect github-run-123 --slug owner/repo
liku github app permissions inspect --slug owner/repo --api false
liku github issues comment draft 321 --body "Please retest with 0.0.16" --slug owner/repo
liku github pr comment draft 123 --body "Looks good overall" --slug owner/repo
liku github apply github-write-preview-123 --approve --approval-file C:\Users\you\.liku\github\writes\github-write-preview-123.approval.json
liku github issues list --state all --limit 10
liku github issues inspect 321
liku github pr list --state all --limit 10
liku github pr inspect 7
liku github pr diff 7 --limit 30
liku github workflow runs --workflow ci.yml --limit 5
liku github workflow inspect 9001
liku github releases list --limit 5
liku github releases inspect latest
liku chat --model gpt-4.1
liku click "Submit"
liku find "Save" --type Button
liku keys ctrl+shift+s
liku screenshot --memory --hash --json
liku verify-stable --metric dhash --stable-ms 800 --timeout 15000 --interval 250 --json
liku window "Visual Studio Code"Liku uses multiple observation/control surfaces depending on what is available:
- Windows UI Automation when semantic controls are discoverable
- active-window and watcher context when semantic controls are limited
- screenshot capture when visual grounding is needed
- grid/overlay workflows in Electron mode
Source of truth for these mappings is the current Electron main-process registration in src/main/index.js.
| Shortcut | Action |
|---|---|
Ctrl+Alt+Space |
Toggle chat window |
Ctrl+Shift+O |
Toggle overlay visibility |
Ctrl+Alt+I |
Toggle inspect mode |
Ctrl+Alt+F |
Toggle fine grid |
Ctrl+Alt+G |
Show all grid levels |
Ctrl+Alt+= |
Zoom in |
Ctrl+Alt+- |
Zoom out |
Ctrl+Alt+X |
Cancel current selection |
TradingView support is a professional advisory / observation workflow, not a broker-execution workflow. The current implementation is modularized behind tool registries and provider hooks so TradingView-specific behavior does not live directly in generic execution loops.
The runtime now carries TradingView-specific grounding for:
- chart/timeframe surfaces
- alert dialogs
- drawing tools
- indicators / studies
- Pine Editor
- DOM / Depth of Market metadata
src/main/tools/tradingview-tool.js is the canonical TradingView facade. It registers:
- ordered TradingView rewrite handlers through the tool rewrite registry
- TradingView risk assessment through the tool risk registry
- Pine authoring system contracts through the system-contract provider registry
- TradingView observation/checkpoint helpers through the observation-provider registry
- Pine resume lifecycle decisions through the lifecycle-hook registry
Tool rewrite/risk registries are default-on. Temporary compatibility escape hatches remain available with LIKU_USE_TOOL_REGISTRY_REWRITES=0 and LIKU_USE_TOOL_REGISTRY_RISKS=0.
Liku can reason about TradingView UI state, but it must remain advisory-safe.
Specifically:
- TradingView live or unknown-mode DOM order-entry actions are blocked fail-closed
- high-confidence Paper Trading DOM order-entry is high-risk, requires explicit confirmation, and resumes only through the confirmation flow
- TradingView DOM flatten / reverse / cancel-all style controls are classified as critical
- TradingView position-management actions are blocked before execution by advisory-only safety rails
This means Liku can help observe, explain, and guide. It must not place live/unknown-mode orders or manage positions, and Paper Trading order-entry remains gated by explicit confirmation.
When a TradingView chart has established focus, Ctrl+E is treated as the grounded shortcut for opening Pine Script Editor. When chart focus is not established, Liku falls back to the verified quick-search route instead of assuming the shortcut will land in TradingView.
Handled through ai-service.handleCommand():
/help/github ...GitHub inspection plus reviewed preview creation via shared typed adapters/login//logout/model [key]/provider [name]/setkey <provider> <key>/status/state [clear]/clear/vision [on|off]/capture/memory [search <query>|clear]/skills/tools [approve|revoke <name>]/rmodel [model|off]
GitHub inspection operations and reviewed preview creation now ship both as top-level liku github ... commands and as shared /github ... slash commands routed through ai-service.handleCommand(). Actual apply remains CLI-only. For the source-grounded VS Code / Codespaces implementation note, see docs/VSCODE_SLASH_COMMAND_IMPLEMENTATION.md.
Handled in src/main/index.js:
/agenticor/agent/orchestrate <task>/research <query>/build <spec>/verify <target>/agentsor/agent-status/agent-reset- experimental
/produce <prompt>path
- Supervisor
- Researcher
- Architect
- Builder
- Verifier
- Diagnostician
- Vision Operator
Hook-based enforcement lives under .github/hooks/ and is used to enforce role boundaries, audit tool calls, and validate subagent outputs.
The cognitive layer persists state under ~/.liku/.
Primary directories:
~/.liku/
├── memory/
├── skills/
├── tools/
├── telemetry/
└── preferences.json
Important note:
- the project still contains migration support from legacy
~/.liku-cli/ - Electron session data still uses
~/.liku-cli/session/to avoid Chromium lock issues
- memory store for structured notes
- skill router with TF-IDF + scope-aware matching
- dynamic tools with proposal/approval flow and sandbox execution
- telemetry + reflection for bounded self-correction loops
- AWM (Agent Workflow Memory) extraction from successful multi-step procedures
Liku follows a fail-closed execution model.
Examples of current safeguards:
- destructive shortcuts such as close-window combos require explicit confirmation
- low-confidence target interactions are elevated in risk
- focus verification runs after action sequences
- post-action verification checks foreground/process alignment after bounded retries
- TradingView key workflows use observation checkpoints before follow-up typing
- DOM trade-entry and order-management actions are blocked by policy
This safety posture is intentional: if the system cannot establish enough evidence, it should stop rather than guess.
npm run test:ai-focused
npm run test:windows-observation-flow
npm run test:chat-actionability
npm run test:ui
npm run test:github-phase8-workflows
npm run test:github-phase9-readonlynpm run smoke
npm run smoke:shortcuts
npm run smoke:chat-direct
npm run smoke:tradingview-live -- --dry-run
npm run test:skills:inline
npm run proof:inline -- --list-suitesThe current focused AI bundle runs:
scripts/test-windows-observation-flow.jsscripts/test-bug-fixes.jsscripts/test-chat-actionability.jsscripts/test-ai-service-contract.jsscripts/test-ai-service-browser-rewrite.jsscripts/test-ai-service-state.jsscripts/test-tradingview-registry-parity.js
TradingView runtime behavior changes should also use docs/TRADINGVIEW_VALIDATION_RUNBOOK.md. The live smoke lane is opt-in and writes artifacts under artifacts\live-validation\; Playwright/browser evidence is secondary and must only validate browser-visible state after Liku actions.
GitHub workflow capability changes should also use docs/GITHUB_WORKFLOW_VALIDATION_RUNBOOK.md. Phase 8 workflow dispatch/rerun/cancel live proofs must stay on reversible, non-production workflows and keep apply on the CLI only.
GitHub governance inventory changes should also use docs/GITHUB_GOVERNANCE_VALIDATION_RUNBOOK.md. Phase 9A proofs should stay read-only, capture redacted metadata only, and prefer --api false local inspection for CODEOWNERS/template validation when possible.
src/
├── cli/ # CLI entrypoint and command modules
├── main/ # Electron main process + AI service
├── renderer/ # Electron renderer processes
├── native/ # Native integrations, including Windows UIA hosts
├── shared/ # Shared utilities
└── assets/ # Static assets
scripts/ # Regression tests, smoke tests, proof harnesses
docs/ # Architecture and orchestration docs
.github/hooks/ # Hook-based enforcement and artifacts
- QUICKSTART.md
- INSTALLATION.md
- ARCHITECTURE.md
- CONFIGURATION.md
- TESTING.md
- CONTRIBUTING.md
- RELEASE_PROCESS.md
- docs/AGENT_ORCHESTRATION.md
- docs/GITHUB_GOVERNANCE_VALIDATION_RUNBOOK.md
- docs/GITHUB_WORKFLOW_VALIDATION_RUNBOOK.md
- docs/INTEGRATED_TERMINAL_ARCHITECTURE.md
If you hit a problem, include as much of the following as possible in an issue:
- platform
- Node version
- command used
- active model/provider
- whether you were using Electron mode or
liku chat - reproduction steps
- expected vs actual behavior
- any relevant
doctor --jsonoutput
Liku is evolving quickly, and the most useful bug reports are the ones tied to real runtime behavior and clear reproduction steps.