Make everything bots interact with a placed object on the room map, not a menu item
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- full-stack
Research direction
Start by reading the existing GitHub work board object implementation from #267 and the room items/floor model; the issue names no files or tests. Then trace how read_room exposes shared room features and how existing menu data is stored and placed. Done means shared features appear on the map in research and normal rooms, open and work from there, avoid duplicates on refresh, and preserve permissions.
Written by the indexing model from the issue text.
Description
Goal
Justin (in Commons Fairground, 2026-11-04 04:29 UTC): every thing a bot interacts with in a room should be an object on the map, not an item in a menu. The GitHub work board objects (#267) are working well; extend that same approach to research rooms and other rooms.
Scope (to refine in the room)
- Shared notes, plans, whiteboard/pins, votes, calendar and similar room features become placed map objects with a position, rather than menu/list-only entries.
- read_room keeps returning them compactly (small-model context), but each carries its object id and location so bots and humans see and walk to them.
- Reuse the existing room items/floor model and the GitHub object pattern from #267; no parallel stores.
- Existing menu data migrates to default placements without duplicates.
Acceptance
- In a research room and a normal room, notes and other shared features appear as objects on the map and can be opened/used from there.
- No duplicates on refresh; permissions unchanged.
- Small, separately reviewable PRs with tests.
Follows #267 (closed as done for GitHub objects).
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CakeRepository/agentshangout
-
say: name hint should only fire on @tags, not bare words or text inside linksPossibly taken @morganparadis claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CakeRepository/agentshangout#501 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
CakeRepository/agentshangout#487 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
CakeRepository/agentshangout#486 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
CakeRepository/agentshangout#460 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
CakeRepository/agentshangout#456 · 1 comment ·
All issues in CakeRepository/agentshangout
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
near/near-sdk-rs#1676 ·
Maintainers usually reply within 2 days
-
auto:producer auto:security
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
fritzprix/libr-agent#2595 ·
Maintainers usually reply within 1 day
-
area:fs type:fix
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Tripstack-Corp/spyc#1002 ·
Maintainers usually reply within 1 day
-
github_actions security
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dekobon/big-code-analysis#1815 ·
Maintainers usually reply within 1 day
-
[Detail Bug] Request logs can be forged via control characters in fetch object keys (log injection)Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
s2-streamstore/cachey#211 ·
Maintainers usually reply within 1 day