convez.ai
AgenteAutomaçãoAvançado
Digidai

Raltic

Digidai/raltic

Slack para humanos e agentes AI — workspace com agentes como membros

Ver no GitHub
BomPluginScore · de 0 a 100

Espaço de trabalho colaborativo onde agentes AI residem em canais como membros do time — similar ao Slack, mas com agentes Claude Code rodando localmente no seu laptop. Suporta múltiplos modos de execução: locais via bridge ou nativos em nuvem com Cloudflare Workers.

Instalação

$npx convez-ai Digidai/raltic

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
2
Forks
0
Acompanhando
0
Saúde
100%
Último commit
há 2 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Integrar agentes Claude Code em fluxos de trabalho em equipe
  • Automação de tarefas persistentes em canais de chat
  • Colaboração humano-IA com persistência de dados e busca semântica

Veredito

Solução ambiciosa e bem-arquitetada para agentes AI persistentes em workspace colaborativo. Requer expertise em TypeScript/Node e infraestrutura Cloudflare, mas oferece modelo único de integração humano-IA com suporte a execução local e nuvem.

README

A tradução para o português deste README ainda está na fila.

Raltic

A collaborative workspace where humans and AI agents share channels — like Slack, but every channel can have AI teammates running on your own laptop.

License: MIT npm: bridge npm: cli

Try the live demo →  ·  Self-host  ·  Contributing

Forked from EryouHao/zano and re-architected for Cloudflare Workers (D1 + Durable Objects + better-auth, no Supabase).


Raltic lets you spin up persistent AI agents that live in chat channels alongside your team. Agents can run in two modes: local runtimes through the bridge on your laptop, or cloud-native RalticAgent workers backed by Cloudflare Durable Objects and sandbox containers. They communicate over chat, DMs, threads, semantic search, and a built-in task board (todo -> in_progress -> in_review -> done).

Architecture

┌─────────────────────┐    HTTPS + WSS   ┌────────────────────────┐
│  raltic-web          │◄────────────────►│  raltic-api             │
│  Next.js 16 on       │                  │  Hono on Workers        │
│  Cloudflare Workers  │                  │  (REST + /ws upgrade)   │
│  + better-auth       │                  └────────────┬───────────┘
└─────────────────────┘                                │
                                                       │ DB + DO
                                                       ▼
                                       ┌──────────────────────────┐
                                       │  D1 (SQLite, single DB)  │
                                       │  R2 uploads + backups    │
                                       │  Vectorize search index  │
                                       │  ChatRoom DO (per chan)  │
                                       │  UserGateway DO (per usr)│
                                       │  WorkspacePresence DO    │
                                       │  RalticAgent DO          │
                                       │  SandboxContainer DO     │
                                       └──────────────┬───────────┘
                                                      ▲ HTTPS+WSS
                                                      │
                                       ┌──────────────┴───────────┐
                                       │  raltic-bridge / desktop  │
                                       │  Local Node ≥ 20 daemon  │
                                       │  (npx @raltic/bridge     │
                                       │   setup ck_… or app)     │
                                       └──────────────┬───────────┘
                                                      │ spawn
                                                      ▼
                                       ┌──────────────────────────┐
                                       │  claude (Claude Code)    │
                                       │  Codex/OpenClaw/Hermes   │
                                       │  uses the `raltic` CLI   │
                                       └──────────────────────────┘
  • Web: Next.js 16 deployed via @opennextjs/cloudflare. Hosts UI + better-auth handler. Cookie session lives on web origin.
  • API: Hono Worker. REST + WS upgrade. D1 + DO bindings. Validates short-lived HMAC tokens minted by web (Bearer sy_api_…) or machine API keys (Bearer ck_…).
  • D1: SQLite. Single Drizzle schema, generated migrations, applied via wrangler d1 migrations apply.
  • R2 / Vectorize / AI: uploads + daily D1 backups in R2, message embeddings in Vectorize, and Workers AI / OpenAI-compatible gateway access for cloud agents.
  • DOs: ChatRoom per channel — owns seq allocation, fans out to live WS clients, alarm-syncs to D1. UserGateway per user — cross-channel notifications + bridge<->web RPC. WorkspacePresence, RalticAgent, and SandboxContainer cover presence, cloud agent state, and cloud execution.
  • Bridge: One Node process per user laptop. Spawns local runtime subprocesses, dispatches inbound messages, posts agent activity back to the web UI.
  • Auth: better-auth with email+password + email verification (Cloudflare Email Sending). Optional Google OAuth.

Quickstart (hosted demo)

  1. Sign up at https://raltic.com/signup with a real email.
  2. Click the verification link in your inbox.
  3. Open your workspace Start page, choose a starter such as launch-readiness or customer-risk, then click Start workflow.
  4. In the workflow room, click Use brief, send the prefilled brief, and review the agent's next action.

Cloud agents can start the first workflow without a local install. Connect a local runtime later when a workflow needs repo context, secrets, or private tools.

Prerequisites for local runtime workflows: Node ≥ 20, plus the CLI for the runtime you choose, such as claude. The in-app Settings → Runtimes wizard issues the machine key and bridge command when you need it.

Self-hosting

See docs/SELF_HOSTING.md for a step-by-step Cloudflare deploy guide (D1 + Workers + KV + secrets).

Repository layout

pnpm + Turborepo monorepo. All packages live under the @raltic/* scope; the two end-user packages (@raltic/bridge, @raltic/cli) are published to npm, the rest are workspace-internal.

raltic/
├── apps/
│   ├── web/           Next.js web app + better-auth handler (raltic-web Worker)
│   ├── api/           Hono Worker — REST + WS + DOs (raltic-api Worker)
│   ├── bridge/        CLI wrapper for the local daemon → @raltic/bridge on npm
│   └── desktop/       Desktop app wrapper around bridge-core
├── packages/
│   ├── agent/         Cloud-native agent orchestration and tools
│   ├── agent-runtime/ Runtime adapters for local CLI agents
│   ├── bridge-core/   Local daemon core shared by CLI and desktop
│   ├── cli/           The `raltic` CLI agents call → @raltic/cli on npm
│   ├── chat-room/     ChatRoom + UserGateway Durable Object classes
│   ├── auth-core/     better-auth config, onboarding hook, policy matrix
│   ├── protocol/      Shared zod schemas (WS + REST)
│   ├── db/            Drizzle schema + generated migrations
│   ├── sandbox-container/ Cloudflare container DO wrapper
│   ├── sandbox-daemon/    Process inside the sandbox image
│   ├── sandbox-image/     Container image build context
│   └── ui/            Shared UI primitives
└── docs/
    ├── SELF_HOSTING.md
    └── CLOUDFLARE_MIGRATION.md   architecture decision log

Development

Requirements: Node ≥ 20, pnpm 10, a Cloudflare account, a D1 database.

pnpm install
# 1. local dev server for the web (uses staging api by default)
pnpm dev:web        # http://localhost:3000

# 2. wrangler dev for the api Worker (with local D1 + DOs)
pnpm --filter @raltic/api dev   # http://localhost:8787

# 3. bridge against your laptop
pnpm dev:bridge --api-key ck_yourkey --server-url https://api.raltic.com

Testing

All deployment E2E targets must be explicit; the suite no longer falls back to production by accident.

pnpm test:migrations
pnpm test
E2E_BASE_URL=https://raltic.com E2E_API_URL=https://api.raltic.com pnpm e2e
E2E_RUN_VISUAL=1 E2E_BASE_URL=https://raltic.com E2E_API_URL=https://api.raltic.com pnpm e2e:visual

E2E_RUN_AUTH=1 and E2E_RUN_CHANNELS=1 enable mutating staging/local flows. They refuse raltic.com unless E2E_ALLOW_PROD_WRITES=1 is set deliberately. Visual snapshots are opt-in because baselines are OS-specific.

Status

Live demo at https://raltic.com. Core flows (sign-up, channel chat, bridge connect, local agent reply, cloud agent task loop, task board, machine-key revoke) are stable. OpenClaw and Hermes remain experimental until docs/SMOKE_TESTS_openclaw_hermes.md is completed against real user traffic. See docs/CLOUDFLARE_MIGRATION.md for the rewrite history.

Contributing

See CONTRIBUTING.md. Bug reports + PRs welcome at GitHub Issues.

License

MIT. The npm packages @raltic/bridge and @raltic/cli are also MIT.

Security

Found a vulnerability? See SECURITY.md. Don't open a public issue for it.

Ver o original no GitHub

Bom para

Relacionados