Skip to content

Repository files navigation

Sessionless

A serverless control plane that keeps conversations canonical while isolated, pluggable agent workers do the work.

CI License: MIT

MVP in progress. The canonical session core, Telegram path, local WebUI, deterministic worker, and feature-disabled provider adapters are implemented. Cloud WebUI rollout, provider composition, and the attached-worker runtime are the remaining MVP delivery tracks.

Explore the documentation · Run the local stand · See the MVP plan

Sessionless WebUI showing a canonical conversation, its completed assistant response, and ready compute capacity

The implemented WebUI running against the repository's deterministic local fixture. No cloud account, provider credential, or private user data is used.

Sessionless gives every frontend the same conversation and execution truth:

  • an append-only, strictly ordered SessionEvent stream;
  • tenant-scoped sessions, bindings, objects, quotas, and worker authority;
  • durable, replay-safe scheduling and delivery across at-least-once queues;
  • isolated harness adapters that cannot redefine the domain model;
  • a local stand that proves the Telegram-to-worker-to-Telegram path end to end.

How it fits together

flowchart TD
    Frontends["Telegram or WebUI"]
    Control["Sessionless control plane"]
    State["Canonical sessions and objects"]
    Worker["Isolated worker and harness"]
    Provider["Authorized AI provider"]

    Frontends -->|"canonical user event"| Control
    Control -->|"atomic event and run"| State
    State -->|"fenced dispatch"| Worker
    Worker -->|"attested invocation"| Provider
    Provider -->|"bounded result"| Worker
    Worker -->|"canonical assistant event"| State
    State -->|"authorized projection"| Frontends
Loading

The control plane owns identity, ordering, authorization, quotas, and durable state. Workers receive only invocation-scoped capabilities. Frontend adapters project canonical events without becoming an alternate source of truth.

Try the complete local path

The local stand uses pinned YDB Local, MinIO, ElasticMQ, a Telegram fixture, and the production Go boundaries. It does not need cloud, Telegram, or AI-provider credentials.

make tools
make dev-up
make e2e-local
make dev-down

make dev-down preserves local data. Read the local stand runbook before using the separate, explicitly confirmed reset command.

Delivery status

Track Status Evidence and next boundary
Canonical core and Telegram Implemented Ordered sessions/events, YDB state, durable ingress/delivery, deterministic two-tenant E2E; tracked by MVP epic #6.
WebUI Implemented locally Authenticated Go BFF, canonical API, and Svelte UI are complete; cloud deployment and tenant-isolation E2E remain in WebUI epic #29.
Provider and serverless harness Experimental, feature-disabled Immutable contracts, conformance fixtures, credential lifecycle, isolation/egress boundaries, and Codex/Pi/OpenCode adapters exist; composition and credentialed cloud E2E remain in provider epic #13.
Attached workers Protocol foundation implemented Owner-scoped identity and capability conformance are complete; transport, fenced dispatch, daemon, UX, and security E2E remain in attached-worker epic #72.
Personal-agent research Planned / post-MVP Memory, tools, web search, subagents, analytics, and federation stay outside the MVP gate until promoted through their research issues.

“Implemented” means code plus repository checks exist. It does not imply a production SLA. “Experimental” paths remain disabled unless their documented release gates and explicit configuration are satisfied.

Find your path

The complete goal-oriented index is in docs/README.md; the component inventory and command map live in docs/components.md.

Contributing and review

Changes are reviewed against deterministic local gates and mirrored exact-SHA GitHub CI. See CONTRIBUTING.md for the development workflow. The security and trust-boundary index routes reviewers to the applicable threat models and contracts.

Sessionless is distributed under the MIT License.

About

Sessionless routes AI requests from Telegram and other frontends to isolated, pluggable agent workers, returning results to the originating conversation. Frontend history provides the primary context, while workloads run safely in separate serverless environments on Yandex Cloud. Mirror from GitCode

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages