
What happened
DeploAI CTO Tsuyoshi Sodeyama wired Even G2 glasses to sode-ai, his agent-managing agent, routing voice requests through Slack and reading replies on the lens. He verified the glasses triggered a filing and delegation to a development-operations agent.
Why it matters
It shows requests and replies can be split into separate paths, so a worker can hand off a task by voice and read the short result later on the glasses, rather than waiting on the spot.
What to watch
The article says receiving a delegation and receiving that job's completion report are different, and the latter is still unverified in his test records. He has also not confirmed stable long-running operation.
WHO IT HITSDevelopers and R&D engineers building agent workflows onto wearables will care most, since the write-up is an implementation log rather than a finished product. Teams that already run approvals inside Slack likely see the Slack-as-identity-and-permission route as the reusable part.
Summaries like this, in your inbox every morning.
The write-up is an engineering log from DeploAI, where Sodeyama serves as representative director and CTO and builds systems that hand work to AI agents and route it to the right owner. In that setup, several role-bearing agents split the work, and sode-ai is the agent that manages the group — you talk to it, and it takes investigation, development or document tasks and lets you check status.
The interesting part is not the glasses themselves but where the design ran into trouble. Agent work takes longer than a glasses response screen can wait, so the relay was split into an intake step that returns an acknowledgment and a later delivery step that fetches Slack thread replies for the glasses app. The Slack route exists because sode-ai's authorization assumes the request comes from the user, and the author notes that posting with a user token still carried bot attributes, so posting went through Slack MCP so sode-ai would treat it as the person's own request — a result he limits to this posting route and gateway setup.
A second gap was between receiving a reply in the background and actually updating the lens. The author added fallbacks from textContainerUpgrade to rebuildPageContainer to createStartUpPageContainer, after which he confirmed on the device that he could see a reply with another app open on the phone. Whether this becomes a daily-use entry point seems to hinge on the pieces left unverified, chiefly receiving a delegated job's completion report on the glasses and stable operation over long periods.
For example, today's edition would include:
AI-summarized, only the topics you pick: one digest a day via Email, LINE, or Slack.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.