neko-core

Drive the computer like a person when there is no programmatic path — see the screen, then click/type/scroll. For "open this app and do X", "click the button", "fill this form in the GUI", "automate this desktop/web flow", controlling software that has no API/CLI. (điều khiển máy tính, thao tác giao diện, tự bấm/điền, automate desktop). PREFER code/CLI first; then the accessibility tree (web=DOM, desktop=Windows UIA) which a plain text model drives with no vision; raw-pixel vision only for custom-drawn UIs.

Listen to, transcribe, summarize, and extract decisions/action items from local meetings; nghe, ghi am, chep loi, tom tat cuoc hop tieng Viet.

Create/edit/verify Word, Excel, PowerPoint files (.docx/.xlsx/.pptx); tao/sua/kiem tra tai lieu, bao cao, bang tinh.

Use Facebook Messenger safely to read, draft, send, or watch a conversation through an attached browser tab or Windows UIA.

Mua sắm / tìm nguồn hàng tại Việt Nam (Purchasing Officer). Khi người dùng cần tìm/so sánh/mua mặt hàng (điện tử, tiêu dùng, sỉ/B2B) ở VN, lọc/sắp xếp theo giá (thấp nhất, cao nhất, tăng/giảm), tổng hợp, hay xuất bảng giá/Excel có link, ship nội địa (vd về Bắc Giang). Agent nghiên cứu + lập kế hoạch; con người duyệt và bấm mua.

Use WeChat or Weixin desktop safely for nhan tin, gui tin nhan, tim lien he, doc chat, group chat, or gui file.

Use Zalo desktop safely for nhan tin, gui tin nhan, tim lien he, doc hoi thoai, gui file, or manage Zalo PC chats.

Read or search a SPECIFIC internet platform the right way - YouTube (transcripts, not the page), Twitter/X, Reddit, Facebook/Instagram feeds, GitHub repos/issues, Bilibili, XiaoHongShu, LinkedIn, RSS, podcasts - by ROUTING to the best FREE backend instead of blindly scraping the SPA. Recognize the platform from the URL or the ask, pick the specialized tool (yt-dlp for YouTube subs, gh for GitHub, agent-reach for login/social), and only fall back to web_fetch markdown for a generic page. For "doc/lay/tom tat/tim tren youtube, twitter/X, reddit, facebook, instagram, github, bilibili, tiktok, linkedin, RSS...". (doc va tim noi dung theo tung nen tang - dung dung cong cu, khong cao SPA).

Read/extract content from a web page or feed EFFICIENTLY - posts, articles, listings, comments, search results - ESPECIALLY heavy JavaScript SPAs (Facebook, X/Twitter, LinkedIn, Instagram, Reddit, Xiaohongshu) where naive DOM scraping returns empty, thrashes, and burns minutes + tokens. Plan the read first, prefer the accessibility snapshot or a compact markdown/structured extract over raw querySelectorAll, and for large feeds capture-before-scroll into a deduplicated disk accumulator instead of carrying every post in model context. Stop after a couple of failed extraction approaches instead of trying a 7th selector. For "luot/doc/thu thap/scrape/trich noi dung web, feed, bai viet, binh luan, ket qua tim kiem". (doc va trich noi dung trang web mot cach hieu qua, khong lan man).

Use when facing ANY bug, test failure, crash, or unexpected behavior, BEFORE proposing or trying a fix. Find the ROOT CAUSE first — read the actual error, reproduce, trace the data flow to where it truly goes wrong — instead of guessing patches at the symptom. Stops the flail loop (edit-rerun-edit-rerun with slightly different guesses) that burns steps and masks the real bug under a pile of band-aids. ("go bug/loi/crash, tim nguyen nhan goc, debug co he thong").

Use BEFORE writing implementation code for any feature, bugfix, or behavior change in a codebase that HAS a test runner (bun test, vitest, pytest, cargo test...). Write the test first, watch it FAIL for the right reason, then write the minimal code to pass. Catches "it looks right" bugs the model would otherwise ship unverified, and turns a vague ask into an executable spec. Skip for throwaway one-offs, pure config, or a repo with no test setup. ("viet test truoc, do-den-refactor, TDD").

Verify Neko's terminal UI (TUI) renders correctly at the pixel level — diffs, colors, glyphs, spinner, layout — instead of guessing. Two complementary techniques: a SAFE deterministic render harness (ink-testing-library) for layout/structure, and a LIVE screenshot loop (launch Neko in a real console, screenshot, read with vision) for actual fonts/colors. Use when changing the UI (transcript/markdown/approval/diff rendering) or auditing how Neko looks on Windows. (test giao diện, kiểm tra render, chụp màn hình, dogfood UI).

Deep, multi-source, fact-checked research — especially time-sensitive or factual questions (latest / current / best / newest / benchmark / price / who / when / so sánh / mới nhất / dữ liệu / nghiên cứu / tìm hiểu / đào sâu). Plan the question, search several sources, CROSS-VERIFY every claim against authoritative/primary sources, sanity-check recency, flag conflicts, and answer with citations. Use whenever accuracy matters more than speed.

Visually verify and debug a web page or UI you built/changed - drive it in a browser, capture screenshots (or record a video and extract frames), then READ those images with vision to check, frame by frame, that it actually works. For "open/test/verify/debug the page/site/UI/app in a browser", visual regressions, "did my change render right", flows that only fail at runtime. (kiem tra/debug giao dien/trang web truc quan).