mia-code 0.2.0 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (410) hide show
  1. package/.miette/260321.md +1 -0
  2. package/.miette/260323.md +9 -0
  3. package/.miette/260331.md +2 -0
  4. package/.pde/2604011511--83a2d7f9-24a5-4cf4-98d5-036c82f872e8/2604020008--d3417f2c-df12-4f0f-8a1b-d88e7968f822/d3417f2c-df12-4f0f-8a1b-d88e7968f822.md +63 -0
  5. package/.pde/2604011511--83a2d7f9-24a5-4cf4-98d5-036c82f872e8/2604020008--e6c3fc5d-4a70-4523-ba7d-a3250da4c235/e6c3fc5d-4a70-4523-ba7d-a3250da4c235.md +72 -0
  6. package/.pde/2604011511--83a2d7f9-24a5-4cf4-98d5-036c82f872e8/2604020008--efeb00a2-b17a-4d32-b1f0-b90c37a8d24e/efeb00a2-b17a-4d32-b1f0-b90c37a8d24e.md +62 -0
  7. package/.pde/2604011511--83a2d7f9-24a5-4cf4-98d5-036c82f872e8/83a2d7f9-24a5-4cf4-98d5-036c82f872e8.json +302 -0
  8. package/.pde/2604011511--83a2d7f9-24a5-4cf4-98d5-036c82f872e8/83a2d7f9-24a5-4cf4-98d5-036c82f872e8.md +149 -0
  9. package/.pde/2604011511--83a2d7f9-24a5-4cf4-98d5-036c82f872e8/AGENTS.md +31 -0
  10. package/.pde/2604011511--83a2d7f9-24a5-4cf4-98d5-036c82f872e8/meta-decomposition-3-children.md +67 -0
  11. package/.pde/2604040129--61f9dd4d-7aa6-45e6-a58b-e480b1aa6737/61f9dd4d-7aa6-45e6-a58b-e480b1aa6737--from-mia-openclaw-workspace.md +125 -0
  12. package/.pde/2604040129--61f9dd4d-7aa6-45e6-a58b-e480b1aa6737/STATUS.md +1 -0
  13. package/.pde/4f02ba94-9f52-422e-9389-b16f9b37f358.json +177 -0
  14. package/.pde/4f02ba94-9f52-422e-9389-b16f9b37f358.md +77 -0
  15. package/.pde/6ad9244d-5340-490f-b76c-c86728b9de52.json +222 -0
  16. package/.pde/6ad9244d-5340-490f-b76c-c86728b9de52.md +99 -0
  17. package/.pde/8b566792-ed15-4606-96f9-2b6f593d7e6b.json +111 -0
  18. package/.pde/8b566792-ed15-4606-96f9-2b6f593d7e6b.md +67 -0
  19. package/.pde/c7f1e74b-05a5-40e2-9f01-4cc48d2528f7.json +349 -0
  20. package/.pde/c7f1e74b-05a5-40e2-9f01-4cc48d2528f7.md +147 -0
  21. package/.pde/dfc00a78-1da0-4c09-8a16-c6982644051b.json +118 -0
  22. package/.pde/dfc00a78-1da0-4c09-8a16-c6982644051b.md +64 -0
  23. package/GUILLAUME.md +8 -0
  24. package/KINSHIP.md +9 -0
  25. package/MIA_CODE_ARCHITECTURE_REPORT.md +718 -0
  26. package/contextual_research/260119-MIA-CODE--98090899-8aff-4e11-9dc3-8b99466d1.md +1101 -0
  27. package/contextual_research/MIA.md +38 -0
  28. package/contextual_research/MIAWAPASCONE.md +59 -0
  29. package/contextual_research/MIETTE.md +38 -0
  30. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/2504.00218v2.pdf +7483 -12
  31. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/2505.00212v3.pdf +0 -0
  32. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/CONTENT.md +1014 -0
  33. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/DESIGN.gemini.md +242 -0
  34. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/INDEX.md +45 -0
  35. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/2504.00218v2.md +2025 -0
  36. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/2504.00218v2.pdf +7483 -12
  37. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/2505.00212v3.md +1755 -0
  38. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/2505.00212v3.pdf +0 -0
  39. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/footnote_1_12_decomposed_prompting.pdf +0 -0
  40. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/footnote_1_19_hugginggpt_planning.pdf +0 -0
  41. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/footnote_1_1_coordination_challenges.md +766 -0
  42. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/footnote_1_1_coordination_challenges.pdf +3431 -4
  43. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/footnote_1_28_guardrails_multi_agent.md +260 -0
  44. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/footnote_1_28_guardrails_multi_agent.pdf +0 -0
  45. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/footnote_1_2_navigating_complexity.md +558 -0
  46. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/footnote_1_2_navigating_complexity.pdf +0 -0
  47. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/footnote_1_34_hierarchical_multi_agent.pdf +0 -0
  48. package/contextual_research/PDE-generalization--caefee82-efb1-4dbb-8733-691b01581464--260130/sources/footnote_1_5_open_intent_extraction.pdf +0 -0
  49. package/contextual_research/PODCAST.md +109 -0
  50. package/contextual_research/langchain-principles-roadmap.md +157 -0
  51. package/contextual_research/persona-to-narrative-character-inquiry_260201.md +50 -0
  52. package/dist/cli.js +35 -11
  53. package/dist/geminiHeadless.js +8 -2
  54. package/dist/index.js +2 -1
  55. package/dist/mcp/miaco-server.js +10 -1
  56. package/dist/mcp/miatel-server.js +10 -1
  57. package/dist/mcp/miawa-server.js +10 -1
  58. package/dist/mcp/utils.d.ts +6 -1
  59. package/dist/mcp/utils.js +24 -3
  60. package/dist/sessionStore.d.ts +8 -2
  61. package/dist/sessionStore.js +39 -3
  62. package/dist/types.d.ts +1 -0
  63. package/miaco/README.md +124 -0
  64. package/miaco/dist/commands/chart.d.ts +6 -0
  65. package/miaco/dist/commands/chart.d.ts.map +1 -0
  66. package/miaco/dist/commands/chart.js +222 -0
  67. package/miaco/dist/commands/chart.js.map +1 -0
  68. package/miaco/dist/commands/decompose.d.ts +6 -0
  69. package/miaco/dist/commands/decompose.d.ts.map +1 -0
  70. package/miaco/dist/commands/decompose.js +98 -0
  71. package/miaco/dist/commands/decompose.js.map +1 -0
  72. package/miaco/dist/commands/schema.d.ts +6 -0
  73. package/miaco/dist/commands/schema.d.ts.map +1 -0
  74. package/miaco/dist/commands/schema.js +66 -0
  75. package/miaco/dist/commands/schema.js.map +1 -0
  76. package/miaco/dist/commands/stc.d.ts +11 -0
  77. package/miaco/dist/commands/stc.d.ts.map +1 -0
  78. package/miaco/dist/commands/stc.js +590 -0
  79. package/miaco/dist/commands/stc.js.map +1 -0
  80. package/miaco/dist/commands/trace.d.ts +6 -0
  81. package/miaco/dist/commands/trace.d.ts.map +1 -0
  82. package/miaco/dist/commands/trace.js +83 -0
  83. package/miaco/dist/commands/trace.js.map +1 -0
  84. package/miaco/dist/commands/validate.d.ts +6 -0
  85. package/miaco/dist/commands/validate.d.ts.map +1 -0
  86. package/miaco/dist/commands/validate.js +58 -0
  87. package/miaco/dist/commands/validate.js.map +1 -0
  88. package/miaco/dist/decompose.d.ts +93 -0
  89. package/miaco/dist/decompose.d.ts.map +1 -0
  90. package/miaco/dist/decompose.js +562 -0
  91. package/miaco/dist/decompose.js.map +1 -0
  92. package/miaco/dist/index.d.ts +18 -0
  93. package/miaco/dist/index.d.ts.map +1 -0
  94. package/miaco/dist/index.js +83 -0
  95. package/miaco/dist/index.js.map +1 -0
  96. package/miaco/dist/storage.d.ts +60 -0
  97. package/miaco/dist/storage.d.ts.map +1 -0
  98. package/miaco/dist/storage.js +100 -0
  99. package/miaco/dist/storage.js.map +1 -0
  100. package/miaco/package-lock.json +4103 -0
  101. package/miaco/package.json +40 -0
  102. package/miaco/tsconfig.json +18 -0
  103. package/miaco/version-patch-commit-and-publish.sh +1 -0
  104. package/miatel/MISSION_251231.md +3 -0
  105. package/miatel/README.md +107 -0
  106. package/miatel/dist/commands/analyze.d.ts +6 -0
  107. package/miatel/dist/commands/analyze.d.ts.map +1 -0
  108. package/miatel/dist/commands/analyze.js +100 -0
  109. package/miatel/dist/commands/analyze.js.map +1 -0
  110. package/miatel/dist/commands/arc.d.ts +6 -0
  111. package/miatel/dist/commands/arc.d.ts.map +1 -0
  112. package/miatel/dist/commands/arc.js +71 -0
  113. package/miatel/dist/commands/arc.js.map +1 -0
  114. package/miatel/dist/commands/beat.d.ts +6 -0
  115. package/miatel/dist/commands/beat.d.ts.map +1 -0
  116. package/miatel/dist/commands/beat.js +165 -0
  117. package/miatel/dist/commands/beat.js.map +1 -0
  118. package/miatel/dist/commands/theme.d.ts +6 -0
  119. package/miatel/dist/commands/theme.d.ts.map +1 -0
  120. package/miatel/dist/commands/theme.js +54 -0
  121. package/miatel/dist/commands/theme.js.map +1 -0
  122. package/miatel/dist/index.d.ts +18 -0
  123. package/miatel/dist/index.d.ts.map +1 -0
  124. package/miatel/dist/index.js +80 -0
  125. package/miatel/dist/index.js.map +1 -0
  126. package/miatel/dist/storage.d.ts +55 -0
  127. package/miatel/dist/storage.d.ts.map +1 -0
  128. package/miatel/dist/storage.js +100 -0
  129. package/miatel/dist/storage.js.map +1 -0
  130. package/miatel/package-lock.json +4103 -0
  131. package/miatel/package.json +35 -0
  132. package/miatel/src/commands/analyze.ts +109 -0
  133. package/miatel/src/commands/arc.ts +78 -0
  134. package/miatel/src/commands/beat.ts +176 -0
  135. package/miatel/src/commands/theme.ts +60 -0
  136. package/miatel/src/index.ts +94 -0
  137. package/miatel/src/storage.ts +156 -0
  138. package/miatel/tsconfig.json +18 -0
  139. package/miawa/MISSION_251231.md +144 -0
  140. package/miawa/README.md +133 -0
  141. package/miawa/dist/commands/beat.d.ts +6 -0
  142. package/miawa/dist/commands/beat.d.ts.map +1 -0
  143. package/miawa/dist/commands/beat.js +69 -0
  144. package/miawa/dist/commands/beat.js.map +1 -0
  145. package/miawa/dist/commands/ceremony.d.ts +6 -0
  146. package/miawa/dist/commands/ceremony.d.ts.map +1 -0
  147. package/miawa/dist/commands/ceremony.js +239 -0
  148. package/miawa/dist/commands/ceremony.js.map +1 -0
  149. package/miawa/dist/commands/circle.d.ts +6 -0
  150. package/miawa/dist/commands/circle.d.ts.map +1 -0
  151. package/miawa/dist/commands/circle.js +75 -0
  152. package/miawa/dist/commands/circle.js.map +1 -0
  153. package/miawa/dist/commands/eva.d.ts +6 -0
  154. package/miawa/dist/commands/eva.d.ts.map +1 -0
  155. package/miawa/dist/commands/eva.js +73 -0
  156. package/miawa/dist/commands/eva.js.map +1 -0
  157. package/miawa/dist/commands/wound.d.ts +6 -0
  158. package/miawa/dist/commands/wound.d.ts.map +1 -0
  159. package/miawa/dist/commands/wound.js +74 -0
  160. package/miawa/dist/commands/wound.js.map +1 -0
  161. package/miawa/dist/index.d.ts +19 -0
  162. package/miawa/dist/index.d.ts.map +1 -0
  163. package/miawa/dist/index.js +91 -0
  164. package/miawa/dist/index.js.map +1 -0
  165. package/miawa/dist/storage.d.ts +73 -0
  166. package/miawa/dist/storage.d.ts.map +1 -0
  167. package/miawa/dist/storage.js +100 -0
  168. package/miawa/dist/storage.js.map +1 -0
  169. package/miawa/package-lock.json +4103 -0
  170. package/miawa/package.json +36 -0
  171. package/miawa/src/commands/beat.ts +74 -0
  172. package/miawa/src/commands/ceremony.ts +256 -0
  173. package/miawa/src/commands/circle.ts +83 -0
  174. package/miawa/src/commands/eva.ts +84 -0
  175. package/miawa/src/commands/wound.ts +79 -0
  176. package/miawa/src/index.ts +108 -0
  177. package/miawa/src/storage.ts +179 -0
  178. package/miawa/tsconfig.json +18 -0
  179. package/package.json +7 -5
  180. package/references/acp/CLAUDE.md +7 -0
  181. package/references/acp/agent-plan.md +84 -0
  182. package/references/acp/clients.md +31 -0
  183. package/references/acp/extensibility.md +137 -0
  184. package/references/acp/initialization.md +225 -0
  185. package/references/acp/prompt-turn.md +321 -0
  186. package/references/acp/proxy-chains.md +562 -0
  187. package/references/acp/schema.md +3171 -0
  188. package/references/acp/session-list.md +334 -0
  189. package/references/acp/session-modes.md +170 -0
  190. package/references/acp/slash-commands.md +99 -0
  191. package/references/acp/terminals.md +281 -0
  192. package/references/acp/tool-calls.md +311 -0
  193. package/references/acp/typescript.md +29 -0
  194. package/references/claude/agent-teams.md +399 -0
  195. package/references/claude/chrome.md +231 -0
  196. package/references/claude/headless.md +158 -0
  197. package/references/claude/hooks-guide.md +708 -0
  198. package/references/claude/output-styles.md +112 -0
  199. package/references/claude/plugins.md +432 -0
  200. package/references/claude/skills.md +693 -0
  201. package/references/claude/sub-agents.md +816 -0
  202. package/references/copilot/acp/agents.md +32 -0
  203. package/references/copilot/acp/architecture.md +37 -0
  204. package/references/copilot/acp/clients.md +31 -0
  205. package/references/copilot/acp/introduction.md +42 -0
  206. package/references/copilot/acp/registry.md +339 -0
  207. package/references/copilot/acp-server.md +117 -0
  208. package/references/copilot/create-copilot-instructions.md +840 -0
  209. package/references/langchain/llms.txt +833 -0
  210. package/references/langchain/python/agents.md +677 -0
  211. package/references/langchain/python/context-engineering.md +1195 -0
  212. package/references/langchain/python/human-in-the-loop.md +326 -0
  213. package/references/langchain/python/long-term-memory.md +168 -0
  214. package/references/langchain/python/mcp.md +949 -0
  215. package/references/langchain/python/multi-agents/custom-workflow.md +187 -0
  216. package/references/langchain/python/multi-agents/handoffs.md +436 -0
  217. package/references/langchain/python/multi-agents/overview.md +295 -0
  218. package/references/langchain/python/multi-agents/router.md +150 -0
  219. package/references/langchain/python/multi-agents/skills.md +92 -0
  220. package/references/langchain/python/multi-agents/subagents.md +486 -0
  221. package/references/langchain/python/retrieval.md +320 -0
  222. package/references/langchain/python/runtime.md +141 -0
  223. package/references/langchain/python/short-term-memory.md +658 -0
  224. package/references/langchain/python/structured-output.md +712 -0
  225. package/references/langfuse/llms.txt +148 -0
  226. package/references/langgraph/javascript/llms.txt +275 -0
  227. package/references/skills/home.md +259 -0
  228. package/references/skills/integrate-skills.md +103 -0
  229. package/references/skills/specification.md +254 -0
  230. package/references/skills/what-are-skills.md +74 -0
  231. package/rispecs/README.md +164 -0
  232. package/rispecs/_sync_/miadi-code/SPEC.md +313 -0
  233. package/rispecs/_sync_/miadi-code/STATUS.md +177 -0
  234. package/rispecs/_sync_/miadi-code/dashboard/SPEC.md +465 -0
  235. package/rispecs/_sync_/miadi-code/dashboard/STATUS.md +212 -0
  236. package/rispecs/_sync_/miadi-code/multiline-input/SPEC.md +232 -0
  237. package/rispecs/_sync_/miadi-code/multiline-input/STATUS.md +108 -0
  238. package/rispecs/_sync_/miadi-code/pde/SPEC.md +253 -0
  239. package/rispecs/_sync_/miadi-code/pde/STATUS.md +56 -0
  240. package/rispecs/_sync_/miadi-code/stc/SPEC.md +397 -0
  241. package/rispecs/_sync_/miadi-code/stc/STATUS.md +70 -0
  242. package/rispecs/ava-langstack/inquiry-routing-upgrade.spec.md +119 -0
  243. package/rispecs/borrowed_from_opencode/001-client-server-architecture.rispec.md +98 -0
  244. package/rispecs/borrowed_from_opencode/002-event-bus-system.rispec.md +125 -0
  245. package/rispecs/borrowed_from_opencode/003-instance-state-pattern.rispec.md +136 -0
  246. package/rispecs/borrowed_from_opencode/004-namespace-module-pattern.rispec.md +151 -0
  247. package/rispecs/borrowed_from_opencode/005-zod-schema-validation.rispec.md +139 -0
  248. package/rispecs/borrowed_from_opencode/006-named-error-system.rispec.md +155 -0
  249. package/rispecs/borrowed_from_opencode/007-structured-logging.rispec.md +138 -0
  250. package/rispecs/borrowed_from_opencode/008-lazy-initialization.rispec.md +127 -0
  251. package/rispecs/borrowed_from_opencode/009-multi-agent-system.rispec.md +97 -0
  252. package/rispecs/borrowed_from_opencode/010-agent-definition-config.rispec.md +135 -0
  253. package/rispecs/borrowed_from_opencode/011-agent-permission-rulesets.rispec.md +151 -0
  254. package/rispecs/borrowed_from_opencode/012-agent-prompt-templates.rispec.md +141 -0
  255. package/rispecs/borrowed_from_opencode/013-agent-generation.rispec.md +142 -0
  256. package/rispecs/borrowed_from_opencode/014-plan-build-mode-toggle.rispec.md +155 -0
  257. package/rispecs/borrowed_from_opencode/015-subagent-task-delegation.rispec.md +146 -0
  258. package/rispecs/borrowed_from_opencode/016-agent-model-selection.rispec.md +151 -0
  259. package/rispecs/borrowed_from_opencode/017-compaction-agent.rispec.md +150 -0
  260. package/rispecs/borrowed_from_opencode/018-session-persistence.rispec.md +125 -0
  261. package/rispecs/borrowed_from_opencode/019-session-compaction.rispec.md +132 -0
  262. package/rispecs/borrowed_from_opencode/020-session-forking.rispec.md +134 -0
  263. package/rispecs/borrowed_from_opencode/021-session-revert-snapshot.rispec.md +135 -0
  264. package/rispecs/borrowed_from_opencode/022-session-sharing.rispec.md +165 -0
  265. package/rispecs/borrowed_from_opencode/023-session-summary-diffs.rispec.md +165 -0
  266. package/rispecs/borrowed_from_opencode/024-child-sessions.rispec.md +164 -0
  267. package/rispecs/borrowed_from_opencode/025-session-title-generation.rispec.md +162 -0
  268. package/rispecs/borrowed_from_opencode/026-message-parts-model.rispec.md +201 -0
  269. package/rispecs/borrowed_from_opencode/027-streaming-message-deltas.rispec.md +212 -0
  270. package/rispecs/borrowed_from_opencode/028-multi-provider-architecture.rispec.md +184 -0
  271. package/rispecs/borrowed_from_opencode/029-provider-authentication.rispec.md +225 -0
  272. package/rispecs/borrowed_from_opencode/030-model-registry.rispec.md +222 -0
  273. package/rispecs/borrowed_from_opencode/031-cost-tracking.rispec.md +243 -0
  274. package/rispecs/borrowed_from_opencode/032-provider-transform-pipeline.rispec.md +282 -0
  275. package/rispecs/borrowed_from_opencode/033-provider-sdk-abstraction.rispec.md +338 -0
  276. package/rispecs/borrowed_from_opencode/034-tool-registry.rispec.md +110 -0
  277. package/rispecs/borrowed_from_opencode/035-tool-context-injection.rispec.md +155 -0
  278. package/rispecs/borrowed_from_opencode/036-tool-output-truncation.rispec.md +138 -0
  279. package/rispecs/borrowed_from_opencode/037-batch-tool.rispec.md +129 -0
  280. package/rispecs/borrowed_from_opencode/038-multi-edit-tool.rispec.md +167 -0
  281. package/rispecs/borrowed_from_opencode/039-apply-patch-tool.rispec.md +161 -0
  282. package/rispecs/borrowed_from_opencode/040-code-search-tool.rispec.md +143 -0
  283. package/rispecs/borrowed_from_opencode/041-web-fetch-tool.rispec.md +131 -0
  284. package/rispecs/borrowed_from_opencode/042-web-search-tool.rispec.md +159 -0
  285. package/rispecs/borrowed_from_opencode/043-todo-tool.rispec.md +156 -0
  286. package/rispecs/borrowed_from_opencode/044-plan-mode-tool.rispec.md +139 -0
  287. package/rispecs/borrowed_from_opencode/045-task-tool.rispec.md +146 -0
  288. package/rispecs/borrowed_from_opencode/046-question-tool.rispec.md +170 -0
  289. package/rispecs/borrowed_from_opencode/047-external-directory-tool.rispec.md +166 -0
  290. package/rispecs/borrowed_from_opencode/048-file-read-write-tools.rispec.md +205 -0
  291. package/rispecs/borrowed_from_opencode/049-lsp-server-management.rispec.md +104 -0
  292. package/rispecs/borrowed_from_opencode/050-lsp-hover-completion.rispec.md +102 -0
  293. package/rispecs/borrowed_from_opencode/051-lsp-diagnostics.rispec.md +86 -0
  294. package/rispecs/borrowed_from_opencode/052-lsp-root-detection.rispec.md +109 -0
  295. package/rispecs/borrowed_from_opencode/053-remote-mcp-servers.rispec.md +119 -0
  296. package/rispecs/borrowed_from_opencode/054-mcp-oauth-flow.rispec.md +107 -0
  297. package/rispecs/borrowed_from_opencode/055-mcp-tool-conversion.rispec.md +118 -0
  298. package/rispecs/borrowed_from_opencode/056-mcp-connection-monitoring.rispec.md +106 -0
  299. package/rispecs/borrowed_from_opencode/057-local-mcp-servers.rispec.md +116 -0
  300. package/rispecs/borrowed_from_opencode/058-rich-tui.rispec.md +108 -0
  301. package/rispecs/borrowed_from_opencode/059-streaming-display.rispec.md +116 -0
  302. package/rispecs/borrowed_from_opencode/060-permission-prompts.rispec.md +130 -0
  303. package/rispecs/borrowed_from_opencode/061-session-navigation.rispec.md +155 -0
  304. package/rispecs/borrowed_from_opencode/062-syntax-highlighting.rispec.md +151 -0
  305. package/rispecs/borrowed_from_opencode/063-keybinding-system.rispec.md +181 -0
  306. package/rispecs/borrowed_from_opencode/064-multi-level-config.rispec.md +155 -0
  307. package/rispecs/borrowed_from_opencode/065-jsonc-config.rispec.md +190 -0
  308. package/rispecs/borrowed_from_opencode/066-config-env-variables.rispec.md +153 -0
  309. package/rispecs/borrowed_from_opencode/067-config-deep-merging.rispec.md +178 -0
  310. package/rispecs/borrowed_from_opencode/068-remote-org-config.rispec.md +183 -0
  311. package/rispecs/borrowed_from_opencode/069-config-markdown-frontmatter.rispec.md +206 -0
  312. package/rispecs/borrowed_from_opencode/070-managed-config-directory.rispec.md +232 -0
  313. package/rispecs/borrowed_from_opencode/071-plugin-architecture.rispec.md +104 -0
  314. package/rispecs/borrowed_from_opencode/072-plugin-hooks.rispec.md +123 -0
  315. package/rispecs/borrowed_from_opencode/073-plugin-auto-install.rispec.md +115 -0
  316. package/rispecs/borrowed_from_opencode/074-permission-system.rispec.md +133 -0
  317. package/rispecs/borrowed_from_opencode/075-git-worktree-management.rispec.md +126 -0
  318. package/rispecs/borrowed_from_opencode/076-snapshot-system.rispec.md +124 -0
  319. package/rispecs/borrowed_from_opencode/077-snapshot-diff.rispec.md +117 -0
  320. package/rispecs/borrowed_from_opencode/078-snapshot-restore.rispec.md +128 -0
  321. package/rispecs/borrowed_from_opencode/079-worktree-branch-naming.rispec.md +122 -0
  322. package/rispecs/borrowed_from_opencode/080-sqlite-storage.rispec.md +134 -0
  323. package/rispecs/borrowed_from_opencode/081-database-migrations.rispec.md +148 -0
  324. package/rispecs/borrowed_from_opencode/082-database-transactions.rispec.md +138 -0
  325. package/rispecs/borrowed_from_opencode/083-deferred-effects.rispec.md +148 -0
  326. package/rispecs/borrowed_from_opencode/084-permission-rules.rispec.md +123 -0
  327. package/rispecs/borrowed_from_opencode/085-permission-glob-patterns.rispec.md +113 -0
  328. package/rispecs/borrowed_from_opencode/086-permission-merging.rispec.md +134 -0
  329. package/rispecs/borrowed_from_opencode/087-permission-modes.rispec.md +145 -0
  330. package/rispecs/borrowed_from_opencode/088-http-api-server.rispec.md +165 -0
  331. package/rispecs/borrowed_from_opencode/089-openapi-spec-generation.rispec.md +164 -0
  332. package/rispecs/borrowed_from_opencode/090-websocket-support.rispec.md +136 -0
  333. package/rispecs/borrowed_from_opencode/091-sse-streaming.rispec.md +168 -0
  334. package/rispecs/borrowed_from_opencode/092-mdns-discovery.rispec.md +145 -0
  335. package/rispecs/borrowed_from_opencode/093-javascript-sdk.rispec.md +200 -0
  336. package/rispecs/borrowed_from_opencode/094-skill-system.rispec.md +187 -0
  337. package/rispecs/borrowed_from_opencode/095-skill-discovery.rispec.md +182 -0
  338. package/rispecs/borrowed_from_opencode/096-desktop-remote-driving.rispec.md +175 -0
  339. package/rispecs/borrowed_from_opencode/INDEX.md +255 -0
  340. package/rispecs/core.rispecs.md +261 -0
  341. package/rispecs/engines.rispecs.md +241 -0
  342. package/rispecs/formatting.rispecs.md +252 -0
  343. package/rispecs/living-specifications.rispecs.md +361 -0
  344. package/rispecs/mcp.rispecs.md +197 -0
  345. package/rispecs/pde.rispecs.md +399 -0
  346. package/rispecs/pi-mono-envisionning/ENVISIONING.md +366 -0
  347. package/rispecs/pi-mono-envisionning/storytelling-horizon.rispecs.md +76 -0
  348. package/rispecs/pi-mono-envisionning/widget.rispecs.md +2 -0
  349. package/rispecs/relation-to-mcp-structural-thinking.kin.md +72 -0
  350. package/rispecs/research-for-better-framework/CLAUDE.md +7 -0
  351. package/rispecs/research-for-better-framework/survey-pi-openclaw-opencode-openhands.md +210 -0
  352. package/rispecs/session.rispecs.md +277 -0
  353. package/rispecs/stc.rispecs.md +138 -0
  354. package/rispecs/unifier.rispecs.md +317 -0
  355. package/scripts/LAUNCH--mcp-mia-code--testing--2603141315--ac705a66-2c15-4a1c-a26d-9491018c5ba8.sh +2 -0
  356. package/scripts/RESUME--mia-code--mcps--260313--ac705a66-2c15-4a1c-a26d-9491018c5ba8.sh +1 -0
  357. package/scripts/install-widget-in-home-pi-agent-extensions.sh +4 -0
  358. package/scripts/sample-decompose--2604011535-prompt.sh +1 -0
  359. package/skills/deep-search/AGENTS.md +17 -0
  360. package/skills/deep-search/SKILL.md +281 -0
  361. package/skills/deep-search/agent-templates.md +224 -0
  362. package/skills/deep-search/orchestration-patterns.md +95 -0
  363. package/skills/miaco-pde-inquiry-routing-deep-search/AGENTS.md +13 -0
  364. package/skills/miaco-pde-inquiry-routing-deep-search/SKILL.md +136 -0
  365. package/skills/miaco-pde-inquiry-routing-internal-external-relationship/AGENTS.md +4 -0
  366. package/skills/miaco-pde-inquiry-routing-internal-external-relationship/SKILL.md +157 -0
  367. package/skills/miaco-pde-inquiry-routing-local-qmd/AGENTS.md +42 -0
  368. package/skills/miaco-pde-inquiry-routing-local-qmd/SKILL.md +135 -0
  369. package/skills/qmd/AGENTS.md +3 -0
  370. package/skills/qmd/SKILL.md +144 -0
  371. package/skills/qmd/references/mcp-setup.md +102 -0
  372. package/skills/rise-pde-inquiry-session-multi-agents-v3/SKILL.md +234 -0
  373. package/skills/rise-pde-inquiry-session-multi-agents-v3/agent-templates.md +436 -0
  374. package/skills/rise-pde-inquiry-session-multi-agents-v3/orchestration-patterns.md +197 -0
  375. package/skills/rise-pde-inquiry-session-multi-agents-v3/references/ceremonial-technology.md +102 -0
  376. package/skills/rise-pde-inquiry-session-multi-agents-v3/references/creative-orientation.md +99 -0
  377. package/skills/rise-pde-inquiry-session-multi-agents-v3/references/prompt-decomposition.md +73 -0
  378. package/skills/rise-pde-inquiry-session-multi-agents-v3/references/rise-framework.md +74 -0
  379. package/skills/rise-pde-inquiry-session-multi-agents-v3/references/structural-tension.md +82 -0
  380. package/src/cli.ts +35 -11
  381. package/src/geminiHeadless.ts +7 -2
  382. package/src/index.ts +2 -1
  383. package/src/mcp/miaco-server.ts +13 -1
  384. package/src/mcp/miatel-server.ts +13 -1
  385. package/src/mcp/miawa-server.ts +13 -1
  386. package/src/mcp/utils.ts +41 -8
  387. package/src/sessionStore.ts +44 -4
  388. package/src/types.ts +2 -1
  389. package/widget/mia-ceremony/README.md +36 -0
  390. package/widget/mia-ceremony/index.ts +143 -0
  391. package/widget/mia-interceptor/README.md +39 -0
  392. package/widget/mia-interceptor/index.ts +221 -0
  393. package/widget/mia-tools/README.md +37 -0
  394. package/widget/mia-tools/index.ts +569 -0
  395. package/widget/miette-echo/README.md +44 -0
  396. package/widget/miette-echo/index.ts +164 -0
  397. package/.claude/settings.local.json +0 -9
  398. package/.hch/issue_.env +0 -4
  399. package/.hch/issue_add__2601211715.json +0 -77
  400. package/.hch/issue_add__2601211715.md +0 -4
  401. package/.hch/issue_add__2602242020.json +0 -78
  402. package/.hch/issue_add__2602242020.md +0 -7
  403. package/.hch/issues.json +0 -2312
  404. package/.hch/issues.md +0 -30
  405. package/WS__mia-code__260214__IAIP_PDE.code-workspace +0 -29
  406. package/WS__mia-code__src332__260122.code-workspace +0 -23
  407. package/samples/copilot/session-state/be76abaa-a27f-4725-b2a9-22fb45f7e0f7/checkpoints/index.md +0 -6
  408. package/samples/copilot/session-state/be76abaa-a27f-4725-b2a9-22fb45f7e0f7/events.jsonl +0 -213
  409. package/samples/copilot/session-state/be76abaa-a27f-4725-b2a9-22fb45f7e0f7/plan.md +0 -243
  410. package/samples/copilot/session-state/be76abaa-a27f-4725-b2a9-22fb45f7e0f7/workspace.yaml +0 -5
@@ -0,0 +1,766 @@
1
+ LLM Multi-Agent Systems: Challenges and Open Problems
2
+
3
+ Shanshan Han 1 Qifan Zhang 1 Weizhao Jin 2 Zhaozhuo Xu 3
4
+
5
+ 6
6
+ 2
7
+ 0
8
+ 2
9
+
10
+ n
11
+ a
12
+ J
13
+
14
+ 8
15
+ 2
16
+
17
+ ]
18
+
19
+ A
20
+ M
21
+
22
+ .
23
+ s
24
+ c
25
+ [
26
+
27
+ 3
28
+ v
29
+ 8
30
+ 7
31
+ 5
32
+ 3
33
+ 0
34
+ .
35
+ 2
36
+ 0
37
+ 4
38
+ 2
39
+ :
40
+ v
41
+ i
42
+ X
43
+ r
44
+ a
45
+
46
+ Abstract
47
+
48
+ This paper explores multi-agent systems and
49
+ identify challenges that remain inadequately ad-
50
+ dressed. By leveraging the diverse capabilities
51
+ and roles of individual agents, multi-agent sys-
52
+ tems can tackle complex tasks through agent col-
53
+ laboration. We discuss optimizing task alloca-tion, fostering robust reasoning through iterative
54
+ debates, managing complex and layered context
55
+ information, and enhancing memory management
56
+ to support the intricate interactions within multi-
57
+ agent systems. We also explore potential appli-
58
+ cations of multi-agent systems in blockchain sys-
59
+ tems to shed light on their future development and
60
+ application in real-world distributed systems.
61
+
62
+ 1. Introduction
63
+
64
+ Multi-agent systems enhance the capabilities of single LLM
65
+ agents by leveraging collaborations among agents and their
66
+ specialized abilities (Talebirad & Nadiri, 2023; Zhang et al.,
67
+ 2023a; Park et al., 2023; Li et al., 2023; Jinxin et al., 2023).
68
+ It utilizing collaboration and coordination among agents to
69
+ execute tasks that are beyond the capability of any individual
70
+ agent. In multi-agent systems, each agent is equipped with
71
+ distinctive capabilities and roles, collaborating towards the
72
+ fulfillment of some common objectives. Such collaboration,
73
+ characterized by activities such as debate and reflection, has
74
+ proven particularly effective for tasks requiring deep thought
75
+ and innovation. Recent works include simulating interactive
76
+ environments (Park et al., 2023; Jinxin et al., 2023), role-
77
+ playing (Li et al., 2023), reasoning (Du et al., 2023; Liang
78
+ et al., 2023), demonstrating the huge potential of multi-agent
79
+ systems in handling complex real-world scenarios.
80
+
81
+ While existing works have demonstrated the impressive ca-
82
+ pabilities of multi-agent systems, the potential for advanced
83
+ multi-agent systems far exceeds the progress made to date.
84
+ A large number of existing works focus on devising planning
85
+
86
+ 1University of California, Irvine, CA, USA 2University of
87
+ Southern California, Los Angeles, CA, USA 3Stevens Institute of
88
+ Technology, Hoboken, NJ, USA. Correspondence to: Shanshan
89
+ Han <shanshan.han@uci.edu>.
90
+
91
+ strategies within a single agent by breaking down the tasks
92
+ into smaller, more manageable tasks (Chen et al., 2022; Ziqi
93
+ & Lu, 2023; Yao et al., 2023; Long, 2023; Besta et al., 2023;
94
+ Wang et al., 2022b). Yet, multi-agent systems involve agents
95
+ of various specializations and more complex interactions
96
+ and layered context information, which poses challenges to
97
+ the designing of the work flow as well as the whole system.
98
+ Also, existing literature pays limited attention to memory
99
+ storage, while memory plays a critical role in collaborations
100
+ between agents. It enables agents to access to some common
101
+ sense, aligning context with their tasks, and further, learn
102
+ from past work flows and adapt their strategies accordingly.
103
+
104
+ To date, multiple significant challenges that differentiate
105
+ multi-agent systems and single-agent systems remain inade-
106
+ quately addressed. We summarize them as follows.
107
+
108
+ • Optimizing task allocation to leverage agents’ unique
109
+
110
+ skills and specializations.
111
+
112
+ • Fostering robust reasoning through iterative debates
113
+ or discussions among a subset of agents to enhance
114
+ intermediate results.
115
+
116
+ • Managing complex and layered context information,
117
+ such as context for overall tasks, single agents, and
118
+ some common knowledge between agents, while en-
119
+ suring alignment to the general objective.
120
+
121
+ • Managing various types of memory that serve for dif-
122
+ ferent objectives in coherent to the interactions in multi-
123
+ agent systems
124
+
125
+ This paper explores multi-agent systems, offering a sur-
126
+ vey of the existing works while shedding light on the chal-lenges and open problems in it. We study major compo-nents in multi-agent systems, including planning and mem-ory storage, and address unique challenges posed by multi-agent systems, compared with single-agent systems. We
127
+ also explore potential application of multi-agent systems
128
+ in blockchain systems from two perspectives, including 1)
129
+ utilizing multi-agent systems as tools, and 2) assigning an
130
+ agent to each blockchain node to make it represent the user,
131
+ such that the agent can can complete some tasks on behalf
132
+ of the user in the blockchain network.
133
+
134
+ 1
135
+
136
+ LLM Multi-Agent Systems: Challenges and Open Problems
137
+
138
+ 2. Overview
139
+
140
+ 2.1. Structure of Multi-agent Systems
141
+
142
+ The structure of multi-agent systems can be categorized into
143
+ various types, based on the each agent’s functionality and
144
+ their interactions.
145
+
146
+ Equi-Level Structure. LLM agents in an equi-level system
147
+ operate at the same hierarchical level, where each agent
148
+ has its role and strategy, but neither holds a hierarchical
149
+ advantage over the other, e.g., DMAS (Chen et al., 2023);
150
+ see Figure 1(a). The agents in such systems can have same,
151
+ neutral, or opposing objectives. Agents with same goals
152
+ collaborate towards a common goal without a centralized
153
+ leadership. The emphasis is on collective decision-making
154
+ and shared responsibilities (Li et al., 2019). With opposing
155
+ objectives, the agents negotiate or debate to convince the
156
+ others or achieve some final solutions (Terekhov et al., 2023;
157
+ Du et al., 2023; Liang et al., 2023; Chan et al., 2023).
158
+
159
+ Hierarchical Structure. Hierarchical structures (Gronauer
160
+ & Diepold, 2022; Ahilan & Dayan, 2019) typically con-sists of a leader and one or multiple followers; see Fig-ure 1(b). The leader’s role is to guide or plan, while the
161
+ followers respond or execute based on the leader’s instruc-tions. Hierarchical structures are prevalent in scenarios
162
+ where coordinated efforts directed by a central authority
163
+ are essential. Multi-agent systems that explore Stackel-berg games (Von Stackelberg, 2010; Conitzer & Sandholm,
164
+ 2006) fall into this category (Harris et al., 2023). This type
165
+ of game is distinguished by this leadership-followership dy-namic and the sequential nature of decision-making. Agents
166
+ make decisions in a sequential order, where the leader player
167
+ first generate an output (e.g., instructions) then the follower
168
+ players take an action based on the leader’s instruc-tion.
169
+
170
+ Nested Structure. Nested structures, or hybrid structures,
171
+ constitute sub-structures of equi-level structures and/or hier-archical structures in a same multi-agent system (Chan et al.,
172
+ 2023); see Figure 1(c). The “big picture” of the system can
173
+ be either equi-level or hierarchical, however, as some agents
174
+ have to handle complex tasks, they break down the tasks
175
+ into small ones and construct a sub-system, either equi-level
176
+ or hierarchical, and “invite” several agents to help with
177
+ those tasks. In such systems, the interplay between different
178
+ levels of hierarchy and peer-to-peer interaction contributes
179
+ to complexity. Also, the interaction among those different
180
+ structures can lead to intricate dynamics, where strategies
181
+ and responses become complicated due to the presence of
182
+ various influencing factors, including external elements like
183
+ context or environment.
184
+
185
+ Dynamic Structure. Dynamic structures mean that the
186
+ states of the multi-agent system, e.g., the role of agents,
187
+ their relations, and the number of agents in the multi-agent
188
+ system, may change (Talebirad & Nadiri, 2023) over time.
189
+
190
+ As an example,
191
+ (Talebirad & Nadiri, 2023) enables ad-dition and removal of agents to make the system to suit
192
+ the tasks at hand. A multi-agent system may also be con-textually adaptive, with the interaction patterns inside the
193
+ system being modified based on internal system states or
194
+ external factors, such as contexts. Agents in such systems
195
+ can dynamically reconfigure their roles and relationships in
196
+ response to changing conditions.
197
+
198
+ 2.2. Overview of Challenges in Multi-Agent Systems
199
+
200
+ This paper surveys various components of multi-agent sys-tems and discusses the challenges compared with single-agent systems. We discuss planning, memory management,
201
+ as well as potential applications of multi-agent systems on
202
+ distributed systems, e.g., blockchain systems.
203
+
204
+ Planning. In a single-agent system, planning involves the
205
+ LLM agent breaking down large tasks into a sequence of
206
+ small, manageable tasks to achieve specific goals efficiently
207
+ while enhancing interpretability, controllability, and flexi-bility (Li et al., 2024; Zhang et al., 2023b; Nye et al., 2021;
208
+ Wei et al., 2022). The agent can also learn to call external
209
+ APIs for extra information that is missing from the model
210
+ weights (often hard to change after pre-training), or connect
211
+ LLMs with websites, software, and tools (Patil et al., 2023;
212
+ Zhou et al., 2023; Cai et al., 2023) to help reasoning and
213
+ improve performance. While agents in a multi-agent sys-tem have same capabilities with single-agent systems, they
214
+ encounter challenges inherited from the work flow in multi-agent systems. In §3, we discuss partitioning work flow and
215
+ allocating the sub-tasks to agents; we name this process as
216
+ “global planning”; see §3.1. We then discuss task decom-position in each single-agent. Different from planning in a
217
+ single-agent systems, agents in multi-agent systems must
218
+ deal with more sophisticated contexts to reach alignment in-side the multi-agent system, and further, achieve consistency
219
+ towards the overall objective; see §3.2.
220
+
221
+ Memory management. Memory management in single-agent systems include short-term memory during a conver-sation, long-term memory that store historical conversations,
222
+ and, if any, external data storage that serves as a complemen-tary information source for inferences, e.g., RAG (Lewis
223
+ et al., 2020). Memory management in multi-agent systems
224
+ must handle complex context data and sophisticated interac-tion and history information, thus requires advanced design
225
+ for memories. We classify the memories involved in multi-agent systems in §4.1 and then discuss potential challenges
226
+ posed by the sophisticated structure of memory in §4.2.
227
+
228
+ Application. We discuss applications of multi-agent sys-tems in blockchain, a distributed system that involves sophis-ticated design of layers and applications. Basically, multi-agent systems can serve as a tool due to its ability to handle
229
+ sophisticated tasks in blockchain; see §5.1. Blockchain can
230
+
231
+ 2
232
+
233
+ LLM Multi-Agent Systems: Challenges and Open Problems
234
+
235
+ Figure 1. Structures of multi-agent systems.
236
+
237
+ also be integrated with multi-agent systems due to their dis-tributed nature, where an intelligent agent can be allocated
238
+ to an blockchain node to perform sophisticated actions, such
239
+ as negotiations, on behalf of the agent; see §5.2.
240
+
241
+ 3. Planning
242
+
243
+ Planning in multi-agent systems involves understanding the
244
+ overall tasks and design work flow among agents based on
245
+ their roles and specializations, (i.e., global planning) and
246
+ breaking down the tasks for each agent into small manage-able tasks (i.e., local planning). Such process must account
247
+ for functionalities of the agents, dynamic interactions among
248
+ the agents, as well as a more complex context compared with
249
+ single-agent systems. This complexity introduces unique
250
+ challenges and opportunities in the multi-agent systems.
251
+
252
+ 3.1. Global Planning
253
+
254
+ Global planning refers to understanding the overall task
255
+ and split the task into smaller ones and coordinate the sub-tasks to the agents. It requires careful consideration of task
256
+ decomposition and agent coordination. Below we discuss
257
+ the unique challenges in global planning in multi-agent
258
+ systems.
259
+
260
+ Designing effective work flow based on the agents’ spe-cializations. Partitioning responsibilities and designing
261
+ effective work flows for agents is crucial for ensuring that
262
+ the tasks for each agent are executable while meaningful
263
+ and directly contributes to the overall objective in systems.
264
+ The biggest challenge lies in the following perspectives: 1)
265
+ the partition of work flow should maximize the utilization of
266
+ each agent’s unique capabilities, i.e., each agent can handle
267
+ a part of the task that matches its capabilities and expertise;
268
+ 2) each agent’s tasks must align with the overall goal; and
269
+ 3) the design must understand and consider the context for
270
+ the overall tasks as well as each agent. This requires a deep
271
+ understanding of the task at hand and the specific strengths
272
+ and limitations of each agent in the system.
273
+
274
+ Introducing loops for a subset of agents to enhance in-termediate results. Multi-agent systems can be integrated
275
+
276
+ with loops inside one or multiple subsets of agents to im-prove the quality of the intermediate results, or, local op-timal answers. In such loops, agents debate or discuss to
277
+ achieve an optimal results that are accepted by the agents
278
+ in the loop. The iterative process can refine the interme-diate results, leading to a deeper exploration of the task.
279
+ The agents in the loop can adjust their reasoning process
280
+ and plans during the loop, thus have better capabilities in
281
+ handling uncertainties of the task.
282
+
283
+ Game Theory. Game theory provides a well-structured
284
+ framework for understanding strategic interactions in multi-agent systems, particularly for systems that involve com-plex interactions among agents such as debates or discus-sions. A crucial concept in game theory is equilibrium, e.g.,
285
+ Nash Equilibrium (Kreps, 1989) and Stackelberg Equilib-rium (Von Stackelberg, 2010; Conitzer & Sandholm, 2006),
286
+ that describes a state where, given the strategies of others,
287
+ no agent benefits from unilaterally changing their strategy.
288
+ Game theory has been applied in multi-agent systems, espe-cially Stackelberg equilibrium (Gerstgrasser & Parkes, 2023;
289
+ Harris et al., 2023), as the structure of Stackelberg equilib-rium contains is a leader agent and multiple follower agents,
290
+ and such hierarchical architectures are wildely considered in
291
+ multi-agent systems. (Gerstgrasser & Parkes, 2023) designs
292
+ a general multi-agent framework to identify Stackelberg
293
+ Equilibrium in Markov games, and (Harris et al., 2023)
294
+ extend the Stackelberg model to allow agents to consider
295
+ external context information, such as traffic and weather, etc.
296
+ However, some problems are still challenging in multi-agent
297
+ systems, such as defining an appropriate payoff structure
298
+ for both the collective strategy and individual agents based
299
+ on the context of the overall tasks, and efficiently achiev-ing equilibrium states. These unresolved issues highlight
300
+ the ongoing need for refinement in the application of game
301
+ theory to complex multi-agent scenarios.
302
+
303
+ 3.2. Single-Agent Task Decomposition
304
+
305
+ Task decomposition in a single agent involves generating
306
+ a series of intermediate reasoning steps to complete a task
307
+ or arrive at an answer. This process can be represented as
308
+
309
+ 3
310
+
311
+ 7a) Equi-level structureb) Hierarchical structurec) Nested structureLeaderFlowersLeaderFlowers LLM Multi-Agent Systems: Challenges and Open Problems
312
+
313
+ transforming direct input-output (⟨input → output⟩) map-pings into the ⟨input → rational → output⟩ mappings (Wei
314
+ et al., 2022; Zhang et al., 2023b). Task composition can be
315
+ of different formats, as follows.
316
+
317
+ i) Chain of Thoughts (CoT) (Wei et al., 2022) that transforms
318
+ big tasks into step-by-step manageable tasks to represent
319
+ interpretation of the agents’ reasoning (or thinking) process.
320
+
321
+ ii) Multiple CoTs (Wang et al., 2022a) that explores multiple
322
+ independent CoT reasoning paths and return the one with
323
+ the best output.
324
+
325
+ iii) Program-of-Thoughts (PoT) (Chen et al., 2022) that
326
+ uses language models to generate text and programming
327
+ language statements, and finally an answer.
328
+
329
+ iv) Table-of-Thoughts (Tab-CoT) (Ziqi & Lu, 2023) that
330
+ utilize a tabular-format for reasoning, enabling the com-plex reasoning process to be explicitly modelled in a highly
331
+ structured manner.
332
+
333
+ v) Tree-of-Thoughts (ToT) (Yao et al., 2023; Long, 2023)
334
+ that extends CoT by formulating a tree structure to explore
335
+ It enables
336
+ multiple reasoning possibilities at each step.
337
+ generating new thoughts based on a given arbitrary thought
338
+ and possibly backtracking from it.
339
+
340
+ vi) Graph-of-Thoughts-Rationale (GoT-Rationale) (Besta
341
+ et al., 2023) that explores an arbitrary graph to enable ag-gregating arbitrary thoughts into a new one and enhancing
342
+ the thoughts using loops.
343
+
344
+ vii) Rationale-Augmented Ensembles (Wang et al., 2022b)
345
+ that automatically aggregate across diverse rationales to
346
+ overcome the brittleness of performance to sub-optimal
347
+ rationales.
348
+
349
+ In multi-agent systems, task decomposition for a single
350
+ agent becomes more intricate. Each agent must understand
351
+ layered and sophisticated context, including 1) the overall
352
+ tasks, 2) the specific context of the agent’s individual tasks,
353
+ and 3) the contextual information provided by other agents
354
+ in the multi-agent system. Moreover, the agents must align
355
+ these complex, multi-dimensional contexts into their decom-posed tasks to ensure coherent and effective functioning
356
+ within the overall task. We summarize the challenges for
357
+ single agent planning as follows.
358
+
359
+ Aligning Overall Context. Alignment of goals among
360
+ different agents is crucial in multi-agent systems. Each LLM
361
+ agent must have a clear understanding of its role and how it
362
+ fits into the overall task, such that the agents can perform
363
+ their functions effectively. Beyond individual roles, agents
364
+ need to recognize how their tasks fit into the bigger picture,
365
+ such that their outputs can harmonize with the outputs of
366
+ other agents, and, further, ensuring all efforts are directed
367
+ towards the common goal.
368
+
369
+ Aligning Context Between Agents. Agents in multi-agent systems process tasks collectively, and each agent
370
+ must understand and integrate the contextual information
371
+ provided by other agents within the system to ensure that
372
+ the information provided by other agents is fully utilized.
373
+
374
+ Aligning Context for Decomposed Tasks. When tasks of
375
+ each agents are broken down into smaller, more manageable
376
+ sub-tasks, aligning the complex context in multi-agent sys-tems becomes challenging. Each agent’s decomposed task
377
+ must fit their individual tasks and the overall goal while inte-grating with contexts of other agents. Agents must adapt and
378
+ update their understanding of the task in response to context
379
+ provided by other agents, and further, plan the decomposed
380
+ tasks accordingly.
381
+
382
+ Consistency in Objectives. In multi-agent systems, con-sistency in objectives is maintained across various levels,
383
+ i.e., from overall goals down to individual agent tasks and
384
+ their decomposed tasks. Each agent must understand and
385
+ effectively utilize the layered contexts while ensuring its
386
+ task and the decomposed sub-tasks to remain aligned with
387
+ the overall goals. (Harris et al., 2023) extends the Stackel-berg model (Von Stackelberg, 2010; Conitzer & Sandholm,
388
+ 2006) to enable agents to incorporate external context in-formation, such as context (or insights) provided by other
389
+ agents. However, aligning the complex context with the
390
+ decomposed tasks during reasoning remains unresolved.
391
+
392
+ 4. Agent Memory and Information Retrieval
393
+
394
+ The memory in single-LLM agent systems refers to the
395
+ agent’s ability to record, manage, and utilize data, such as
396
+ past historical queries and some external data sources, to
397
+ help inference and enhance decision-making and reason-ing (Yao et al., 2023; Park et al., 2023; Li & Qiu, 2023;
398
+ Wang et al., 2023; Guo et al., 2023). While the memory
399
+ in a single-LLM agent system primarily focuses on inter-nal data management and utilization, a multi-agent system
400
+ requires agents to work collaboratively to complete some
401
+ tasks, necessitating the individual memory capabilities of
402
+ each agent as well as a sophisticated mechanism for sharing,
403
+ integrating, and managing information across agents, thus
404
+ poses challenges to memory and information retrieval.
405
+
406
+ 4.1. Classifications of Memory in Multi-agent Systems
407
+
408
+ Based on the work flow of a multi-agent system, we catego-rize memory in multi-agent system as follows.
409
+
410
+ • Short-term memory: This is the immediate, transient
411
+ memory used by a Large Language Model (LLM) dur-ing a conversation or interaction, e.g., working memory
412
+ in (Jinxin et al., 2023). It is ephemeral, existing only
413
+ for the duration of the ongoing interaction and does
414
+ not persist once the conversation ends.
415
+
416
+ 4
417
+
418
+ LLM Multi-Agent Systems: Challenges and Open Problems
419
+
420
+ • Long-term Memory: This type of memory stores his-torical queries and responses, essentially chat histories
421
+ from earlier sessions, to support inferences for future
422
+ interactions. Typically, this memory is stored in exter-nal data storage, such as a vector database, to facilitate
423
+ recall of past interactions.
424
+
425
+ • External data storage: This is an emerging area in
426
+ LLM research where models are integrated with ex-ternal data storage like vector databases, such that the
427
+ agents can access additional knowledge from these
428
+ databases, enhancing their ability to ground and enrich
429
+ their responses (Lewis et al., 2020). This allows the
430
+ LLM to produce responses that are more informative,
431
+ accurate, and highly relevant to the specific context of
432
+ the query.
433
+
434
+ • Episodic Memory: This type of memory encompasses
435
+ a collection of interactions within multi-agent systems.
436
+ It plays a crucial role when agents are confronted with
437
+ new tasks or queries. By referencing past interactions
438
+ that have contextual similarities to the current query,
439
+ agents can significantly enhance the relevance and ac-curacy of their responses. Episodic Memory allows for
440
+ a more informed approach to reasoning and problem-solving, enabling a more adaptive and intelligent re-sponse mechanism, thus serves as a valuable asset in
441
+ the multi-agent system,
442
+
443
+ • Consensus Memory: In a multi-agent system where
444
+ agents work on a task collaboratively, consensus mem-ory acts as a unified source of shared information, such
445
+ as common sense, some domain-specific knowledge,
446
+ etc, e.g., skill library in (Jinxin et al., 2023). Agents
447
+ utilize consensus memory to align their understand-ing and strategies with the tasks, thus enhancing an
448
+ effective and cohesive collaboration among agents.
449
+
450
+ While both single-agent and multi-agent systems handle
451
+ short-term memory and long-term memory, multi-agent sys-tems introduce additional complexities due to the need for
452
+ inter-agent communication, information sharing, and adap-tive memory management.
453
+
454
+ 4.2. Challenges in Multi-agent Memory Management
455
+
456
+ Managing memory in multi-agent systems is fraught with
457
+ challenges and open problems, especially in the realms of
458
+ safety, security, and privacy. We outline these as follows:
459
+
460
+ Hierarchical Memory Storage: In a multi-agent system,
461
+ different agents often have varied functionalities and access
462
+ needs. Some agents may have to query their sensitive data,
463
+ but they don’t want such data to be accessed by other parties.
464
+ While ensuring the consensus memory to be accessible to
465
+ all clients, implementing robust access control mechanisms
466
+ is crucial to ensure sensitive information of an agent is not
467
+ accessible to all agents. Additionally, as the agents in a sys-tem collaborative on one task, and their functionalities share
468
+ same contexts, their external data storage and memories
469
+ may overlap. If the data and functionalities of these agents
470
+ are not sensitive, adopting an unified data storage can effec-tively manage redundancy among the data, and furthermore,
471
+ ensure consistency across the multi-agent system, leading
472
+ to more efficient and precise maintenance of memory.
473
+
474
+ Maintenance of Consensus Memory: As consensus mem-ory is obtained by all agents when collaborating on a task,
475
+ ensuring the integrity of shared knowledge is critical to en-sure the correct execution of the tasks in the multi-agent
476
+ systems. Any tampering or unauthorized modification of
477
+ consensus memory can lead to systemic failures of the ex-ecution. Thus, a rigorous access control is important to
478
+ mitigate risks of data breaches.
479
+
480
+ Communication and information exchange: Ensuring
481
+ effective communication and information exchange between
482
+ agents is essential in multi-agent systems. Each agent may
483
+ hold critical pieces of information, and seamless integration
484
+ of these is vital for the overall system performance.
485
+
486
+ Management of Episodic Memory. Leveraging past inter-actions within the multi-agent system to enhance responses
487
+ to new queries is challenging in multi-agent systems. De-termining how to effectively recall and utilize contextually
488
+ relevant past interactions among agents for current problem-solving scenarios is important.
489
+
490
+ These challenges underscore the need for continuous re-search and development in the field of multi-agent systems,
491
+ focusing on creating robust, secure, and efficient memory
492
+ management methodologies.
493
+
494
+ 5. Applications in Blockchain
495
+
496
+ Multi-agent systems offer significant advantages to
497
+ blockchain systems by augmenting their capabilities and
498
+ efficiency. Essentially, these multi-agent systems serve as
499
+ sophisticated tools for various tasks on blockchain and Web3
500
+ systems. Also, blockchain nodes can be viewed as agents
501
+ with specific roles and capabilities (Ankile et al., 2023).
502
+ Given that both Blockchain systems and multi-agent sys-tems are inherently distributed, the blockchain networks
503
+ can be integrated with multi-agent systems seamlessly. By
504
+ assigning a dedicated agent to each blockchain node, it’s
505
+ possible to enhance data analyzing and processing while
506
+ bolstering security and privacy in the chain.
507
+
508
+ 5.1. Multi-Agent Systems As a Tool
509
+
510
+ To cast a brick to attract jade, we give some potential direc-tions that multi-agents systems can act as tools to benefit
511
+ blockchain systems.
512
+
513
+ Smart Contract Analysis. Smart contracts are programs
514
+
515
+ 5
516
+
517
+ LLM Multi-Agent Systems: Challenges and Open Problems
518
+
519
+ stored on a blockchain that run when predetermined con-ditions are met. Multi-agents work together to analyze
520
+ and audit smart contracts. The agents can have different
521
+ specializations, such as identifying security vulnerabilities,
522
+ legal compliance, and optimizing contract efficiency. Their
523
+ collaborative analysis can provide a more comprehensive
524
+ review than a single agent could achieve alone.
525
+
526
+ Consensus Mechanism Enhancement. Consensus mech-anisms like Proof of Work (PoW) (Gervais et al., 2016) or
527
+ Proof of Stake (PoS) (Saleh, 2021) are critical for validating
528
+ transactions and maintaining network integrity. Multi-agent
529
+ systems can collaborate to monitor network activities, an-alyze transaction patterns, and identify potential security
530
+ threats. By working together, these agents can propose
531
+ enhancements to the consensus mechanism, making the
532
+ blockchain more secure and efficient.
533
+
534
+ Fraud Detection. Fraud detection is one of the most im-portant task in financial monitoring. As an example, (Ankile
535
+ et al., 2023) studies fraud detection through the perspective
536
+ of an external observer who detects price manipulation by
537
+ analyzing the transaction sequences or the price movements
538
+ of a specific asset. Multi-agent systems can benefit fraud de-tection in blockchain as well. Agents can be deployed with
539
+ different roles, such as monitoring transactions for fraud-ulent activities and analyzing user behaviors. Each agent
540
+ could also focus on different behavior patterns to improve
541
+ the accuracy and efficiency of the fraud detection process.
542
+
543
+ 5.2. Blockchain Nodes as Agents
544
+
545
+ (Ankile et al., 2023) identifies blockchain nodes as agents,
546
+ and studies fraud detection in the chain from the perspective
547
+ an external observer. However, as powerful LLM agents
548
+ with analyzing and reasoning capabilities, there are much
549
+ that the agents can do, especially when combined with game
550
+ theory and enable the agents to negotiate and debate. Below
551
+ we provide some perspectives.
552
+
553
+ Smart Contract Management and Optimization. Smart
554
+ contracts are programs that execute the terms of a contract
555
+ between a buyer and a seller in a blockchain system. The
556
+ codes are fixed, and are self-executed when predetermined
557
+ conditions are met. Multi-agent systems can automate and
558
+ optimize the execution of smart contracts with more flexible
559
+ terms and even dynamic external information from users.
560
+ Agents can negotiate contract terms on behalf of their users,
561
+ manage contract execution, and even optimize gas fees (in
562
+ the context of Ethereum (Wood et al., 2014). The agents can
563
+ analyze context information , such as past actions and pre-defined criteria, and utilize the information with flexibility.
564
+ Such negotiations can also utilize game theory, such as
565
+ Stackelberg Equilibrium (Von Stackelberg, 2010; Conitzer
566
+ & Sandholm, 2006) when there is a leader negotiator and
567
+ Nash Equilibrium (Kreps, 1989) when no leader exists.
568
+
569
+ 6. Conclusion
570
+
571
+ The exploration of multi-agent systems in this paper under-scores their significant potential in advancing the capabil-ities of LLM agents beyond the confines of single-agent
572
+ paradigms. By leveraging the specialized abilities and col-laborative dynamics among agents, multi-agent systems can
573
+ tackle complex tasks with enhanced efficiency and innova-tion. Our study has illuminated challenges that need to be
574
+ addressed to harness the power of multi-agent systems bet-ter, including optimizing task planning, managing complex
575
+ context information, and improving memory management.
576
+ Furthermore, the potential applications of multi-agent sys-tems in blockchain technologies reveal new avenues for
577
+ development, which suggests a promising future for these
578
+ systems in distributed computing environments.
579
+
580
+ References
581
+
582
+ Ahilan, S. and Dayan, P. Feudal multi-agent hierarchies
583
+ for cooperative reinforcement learning. arXiv preprint
584
+ arXiv:1901.08492, 2019.
585
+
586
+ Ankile, L., Ferreira, M. X., and Parkes, D. I see you! robust
587
+ In Multi-Agent
588
+
589
+ measurement of adversarial behavior.
590
+ Security Workshop@ NeurIPS’23, 2023.
591
+
592
+ Besta, M., Blach, N., Kubicek, A., Gerstenberger, R., Gi-aninazzi, L., Gajda, J., Lehmann, T., Podstawski, M.,
593
+ Niewiadomski, H., Nyczyk, P., et al. Graph of thoughts:
594
+ Solving elaborate problems with large language models.
595
+ arXiv preprint arXiv:2308.09687, 2023.
596
+
597
+ Cai, T., Wang, X., Ma, T., Chen, X., and Zhou, D.
598
+ Large language models as tool makers. arXiv preprint
599
+ arXiv:2305.17126, 2023.
600
+
601
+ Chan, C.-M., Chen, W., Su, Y., Yu, J., Xue, W., Zhang, S.,
602
+ Fu, J., and Liu, Z. Chateval: Towards better llm-based
603
+ evaluators through multi-agent debate. arXiv preprint
604
+ arXiv:2308.07201, 2023.
605
+
606
+ Chen, W., Ma, X., Wang, X., and Cohen, W. W. Program
607
+ of thoughts prompting: Disentangling computation from
608
+ reasoning for numerical reasoning tasks. arXiv preprint
609
+ arXiv:2211.12588, 2022.
610
+
611
+ Chen, Y., Arkin, J., Zhang, Y., Roy, N., and Fan, C. Scalable
612
+ multi-robot collaboration with large language models:
613
+ Centralized or decentralized systems? arXiv preprint
614
+ arXiv:2309.15943, 2023.
615
+
616
+ Conitzer, V. and Sandholm, T. Computing the optimal
617
+ strategy to commit to. In Proceedings of the 7th ACM
618
+ conference on Electronic commerce, pp. 82–90, 2006.
619
+
620
+ 6
621
+
622
+ LLM Multi-Agent Systems: Challenges and Open Problems
623
+
624
+ Du, Y., Li, S., Torralba, A., Tenenbaum, J. B., and Mor-Improving factuality and reasoning in lan-datch, I.
625
+ guage models through multiagent debate. arXiv preprint
626
+ arXiv:2305.14325, 2023.
627
+
628
+ Li, Y., Wen, H., Wang, W., Li, X., Yuan, Y., Liu, G., Liu,
629
+ J., Xu, W., Wang, X., Sun, Y., et al. Personal llm agents:
630
+ Insights and survey about the capability, efficiency and
631
+ security. arXiv preprint arXiv:2401.05459, 2024.
632
+
633
+ Gerstgrasser, M. and Parkes, D. C. Oracles & followers:
634
+ Stackelberg equilibria in deep multi-agent reinforcement
635
+ learning. In International Conference on Machine Learn-ing, pp. 11213–11236. PMLR, 2023.
636
+
637
+ Liang, T., He, Z., Jiao, W., Wang, X., Wang, Y., Wang,
638
+ R., Yang, Y., Tu, Z., and Shi, S. Encouraging divergent
639
+ thinking in large language models through multi-agent
640
+ debate. arXiv preprint arXiv:2305.19118, 2023.
641
+
642
+ Gervais, A., Karame, G. O., W¨ust, K., Glykantzis, V., Ritz-dorf, H., and Capkun, S. On the security and performance
643
+ of proof of work blockchains. In Proceedings of the 2016
644
+ ACM SIGSAC conference on computer and communica-tions security, pp. 3–16, 2016.
645
+
646
+ Gronauer, S. and Diepold, K. Multi-agent deep reinforce-ment learning: a survey. Artificial Intelligence Review,
647
+ pp. 1–49, 2022.
648
+
649
+ Guo, Z., Cheng, S., Wang, Y., Li, P., and Liu, Y. Prompt-guided retrieval augmentation for non-knowledge-intensive tasks. arXiv preprint arXiv:2305.17653, 2023.
650
+
651
+ Harris, K., Wu, S., and Balcan, M. F. Stackelberg games
652
+ In Multi-Agent Security Work-with side information.
653
+ shop@ NeurIPS’23, 2023.
654
+
655
+ Jinxin, S., Jiabao, Z., Yilei, W., Xingjiao, W., Jiawen, L.,
656
+ and Liang, H. Cgmi: Configurable general multi-agent
657
+ interaction framework. arXiv preprint arXiv:2308.12503,
658
+ 2023.
659
+
660
+ Kreps, D. M. Nash equilibrium. In Game Theory, pp. 167–177. Springer, 1989.
661
+
662
+ Lewis, P., Perez, E., Piktus, A., Petroni, F., Karpukhin, V.,
663
+ Goyal, N., K¨uttler, H., Lewis, M., Yih, W.-t., Rockt¨aschel,
664
+ T., et al. Retrieval-augmented generation for knowledge-intensive nlp tasks. Advances in Neural Information Pro-cessing Systems, 33:9459–9474, 2020.
665
+
666
+ Li, G., Hammoud, H. A. A. K., Itani, H., Khizbullin, D., and
667
+ Ghanem, B. Camel: Communicative agents for” mind”
668
+ exploration of large scale language model society. arXiv
669
+ preprint arXiv:2303.17760, 2023.
670
+
671
+ Li, X. and Qiu, X. Mot: Memory-of-thought enables chatgpt
672
+ to self-improve. In Proceedings of the 2023 Conference
673
+ on Empirical Methods in Natural Language Processing,
674
+ pp. 6354–6374, 2023.
675
+
676
+ Li, X., Sun, M., and Li, P. Multi-agent discussion mech-anism for natural language generation. In Proceedings
677
+ of the AAAI Conference on Artificial Intelligence, vol-ume 33, pp. 6096–6103, 2019.
678
+
679
+ Long, J. Large language model guided tree-of-thought.
680
+
681
+ arXiv preprint arXiv:2305.08291, 2023.
682
+
683
+ Nye, M., Andreassen, A. J., Gur-Ari, G., Michalewski, H.,
684
+ Austin, J., Bieber, D., Dohan, D., Lewkowycz, A., Bosma,
685
+ M., Luan, D., et al. Show your work: Scratchpads for
686
+ intermediate computation with language models. arXiv
687
+ preprint arXiv:2112.00114, 2021.
688
+
689
+ Park, J. S., O’Brien, J., Cai, C. J., Morris, M. R., Liang,
690
+ P., and Bernstein, M. S. Generative agents: Interactive
691
+ simulacra of human behavior. In Proceedings of the 36th
692
+ Annual ACM Symposium on User Interface Software and
693
+ Technology, pp. 1–22, 2023.
694
+
695
+ Patil, S. G., Zhang, T., Wang, X., and Gonzalez, J. E. Gorilla:
696
+ Large language model connected with massive apis. arXiv
697
+ preprint arXiv:2305.15334, 2023.
698
+
699
+ Saleh, F. Blockchain without waste: Proof-of-stake. The
700
+ Review of financial studies, 34(3):1156–1190, 2021.
701
+
702
+ Talebirad, Y. and Nadiri, A. Multi-agent collaboration:
703
+ Harnessing the power of intelligent llm agents. arXiv
704
+ preprint arXiv:2306.03314, 2023.
705
+
706
+ Terekhov, M., Graux, R., Neville, E., Rosset, D., and Kolly,
707
+ G. Second-order jailbreaks: Generative agents success-fully manipulate through an intermediary. In Multi-Agent
708
+ Security Workshop@ NeurIPS’23, 2023.
709
+
710
+ Von Stackelberg, H. Market structure and equilibrium.
711
+
712
+ Springer Science & Business Media, 2010.
713
+
714
+ Wang, W., Dong, L., Cheng, H., Liu, X., Yan, X., Gao, J.,
715
+ and Wei, F. Augmenting language models with long-term
716
+ memory. arXiv preprint arXiv:2306.07174, 2023.
717
+
718
+ Wang, X., Wei, J., Schuurmans, D., Le, Q., Chi, E., Narang,
719
+ S., Chowdhery, A., and Zhou, D. Self-consistency im-proves chain of thought reasoning in language models.
720
+ arXiv preprint arXiv:2203.11171, 2022a.
721
+
722
+ Wang, X., Wei, J., Schuurmans, D., Le, Q., Chi, E., and
723
+ Zhou, D. Rationale-augmented ensembles in language
724
+ models. arXiv preprint arXiv:2207.00747, 2022b.
725
+
726
+ 7
727
+
728
+ LLM Multi-Agent Systems: Challenges and Open Problems
729
+
730
+ Wei, J., Wang, X., Schuurmans, D., Bosma, M., Xia, F.,
731
+ Chi, E., Le, Q. V., Zhou, D., et al. Chain-of-thought
732
+ prompting elicits reasoning in large language models.
733
+ Advances in Neural Information Processing Systems, 35:
734
+ 24824–24837, 2022.
735
+
736
+ Wood, G. et al. Ethereum: A secure decentralised gener-alised transaction ledger. Ethereum project yellow paper,
737
+ 151(2014):1–32, 2014.
738
+
739
+ Yao, S., Yu, D., Zhao, J., Shafran, I., Griffiths, T. L., Cao, Y.,
740
+ and Narasimhan, K. Tree of thoughts: Deliberate prob-lem solving with large language models. arXiv preprint
741
+ arXiv:2305.10601, 2023.
742
+
743
+ Zhang, J., Xu, X., and Deng, S. Exploring collaboration
744
+ mechanisms for llm agents: A social psychology view,
745
+ 2023a.
746
+
747
+ Zhang, Z., Yao, Y., Zhang, A., Tang, X., Ma, X., He, Z.,
748
+ Wang, Y., Gerstein, M., Wang, R., Liu, G., et al. Igniting
749
+ language intelligence: The hitchhiker’s guide from chain-of-thought reasoning to language agents. arXiv preprint
750
+ arXiv:2311.11797, 2023b.
751
+
752
+ Zhou, S., Xu, F. F., Zhu, H., Zhou, X., Lo, R., Sridhar, A.,
753
+ Cheng, X., Bisk, Y., Fried, D., Alon, U., et al. Webarena:
754
+ A realistic web environment for building autonomous
755
+ agents. arXiv preprint arXiv:2307.13854, 2023.
756
+
757
+ Ziqi, J. and Lu, W. Tab-CoT: Zero-shot tabular chain
758
+ of thought.
759
+ In Rogers, A., Boyd-Graber, J., and
760
+ Okazaki, N. (eds.), Findings of the Association for Com-putational Linguistics: ACL 2023, pp. 10259–10277,
761
+ Toronto, Canada, July 2023. Association for Computa-tional Linguistics. doi: 10.18653/v1/2023.findings-acl.
762
+ 651. URL https://aclanthology.org/2023.
763
+ findings-acl.651.
764
+
765
+ 8
766
+