Device Code Login
Complete guide for Device Code Login with Kequan Office — local-first AI in real documents.
What this page helps with
If you need to complete “Device Code Login”, Kequan Office’s path is: draft with AI inside a real Office document, then approve write-back (Account / API / models).
When this usually comes up
People tackling “Device Code Login” usually want faster document/spreadsheet/deck work without cloud AI silently rewriting files, uploading full documents, or locking them to online accounts. Kequan is a desktop suite with optional cloud quota.
Recommended path
Recommended path for “Device Code Login” (Account / API / models):
- 官网注册可圈账户
- 客户端 device/start → 浏览器授权 → poll 取 token
- baseURL=https://api.03122.com
- 或本机 Ollama / BYOK 双轨
Skills / capabilities: Device Code, sessionToken, plans 额度, MCP apply_approved
Features & logic
User intent / skill match / inject queue → (large tasks) work-plan confirmation → model draft (FIX| / outline / formula blocks …) → human Diff review: approve / reject → DocumentAIApply write-back → soft validation cards + undo write-back
Key rules:
- Consult/QA without write-back blocks stays consultative — never silent replace
- Work-plan confirm ≠ permanent silent-edit authorization
- Edit memory is local per document (e.g. “don’t touch amount columns”) and not uploaded
- Inline ⌘/Ctrl+K and ghost ⌘/Ctrl+. share the same trust chain (Tab approve / Esc reject)
- GUI default Shell safe first screen; idle can upgrade to the full AI panel
Trust & limits
- Local-first; no silent full-document upload
- Write-back requires approval; one approval is not permanent
- PDF understanding ≠ full Acrobat editing
- Business templates are scaffolds, not online approval workflows
- Preview installers may be unsigned
- Post-write checks are soft signals; large edits may false-negative
Related reading
If you are working on “Device Code Login”, these links are usually the next useful steps:
Next actions
1) Download the client and set up a local model or official cloud login; 2) run draft → approve → validate on a real file; 3) store hard constraints in memory; 4) enable membership when the team needs quota.
Site https://www.03122.com Docs https://www.03122.com/ko/docs/ API https://api.03122.com Auth https://www.03122.com/ko/account/device.html
FAQ
How to do Device Code Login in Kequan?
Follow the recommended path: use Kequan AI draft then approve write-back.
Will it auto-edit files?
No. Write-back requires explicit approval.
Fully offline?
Editing + local models work offline; cloud quota needs network.
Vs WPS/Word/Copilot?
Kequan emphasizes local-first approve-before-write. See Compare hub.
Developer access?
Device-code login to api.03122.com; MCP stdio requires humanApproval for apply.