ZacharyZhang-NY
d6c20fc13f
Hard fork of xai-org/grok-build (Apache-2.0) re-targeted as Kigi, an
unofficial Kimi Code CLI community build.
Rename & identity
- 72 xai-*/xai-grok-* crates -> kigi-* (explicit: xai-grok-pager-bin ->
kigi-bin [binary `kigi`], xai-grok-pager -> kigi-tui; rest mechanical);
ptyctl, ptyctl-cli, third_party/ unchanged; proto package
xai.grok.tools.v1 -> kigi.tools.v1
- Config home ~/.kigi (KIGI_SHARE_DIR override), env prefix GROK_* ->
KIGI_*, `kigi --version` carries the unofficial-community-build notice
- clap identity, help text, startup banner, prompt templates rebranded
(templates re-encrypted)
Deletions (PRD removal list #5/#6/#7/#9/#10)
- voice input (xai-grok-voice) and all TUI wiring
- telemetry: Mixpanel client, external OTel stream, Sentry, OTLP layers,
trace/GCS/S3 upload queues (kigi-file-utils halved), workspace upload
module & dc_log, heap-profile uploader, auth-diagnostics uploader,
session-analytics halves of feedback; local zero-egress observability
preserved in new kigi-log crate (unified log, --debug firehose,
subsystem file logs, opt-in instrumentation)
- announcements (crate, remote-settings fields, TUI surfaces)
- plugin marketplace (crate, sources/browse/CTA/extensions-modal tab);
direct plugin install/uninstall/update via kigi-agent git_install kept
- relay/gateway/assets endpoints and features (agent relay, headless
relay transport, gateway bridge, LeaderEnvUrls); leader IPC socket now
~/.kigi/leader.sock + KIGI_LEADER_SOCKET, no ws-url derivation
- functional types rehomed instead of deleted: PermissionMode ->
kigi-config-types, McpInitStrategy -> kigi-mcp, PrCreationSource ->
session signals, TerminalDiagnostics -> kigi-pager-render, agent_id ->
shell util
Endpoints
- kigi-env rewritten: single production KigiEndpoints {coding_api_base_url
https://api.kimi.com/coding/v1 (KIGI_CODE_BASE_URL), oauth_host
https://auth.kimi.com (KIGI_OAUTH_HOST), update_base_url (GitHub
Releases API), upgrade_page_url}; GrokBuildEnvironment enum deleted
Toolchain & workspace hygiene
- Rust 1.97.0 pinned; edition 2024; full cargo update; git2 hoisted to
workspace at 0.21 (Option->Result API migration), quick-xml 0.41
- Root Cargo.toml hand-maintained (PRD §8.1): version 0.1.0 inherited by
all members, members sorted, unused deps pruned
- cargo-deny advisories gate (deny.toml with documented transitive
exceptions); CI workflow (check/clippy/fmt/deny/test, macOS+Linux)
- cross-crate test seams re-gated behind `test-support` cargo feature;
insta snapshot baselines renamed to the kigi_tui prefix
- clippy --workspace --all-targets: zero warnings; fmt clean
Fixes surfaced by the port
- updater probe/installer divergence (bin/kigi vs bin/grok symlink set)
- idle model-metadata refresh dead under KIGI_CODE_BASE_URL override
(new is_effective_coding_endpoint_url, loopback+override aware)
- macOS symlinked-TMPDIR fixture canonicalization (foreign_sessions,
fast-worktree); RSS measurement tests serialized via serial_test
Docs & legal (Apache §4)
- NOTICE added (upstream attribution + change statement); THIRD-PARTY
notices sustained; kigi-tools ported-code notices extended; README,
CONTRIBUTING, SECURITY, AGENTS.md rewritten
Out of scope for M0 (tracked): Kimi auth/inference (M1), search/fetch,
command parity, config import (M2), Computer Hub excision & final
brand-token sweep (M2), distribution & self-update rewrite (M3).
62 lines
2.2 KiB
YAML
62 lines
2.2 KiB
YAML
name: folder-trust-prompt
|
|
description: >
|
|
Full session e2e for the client-side folder-trust prompt. With the feature on
|
|
(`KIGI_FOLDER_TRUST=1`) and the pager running in a git repo that ships a
|
|
repo-local `.mcp.json`, `decide` returns `Prompt` so the trust question renders
|
|
BEFORE any session starts. Accepting it (`y`) persists the grant, lets the
|
|
session proceed, and a submitted prompt streams the mock assistant response —
|
|
proving repo-local loading was gated until the user answered.
|
|
terminal:
|
|
rows: 50
|
|
cols: 120
|
|
environment:
|
|
env:
|
|
- key: KIGI_FOLDER_TRUST
|
|
value: "1"
|
|
# A self-built (unstamped) grok auto-trusts and never prompts; simulate a
|
|
# release build so the folder-trust prompt is actually evaluated.
|
|
- key: KIGI_TEST_VERSION
|
|
value: "0.0.0-sim"
|
|
workspace:
|
|
git_init: true
|
|
files:
|
|
".mcp.json": "{\"mcpServers\": {}}"
|
|
mock:
|
|
response: "FOLDER_TRUST_SESSION_OK assistant reply streamed after the folder was trusted."
|
|
steps:
|
|
# 1. The trust question renders before any session exists.
|
|
- action: wait_for_text
|
|
text: "Do you trust the contents of this directory"
|
|
timeout_ms: 20000
|
|
- action: assert_not_contains
|
|
text: panicked
|
|
# The decline affordance is on screen (keyboard-driven y/N answer; n = quit).
|
|
- action: assert_contains
|
|
text: "No, quit"
|
|
# 2. Accept the folder.
|
|
- action: keys
|
|
keys: "y"
|
|
# 3. The question is gone and the normal welcome / prompt is ready.
|
|
- action: wait_for_text
|
|
text: Quit
|
|
timeout_ms: 20000
|
|
- action: assert_not_contains
|
|
text: "Do you trust the contents of this directory"
|
|
# 4. Submit a prompt — the session must now start (gate answered).
|
|
- action: type_text
|
|
text: "summarize the trusted repo"
|
|
- action: keys
|
|
keys: "<Enter>"
|
|
# 5. The mock assistant response renders ⇒ the session actually started and
|
|
# repo-local loading proceeded ungated.
|
|
- action: wait_for_text
|
|
text: FOLDER_TRUST_SESSION_OK
|
|
timeout_ms: 30000
|
|
- action: assert_chat_completion
|
|
- action: assert_not_contains
|
|
text: panicked
|
|
- action: assert_running
|
|
- action: screenshot
|
|
name: folder-trust-session
|
|
note: "Trust prompt accepted; prompt submitted; mock assistant response rendered."
|