@@ -1,30 +1,34 @@
11 # KNOWN ISSUES:
22
3-These are the currently know issues to investigate:
3+These are the currently known issues to investigate:
44
5-- [ ] Myses have trouble login in, and mostly resort to new accoutns. We need to create a new table for username/password pairs available to the swarm, and which ones are in use or not. the introduce a new zoea tool to getch this data. Revise the prompt to ensure we encorage re-using swarm acounts first, and only create new ones as a fallback. If a mysis attempts to login to an active account, provide an directive response "use these available details" or "register a new one"
5+## Authentication & Account Management
6+
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+
9+- [ ] 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.
10+
11+## Context & Memory Management
612
713 - [ ] 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.
814
9-- [ ] Mysis prompt review: Encorage myses to collaborate together via zoea tooling and create a goal and colaborate towards it. Encourage to pick a Crustacian Cosmos + Zoea/Mysis themed username. Critical rules must be in every prompt, not only the first one.
15+## Prompt & Behavior
16+
17+- [ ] Mysis prompt review: Encourage myses to collaborate together via zoea tooling and 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.
1018
11-- [ ] 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.
12- **BUG**: 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.
19+- [ ] 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.
1320
14-- [ ] 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.
15- **BUG**: Mysis should continue to act on his tick during travel. They can still use other actions when traveling. Like chatting, or other non traveling actions in the game. Currently the Mysis looses his ticks waiting when he could be using the turns to explore the game api and interacting with the swarm.
21+## Gameplay Issues
1622
17-- [ ] TUI usability issues: Swarm messages list isnot kept up to date. Sending a broadcast doesn't update the list of swarm messages.
18- **BUG**: Breaking change from the spec, the TUI should be high performance and in sync with the data at all times. When a message is sent by the commander, we need a "sending message state" with animation until the commander can send a new message. Stay consistent with zoea theme. check documentation for design rules.
23+- [ ] 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 …
1924
20-- [ ] Broadcast messages are labelled YOU in focus view. We don't differentiate between swam broadcast senders. We need to start tracking it and reflecting it in the UI, in a consistent formatting and style acording to our thematic and design rules (see the documentation before doing changes)
25+## TUI Issues
2126
22-- [ ] 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 else where.
27+- [ ] Swarm messages list is not kept up to date. Sending a broadcast doesn't update the list of swarm messages. The TUI should be high performance and in sync with the data at all times. When a message is sent by the commander, we need a "sending message state" with animation until the commander can send a new message. Stay consistent with zoea theme. Check documentation for design rules.
2328
24-- [ ] The project shouldn't use emojis at all. Replace emoji usage with unicode accross all files in the project.
29+- [ ] 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).
2530
26-- [ ] Cognitive Looping and Prompt Inefficiency: Myses can get stuck in "cooldown" loops or redundant "waiting" states, consuming tokens every 30 seconds without operational progress.
27- **BUG**: 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.
31+- [ ] 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.
2832
2933 ## Notes: