xonecas.io
60255
Zn

Zoea-Nova / commit f69355a

docs(known-issues): add evidence notes

xonecas2026-02-04 f69355a13113282a7a581323c26ef6e0b05eaa6d parent c119e8a

2 files changed

.opencode/commands/zoea-known-issues.md+1−0
@@ -16,3 +16,4 @@ Read `documentation/KNOWN_ISSUES.md` and:
1616 - Read the documentation before investigating.
1717 - Gather all required context first.
1818 - Use explorer subagents to gather information.
19+- Use zoea_analyzer agents if you need database information.
documentation/KNOWN_ISSUES.md+15−18
@@ -4,45 +4,42 @@ These are the currently known issues to investigate:
44
55 ## Authentication & Account Management
66
7-- [ ] Myses have trouble logging in and mostly resort to new accounts. We need to create a new table for username/password pairs available to the swarm, and which ones are in use or not. Then introduce a new zoea tool to fetch this data. Revise the prompt to ensure we encourage re-using swarm accounts first, and only create new ones as a fallback. If a mysis attempts to login to an active account, provide a directive response "use these available details" or "register a new one"
8-
97 - [ ] Captain's Log Bug: There is a consistent pattern of Myses failing to use captains_log_add. They appear to be trying to "remember" their registration password but are encountering an empty_entry error from the MCP server. This suggests the LLM might be misformatting the arguments for this specific tool. Related: Myses find each other's passwords and fail to login. Myses do not have a reliable way to re-use usernames they created in the past.
8+- [ ] Evidence: System prompt mentions captains_log_add but does not define argument shape; MCP proxy forwards raw arguments upstream. Myses can send empty or malformed payloads and hit empty_entry.
109
1110 ## Context & Memory Management
1211
1312 - [ ] Myses should know to prefer more recent information in their context. We should improve our context messages list to compact repeated state updates into the most recent state snapshot. We should also re-enforce the use of search tools to access older memory. Maybe increase the tool loop for longer autonomy.
13+- [ ] Evidence: Sliding-window context uses MaxContextMessages=20 with no compaction of repeated state snapshots.
1414
1515 ## Prompt & Behavior
1616
1717 - [ ] Mysis prompt review: Encourage myses to collaborate together via zoea tooling to create a goal and collaborate towards it. Encourage to pick a Crustacean Cosmos + Zoea/Mysis themed username. Critical rules must be in every prompt, not only the first one.
18+- [ ] Evidence: SystemPrompt includes collaboration + themed usernames; ContinuePrompt does not include CRITICAL RULES, so enforcement depends on system prompt being present in the 20-message window.
1819
1920 - [ ] Cognitive Looping and Prompt Inefficiency: Myses can get stuck in "cooldown" loops or redundant "waiting" states, consuming tokens every 30 seconds without operational progress. The system prompts Myses every tick regardless of their state. Myses may hallucinate non-existent cooldowns or fail to use non-traveling actions during long journeys.
21+- [ ] Evidence: ContinuePrompt is sent on a fixed 30-second ticker with no state-aware suppression.
2022
2123 ## Gameplay Issues
2224
2325 - [ ] Travel Duration: The travel to the asteroid belt is a long-duration task (30k+ ticks). The Myses correctly entered a "waiting" mode, showing they can manage long-term state without wasting tokens on redundant actions. However, Mysis should continue to act on their tick during travel. They can still use other actions when traveling, like chatting or other non-traveling actions in the game. Currently the Mysis loses their ticks waiting when they could be using the turns to explore the game A …
26+- [ ] Evidence: ContinuePrompt is always issued while running, even during travel/cooldown states.
2427
2528 ## TUI Issues
2629
2730 - [ ] Broadcast messages are labelled YOU in focus view. We don't differentiate between swarm broadcast senders. We need to start tracking it and reflecting it in the UI, in a consistent formatting and style according to our thematic and design rules (see the documentation before doing changes).
28-
2931 - [ ] Reasoning messages are not displayed in the UI. They should appear in the focus mysis view, and be rendered with the purple color we use for text elsewhere. Note: Reasoning capture and storage was implemented in v1.5.2, but UI display is still pending.
32+- [ ] Username status for each mysis focus view and in commander view.
33+- [ ] Evidence: Focus view labels are based on Role only (broadcast source ignored); reasoning is stored but not rendered; TUI models do not include account username fields.
3034
31-- [ ] username status for each mysis focus view and in commander view.
32-
33-## Notes:
34-
35-I need to remmeber this to make an opencode workflow command later:
36-
37-```
38-Follow the plan, create todo list first. Stop if the anything deviates from the plan.
39-```
35+## Notes
4036
41-I need to make a new make command to:
37+- [ ] Create an OpenCode workflow command to enforce: "Follow the plan, create todo list first. Stop if anything deviates from the plan."
4238
43-- extract username/passwords from current db to a file in the root of the repo.
44-- wipe the current db
45-- import username/passwords from file.
46-- update docs to use this when wiping db
39+- [ ] Add a Make command that:
40+ - extracts username/passwords from the current DB to a root-level file
41+ - wipes the current DB
42+ - imports username/passwords from file
43+ - updates docs to use this when wiping the DB
4744
48-The space molt gameserver and mcp have been updated. Need to check for inconsisyencies.
45+- [ ] Validate MCP and game server updates for inconsistencies.