Unverified50% confidenceFactExact time
tabsh's daemon communicates with the browser frontend via a local port or Unix socket, and all project session states are maintained centrally in this process.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/26/2026
First Seen
Valid until: 1/24/2027
Sources
Related Entities
Related Claims
Unverifiedtabsh uses a small Rust daemon to manage the session lifecycle of all projects and consolidates sessions onto a single kanban board/list.66% similarUnverifiedtabsh's core idea is "sessions around work, not work around sessions," moving coding sessions into browser tabs rather than cramming the browser into the IDE.65% similarUnverifiedThe Host is responsible for reading environment configuration, initializing dependencies, resolving conversation identity before locking, persisting the turn to conversation history, ensuring the trace ends and is exported in a finally block, and wrapping the response envelope needed by the HTTP handler.62% similarUnverifiedSession communication is done through an event stream: the frontend sends user.message events, and the backend listens to the SSE stream and pushes the agent's responses back to the browser in real time.62% similarUnverifiedThe project integrates the Cursor SDK, running a background daemon to synchronize conversation state across multiple Neovim instances and browser views.60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1099550API
curl https://kongchang.com/api/v1/knowledge/claims/1099550MCP
get_claim(id=1099550)