mirror of
https://github.com/apache/maka.git
synced 2026-10-28 17:04:39 +08:00
Xinhao Xu
57cde86bdc
* feat(assistant): coordinate work through a durable inbox bot Route assistant conversations through a persistent Bot loop with explicit user messaging and sleep. Connect task clarification and feedback, direct index management, discovery reports, and per-request task inbox delivery. Add assistant chat bubbles and avatar support. Generated-by: Codex * fix(assistant): reconcile durable wakes and canonical outbox retries Track wake submission IDs through Runtime execution state instead of scanning transcripts. Preserve pending submissions across recovery and release cancelled waits without losing Inbox entries. Compare canonical message values when replaying the outbox. Generated-by: Codex * fix(assistant): clarify bot duties and separate discovery configuration Separate enabling general discovery from changing its cadence, preserve existing schedules, and report mutation scope explicitly. Align Bot guidance and task/index tool descriptions around work, configuration, and notification responsibilities. Generated-by: Codex * refactor(assistant): focus bot instructions on duties and mechanics Keep reasoning choices with the Bot, document inbox pagination and sleep behavior on tools, and clarify existing-task communication and recovery capabilities. Generated-by: Codex * refactor(assistant): clarify bot duties and delegation * fix(memory): share and parallelize source refreshes in index listings * feat(assistant): add expandable message summaries and typing indicator * fix(assistant): recover interrupted wakes and resolve review checks * fix(browser): allow selected sessions to operate hidden browser panels * fix(ui): render summary markdown and unify expanded body colors * fix(assistant): use Astryx summary button and update SendUser fixtures * fix(assistant): preserve chat empty states and fence browser and message admission * fix(desktop): remove unused personal assistant re-exports * fix(assistant): address remaining provenance, safety and renderer nits * fix(bot): retain production connector provenance through turn admission * fix(assistant): retry failed initiative binding resolution
Maka documentation
This page is the authority map for Maka documentation. Code and contract tests remain the final authority when documentation disagrees with the implementation.
Where information belongs
- Root and package READMEs describe stable product entry points, public seams, and local ownership.
docs/contains current cross-cutting architecture, security, product, and validation contracts.docs/blogs/contains long-form explanations of Maka's design ideas; code and current contracts remain authoritative.- GitHub issues and pull requests contain implementation plans, migration progress, and time-sensitive TODOs.
docs/archive/preserves completed plans and superseded material for historical context. Archived documents are not current implementation guidance.
Start here
- Backend architecture (中文)
- Desktop architecture
- Renderer architecture
- Evaluation kernel
- Runtime package
- Computer Use package
- UI package architecture
- Security policy
- Collect evidence for a Desktop conversation problem (中文)
Blogs
- Log Is the Runtime: How Maka Uses an Append-Only Log to Manage Agent State and Context (中文)
- From Copy-on-Write to Mailboxes: Two Paths for Multi-Agent Scheduling (中文)
- From Stateless Functions to Agent Runtimes: The Serverless Scheduling Unit Is Growing (中文)
Current contracts
Runtime and Eval
- SessionTodo lifecycle
- Desktop message queue
- Work Board contract
- Work Board Phase 1 surface
- WorkHub domain language
- WorkHub Coordination Session ADR
- Runtime resume architecture (中文)
- Runtime PDF rejection recovery
- Runtime Host architecture (中文)
- Peer Mesh architecture (中文)
- Remote Runtime Host setup (中文)
- Runtime resume extraction ledger
- Runtime resume Phase 3–4 implementation route
- Skill catalog policy
- Provider-hosted web search capability
- Agent Swarm
- Side Conversation
- Agent Graph stream scheduling (中文)
- IM 扫码接入 runtime architecture
- Backend architecture chapters
Computer use
- Foundation contract
- Model-loop foundation
- Evidence classes
- Provider evidence contract
- Host events contract
Frontend and validation
Release operations
Security and privacy
Historical material
- Runtime kernel extraction
- Runtime v2 architecture evolution
- Runtime v2 implementation notes
- DeepSeek Reasonix cost runtime design
- Documentation archive
Maintenance
- Add stable cross-cutting documentation to the closest section above.
- Put local architecture beside the code and link it from Start here.
- Keep progress and TODOs in issues or pull requests instead of copying them into stable documents.
- Move completed plans to
docs/archive/; remove a document only after its unique references are updated or no longer needed. - Prefer updating an existing authority over adding a parallel document.
- Keep PR follow-up records, incident investigations, and run logs in the pull request or
docs/archive/, not as new current contracts.notes/anddocs/local/are workspace-local scratch and stay untracked. - Do not commit PR or issue screenshots under
docs/. Attach temporary visual evidence on the GitHub thread; product hero/marketing images live under.github/assets/.