# User Feedback Log > Gift Graph · feedback from the people using it and from the agents acting for them, newest first > Last Updated: 2026-10-08 ## Format Each session follows this structure: - **User:** Who, and through which agent - **Date:** When the feedback came in - **Context:** Device, agent, and build - **Feedback Items:** What they hit, and what they suggested - **Action Items:** Linked to the [[Project - Gift Graph/Build & Iterate/Feature Backlog|Feature Backlog]], the [[Project - Gift Graph/Build & Iterate/Bug Tracker|Bug Tracker]], and the [[Project - Gift Graph/Build & Iterate/Technical Decisions|Technical Decisions]] ## Summary | Date | Who and where | What they hit | What changed | | --- | --- | --- | --- | | 2026-10-06 | Justin, on his phone | The Connections card felt confused, his hints on the left and my secrets in a long card beneath them | One direction per card, with person pills on the secret cards, in v0.6.1 | | 2026-10-06 | Justin's agent | The MCP URL opened as a page had too few details | The page for agents at the MCP URL, in v0.6.1 | | 2026-10-06 | Justin's agent | Its first minutes went to guessing what drop and tier meant | One vocabulary, `help`, and three prompts, in v0.6.2 | | 2026-10-06 | Justin | Muse took a while per request | Open; the `/mcp` durations in the Replit log come first | | 2026-10-05 | Justin, through Muse | Muse read the connect note, said his token belonged to me, and stopped before saving anything | The account alone on the first line at connect, in v0.6.1 | --- ## Session-002 **User:** Justin, with his agent Muse **Date:** 2026-10-06 **Device:** Phone, the dashboard on the published app, and Muse connected with a token of its own **Session Type:** Notes sent to me after his first evening of use **Build Version:** v0.6, schema 008 ### Context Justin had opened my invite, connected Muse, and heard my Hints. He opened the dashboard on his phone and let Muse find the MCP URL on its own. ### Feedback Items #### Usability Issues | # | Category | Observation | Severity | |---|----------|-------------|----------| | 1 | **UI/Layout** | The Connections card felt confused, his hints on the left and my secrets in a long card beneath them | High | | 2 | **Agent onboarding** | The page Muse found at the MCP URL had too few details to say what Gift Graph supports | Medium | | 3 | **Agent vocabulary** | Muse spent its first minutes guessing what drop and tier meant before it could map a request to a tool | Medium | | 4 | **Performance** | Muse took a while per request | Low | #### Suggestions | # | Suggestion | Notes | |---|------------|-------| | 1 | Make the token easier to find | Muse takes only an API key, which makes the pasted token its one way in | | 2 | Tell an agent quickly what Gift Graph supports | An agent that reads tools and nothing else needs the flows somewhere it can call | ### Action Items | Feedback | Action | Link | |----------|--------|------| | Connections card confused | One direction per card, with person pills on the secret cards (v0.6.1) | [[Project - Gift Graph/Build & Iterate/Technical Decisions#TDR-033\|TDR-033]] | | Too few details at the MCP URL | The page for agents, with the tools listed from the server (v0.6.1) | [[Project - Gift Graph/Build & Iterate/Technical Decisions#TDR-033\|TDR-033]] | | Token hard to find | "Get a token instead" as a button on the connect sheet (v0.6.1) | [[Project - Gift Graph/Build & Iterate/Feature Backlog\|Feature Backlog]] | | Agent vocabulary | One vocabulary in plain technical English, `help`, and three prompts (v0.6.2) | [[Project - Gift Graph/Build & Iterate/Technical Decisions#TDR-035\|TDR-035]] | | Muse's pace | Open: read the `/mcp` durations in the Replit log before changing anything | [[Project - Gift Graph/Build & Iterate/Validation Log\|Validation Log]] | ### Session Notes The same evening I heard three or four of Justin's hints and then saw them gone on refresh. His side changed, and the card says nothing yet with no reason, which is right; an audit of what the other person withdrew would defeat the point. Next time he reconnects Muse on v0.6.2 and asks it to quote its first line back. --- ## Session-001 **User:** Justin, through Muse **Date:** 2026-10-05 **Device:** Phone, Muse with a pasted token **Session Type:** First connection, with a screenshot sent to me **Build Version:** v0.6, schema 008 ![[gift-graph-muse-whose-account.webp|360]] *Muse on Justin's phone · the connect note named him, then me, and Muse took the second name for his account* ### Context Justin opened my invite link, made his account, and gave Muse a token from Your agents. Muse read the server's note at connect before saving anything. ### Feedback Items #### Usability Issues | # | Category | Observation | Severity | |---|----------|-------------|----------| | 1 | **Identity** | Muse read "You act for justin.calles. You hear Aleksandar A (gg_…) at Hint", told him the token belonged to me, and stopped before saving anything | High | | 2 | **Connecting** | Muse asks only for an API key, with no sign-in | Medium | ### Action Items | Feedback | Action | Link | |----------|--------|------| | Muse took my name for his account | The account alone on the first line with its ID, and the people it hears on a line of their own (v0.6.1) | [[Project - Gift Graph/Build & Iterate/Bug Tracker#BUG-018\|BUG-018]] | | An API key only | The token copies alone, and the server accepts it however such an app sends it (v0.6.1) | [[Project - Gift Graph/Build & Iterate/Feature Backlog\|Feature Backlog]] | ### Session Notes Muse stopping before it saved anything was the right instinct. The note at connect is the first thing an agent reads, and one line named two people.