mosaicstack/stack
1
0
Fork 0
Code Issues 42 Pull Requests Actions Packages Projects Releases 15 Wiki Activity

Tess: Pi-native Mosaic interaction agent and Hermes migration bridge #706

New Issue
Open
opened 2026-07-12 17:41:40 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-07-12 17:41:40 +00:00
Owner
Copy Link

Objective

Build Tess, a long-running Pi-native GPT-5.6 Sol interaction agent complementary to Mos. Tess is Jason’s primary Discord and CLI entry point for Mosaic fleet/Hermes interaction and the migration bridge toward native Mosaic capabilities.

Scope

  • Agent-runtime provider contract for sessions, streaming, messaging, termination, hierarchy, and attachment
  • Pi-native Tess agent profile/service with GPT-5.6 Sol high reasoning
  • Dedicated Discord channel binding and CLI interaction/attach
  • Mosaic fleet and Mos coordination tools
  • Transitional Hermes adapter for sessions, agents, Kanban, skills, memory, tools, and cron
  • Native memory/state/inbox/runtime-contract plugin foundation
  • RBAC, approvals, audit, correlation IDs, observability, and recovery
  • tmux transport now; Matrix/native Mosaic transport behind replaceable adapters

Hard boundaries

  • Mos remains orchestration authority; Tess must not become a competing orchestrator
  • Mosaic is the enterprise AI hub; Hermes is a reference migration adapter, never the platform core
  • Gateway remains the single API surface
  • No secrets in source or durable handoffs
  • PRD and traceable tasks required before implementation

Acceptance gate

A dedicated Discord channel and mosaic tess CLI connect to the same durable Tess session; Tess can inspect/message/attach to fleet sessions, coordinate with Mos, expose approved Hermes capabilities through adapters, survive restart/compaction, and pass independent security/code review plus end-to-end tests.

## Objective Build Tess, a long-running Pi-native GPT-5.6 Sol interaction agent complementary to Mos. Tess is Jason’s primary Discord and CLI entry point for Mosaic fleet/Hermes interaction and the migration bridge toward native Mosaic capabilities. ## Scope - Agent-runtime provider contract for sessions, streaming, messaging, termination, hierarchy, and attachment - Pi-native Tess agent profile/service with GPT-5.6 Sol high reasoning - Dedicated Discord channel binding and CLI interaction/attach - Mosaic fleet and Mos coordination tools - Transitional Hermes adapter for sessions, agents, Kanban, skills, memory, tools, and cron - Native memory/state/inbox/runtime-contract plugin foundation - RBAC, approvals, audit, correlation IDs, observability, and recovery - tmux transport now; Matrix/native Mosaic transport behind replaceable adapters ## Hard boundaries - Mos remains orchestration authority; Tess must not become a competing orchestrator - Mosaic is the enterprise AI hub; Hermes is a reference migration adapter, never the platform core - Gateway remains the single API surface - No secrets in source or durable handoffs - PRD and traceable tasks required before implementation ## Acceptance gate A dedicated Discord channel and `mosaic tess` CLI connect to the same durable Tess session; Tess can inspect/message/attach to fleet sessions, coordinate with Mos, expose approved Hermes capabilities through adapters, survive restart/compaction, and pass independent security/code review plus end-to-end tests.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#706
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?