cynarAI a35e431d1c
feat: main agent with a main conversation, user model and delegation (#101)
* feat(db): main agent, main conversation, user model and delegated task foundation

The product needs one main agent that leads a main conversation, knows the
user across spaces, and hands work to visible specialists. Today none of
that exists in the data model: "Chief" is a client-side naming convention,
the "Hauptthread" is a group the web client creates by name, and nothing
stores what the agents know about the user.

This adds the shared foundation the Phase 1 features build on:

- Bot.kind ("main" | "specialist", one main bot per user) plus capability
  fields (tags, builtin tool allowlist, model tier).
- ChatGroup.kind ("group" | "main", one main conversation per user) and
  ChatGroup.leadBotId.
- UserProfile and UserFact with category, confidence, source, consent
  status and per-space visibility; embeddings are stored as float arrays
  because none of the Postgres images ship pgvector.
- DelegatedTask for work the main bot hands to a specialist.
- SpaceModelTier to map a model tier to a connected model per space.

The migration backfills each user's onboarding bot in the home space as the
main bot and turns an existing "Hauptthread" group containing it into the
main conversation. CHECK and foreign key constraints on existing tables are
added NOT VALID and validated in a separate migration, as elsewhere in this
repo.

New db helpers ensure the main bot and the main conversation (idempotent and
race-safe, repairing a lost lead), add same-space specialists to the main
conversation and announce it with a group.updated event, and load the user
context a run may see. The main conversation is exempt from the two-member
floor and cannot have its members replaced through a group update. The
contracts expose the new fields and the user model and delegated task
schemas.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* feat(adapters): every run knows who it is and who the user is, in the user's time zone

Runs dropped the bot's name, title and description whenever custom
instructions existed, always stated the time in UTC, and knew the user only
through free-form durable memory. Groups with a lead, like the main
conversation, still got the peer-group lines that forbid handing work back.
And every group follow-up run failed during setup: the inbound handoff lookup
selected a `bot` relation that Message does not have, which Prisma rejects.

- Instructions now open with the bot's identity, then its own instructions,
  a main-agent role paragraph for the main bot, the current time in the
  user's time zone with its offset (UTC when unknown), and a `<user>` block
  built from loadUserContext: profile fields and the active facts visible in
  the run's space, escaped, clipped and framed as data rather than
  instructions. Runs that reply in a shared messaging channel get only the
  name, zone, locale, language and style, matching how those runs already
  leave out durable memory.
- run_subagent helpers receive the identity, time and user block through a
  new optional AgentRunRequest.subagentContext instead of nothing.
- Groups with an active lead get lead and specialist lines and matching
  inbound handoff instructions. Members may hand a stage back to the lead and
  the lead may delegate the next stage; the bounce rules still apply between
  members. Ordinary groups keep today's lines.
- The teammate directory is rendered only when the run has message_bot, which
  group runs never have, and tool guidance names a tool only when the run has
  it.
- The auto-review judge, history compaction and the team chat judge read the
  time in the user's zone, and schedule_create defaults to it.
- The inbound handoff sender is read from the handoff block and looked up
  among the user's bots; a Postgres test covers the follow-up run, the prompt
  it receives, and handing the result back to the lead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* feat(memory): learn the user profile from conversations; add built-in semantic memory

Why: the user profile only knew what onboarding wrote, so people had to repeat themselves,
and semantic recall needed a hosted or separately run memory service. The profile now grows
from everyday conversations, and recall can run on the user's own server with a local
embeddings endpoint (for example llama.cpp). Both stay optional and are tested offline.

What:
- adapter-kit: EmbeddingProvider contract (describe, embed) and the profile.consolidate job
  (payload schema and a replace-keyed job factory, one pending job per user).
- adapters: OpenAI-compatible embeddings (POST {baseUrl}/embeddings through the guarded
  OpenAI-compatible fetch, batching, bounded responses, clear errors), a deterministic
  emulator, an in-process /v1/embeddings server emulator, and a shared conformance suite.
- adapters: "builtin" semantic memory stored in Postgres (semantic_memory_items with Float[]
  embeddings, cosine ranking in process, bot/shared/history scopes matching the existing
  providers), registered in the memory provider factory and configured through
  memory.connectProvider with an embeddings URL, model and optional API key. Private
  endpoints require the deployment owner, like the other local memory providers.
- adapters: profile consolidation reads the user's settled app conversations since
  UserProfile.consolidatedAt (never messaging channels), asks the main bot's model for strict
  JSON facts and an updated summary, drops restatements (embedding cosine when built-in
  memory is configured, normalized text otherwise), stores sensitive categories as pending,
  and advances the cursor with a compare-and-set. A reconciler hook enqueues it at most daily
  per active user; it skips under the scripted runtime and without a usable model.
- db: additive migration 20261002210400_ws4_semantic_memory.
- web: a "Built-in" option in Memory settings; AI data sharing names the embeddings server.

Tests: new embedding conformance, OpenAI-compatible wire, built-in provider and consolidation
unit tests; new Postgres suites for built-in memory (including a real loopback embeddings
server through the memory provider resolver) and for consolidation and its scheduling query,
both added to the integration harness. The settings E2E spec now opens the new form.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* feat(models): map model tiers per space and let bots and helpers ask for one

A space can now map the tiers fast, standard and code to connected models,
including several models served by one OpenAI-compatible router endpoint
(one credential, many model ids). A bot can ask for a tier, and a single
run_subagent call can ask for one. A tier with no model mapped falls back
to the usual model choice, so nothing breaks before tiers are set up.

- db: SpaceModelTier repo (list, find, set or clear); tier mappings are
  copied into a new space like model and voice preferences; createBot
  carries a tier, so duplicates keep it and spawned bots inherit it.
- contracts/api: models.tiers.list and models.tiers.set;
  models.probeOpenAiCompatible can list a connected server's models by
  credential id with its stored address and key; bots.update accepts
  modelTier and keeps a pinned model and a tier mutually exclusive, so a
  model picked on a surface that knows no tiers (mobile) is never silently
  overridden. Thinking-level validation follows the tier's model. AI
  consent status discloses tier models; desktop local settings allow the
  tier procedures.
- adapters: selectConfiguredModel runs a mapped tier ahead of the pinned
  model and the space default; the executor resolves bot tiers for runs
  and model lookups, and helper tiers through resolveModelTier.
  run_subagent takes model_tier; an explicit model wins over it.
- web: a collapsed Tiers section in model settings (shown once a model is
  connected) and mapped tiers as choices in the bot Model select.
- docs: tiers in self-host model setup.
- tests: resolution order and fallbacks (selection, executor, Pi helper),
  repo, API and contract units, authorization and offline Pi Postgres
  suites, and a model-tiers web E2E spec.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* fix(adapters): state the consolidation time in the user's zone; name the memory migration after its content

Profile consolidation now passes the profile's time zone to the shared time
instruction, which takes the zone since every run states the time in the
user's zone. The semantic memory migration is renamed after what it creates.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* fix(adapters): keep the user's summary and facts out of replies to other owners' agents

An agent connection wakes a bot with another owner's message, and the reply
goes back to that owner. Such runs now get only the basics of the user block
(name, time zone, locale, language, style), like runs in shared messaging
channels, so confirmed facts such as health never reach another person's
agent.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* feat(profile): readable, writable and forgettable user model

The main agent is meant to know the user, but nothing could read or change
the user model the foundation added. Onboarding pasted the user's answers
into the first bot's instructions as a "User Context" block, and the user
had no way to see or remove what their bots knew about them.

This makes the user model a user-controlled resource:

- db: a profile repository scoped by user. One atomic update writes the
  account name, profile fields, new facts (deduplicated by normalized
  text, capped per user), fact edits including per-space visibility, and
  confirmations. Health and values facts wait for confirmation unless the
  user wrote them. Forgetting hard-deletes facts by id, category or all,
  clears the summary that may restate them and marks earlier chats as
  consolidated so they cannot teach them again; forgetting everything also
  clears the profile fields. Writes take a per-user advisory lock.
- api/contracts: profile.get, profile.update and profile.forget. Unknown
  fact ids are a 404 on update and ignored on forget; spaces outside the
  user's memberships are rejected.
- adapters: an update_user_profile tool for the main bot only, hidden from
  specialists and shared messaging channels and refused if called anyway.
  Facts carry source "conversation" and the bot, thread and message they
  came from. The scripted runtime records "learn about me: [category:]
  statement" for tests.
- web: onboarding writes the name, time zone (browser default, now
  prefilled and editable), locale, chosen language, communication style
  and the hobby and work-style answers to the profile instead of
  overwriting the bot's instructions, and the harvested memory section no
  longer repeats them. A new "About you" settings section lists profile
  fields and facts by category with their origin, confirms pending facts,
  and forgets one fact or everything.

Tests cover the contracts, the repository (unit and PostgreSQL), tool
selection and refusal, the scripted trigger, the onboarding mapping and
view helpers, an API suite that runs the tool through the executor with a
real main bot, authorization for the new procedures, and an E2E spec.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* feat(delegation): main bot hands work to specialists as tracked tasks

The main agent had no way to give a specialist a piece of work and keep
track of it. message_bot is a fire-and-forget peer message whose work stays
hidden from the user, and handoff_to_bot ends the main bot's turn and only
works between members of one group. Delegation now runs the specialist's
work where the user follows the main agent and brings the result back so
the main agent can close the task.

- delegate_task({bot, title, brief, deadline?}) is offered to the main bot
  only and refused unless the caller leads the main conversation. It
  resolves the specialist by id or name across the user's spaces, creates a
  DelegatedTask and posts a task card in the main conversation.
- A specialist from the main conversation's space joins it and works there
  in a run with the new trigger "delegation", which the peer filters do not
  hide, so its progress, asks and approvals appear in the main conversation
  with the specialist as sender. A specialist from another space works in
  its own chat; its written result is posted into the main conversation as
  its message.
- The executor mirrors the run on its task (running, waiting, done, failed,
  cancelled) after the run starts and when each attempt ends, and updates
  the card in place through thread.message.updated. Done and failed tasks
  wake the main bot in the main conversation with the result. The job
  reconciler settles tasks whose run ended without the executor (stop,
  clear, archive, deletion, crash).
- tasks.list({threadId?, status?}) returns the caller's tasks for the
  current space.
- The task card shows who, what and status with Lingui labels; the brief
  opens on demand. The message_bot card no longer shows the recipient's
  unrelated overall status or hard-coded German copy.
- The scripted runtime understands "delegate to the bot named X: ..." and
  the task wake prompt; activity rows name delegation runs by task title.

Tests: unit tests for the prompts, status mapping, card, reducer, tool
selection and scripted runtime; a Postgres suite for same-space, group,
other-space, ask and answer, failure, stop and replay; tasks.list in the
authorization suite; and an end-to-end spec for the whole flow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* fix(adapters): show the main agent the specialists it can delegate to

The main conversation is a group run, and group runs no longer list the
teammate directory, so the main agent could not see the names of the
specialists delegate_task expects. Runs that have delegate_task now list
the user's specialists across the spaces they belong to, those next to the
conversation first and others marked with their space, and that list
replaces the teammate directory so no bot appears twice. It also says when
to prefer delegate_task over handoff_to_bot.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* feat(inbox): show what specialists need from the user in the main conversation

Specialists ask questions, request approvals and the computer screen in
their own threads, and the user only finds out by opening each thread. With
the main conversation as the single entry point, those requests have to
reach the user there, with the specialist as the visible sender.

- inbox.list returns, for the current space and the user's own bots, pending
  asks and approvals (bot messages with a pending ask block whose run waits
  for input), takeover requests, and unread specialist threads. Asks already
  in the main conversation are left out; takeovers stay because their
  controls live in the bot's own thread. Each item carries the bot, the
  thread target, run and message ids, and the ask block for asks and
  approvals.
- The main conversation shows the items above the composer. Asks and
  approvals are answered in place through threads.answer with the source
  thread target; takeovers and unread threads open the bot's thread. The
  list refreshes when the bots' status, unread state or newest message
  changes, every 15 seconds, and after an answer.
- The inbox shrinks and scrolls so it never pushes the composer out of view.
  The transcript now clips its scroller: with no room left in the column,
  the scroller's padding used to spill over whatever sat below it.
- The ask block schema is extracted from MessageBlock so the inbox contract
  reuses it, and AskCard accepts a className.

Tests: unit tests for the item builder and the component, a Postgres suite
for the query (added to the harness list), inbox cases in the authorization
suite, and an E2E spec in which a specialist asks in its own thread and the
user answers from the main conversation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* fix(adapters): write learned facts under the profile's lock and limit

Profile consolidation wrote facts beside the user profile repository: without
its per-user lock, its duplicate check at write time, or its limit of 500
facts. A long-running profile could grow past the limit and then refuse the
user's own additions. Consolidation now takes the same lock, drops facts the
profile gained since the run read it, and keeps only what still fits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* fix(adapters): keep profile writes out of replies to other owners' agents

A run woken over an agent connection hears another owner's bot, not the
user, so update_user_profile is withheld there: nothing such a conversation
says can become a fact about the user. Detection moves ahead of tool
selection; the reduced user block uses the same flag.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* feat(capabilities): least-privilege builtin tools per bot and schedules on behalf

Every bot saw every builtin tool, and nothing outside the runtime's own
declaration kept a run to the tools it was given: the executor ran any tool a
runtime asked for, and the Pi runtime exposed all builtins whenever a caller
passed an empty tool list, which the safety checker, the history summarizer
and the team chat judge do on purpose. A specialist could not be kept to the
tools of its lane, bots had no capability tags, and the main bot could only
schedule routines for itself.

- A bot can carry a builtin tool allowlist. Its runs see only the allowlisted
  builtins, and an empty allowlist means none. MAIN_ONLY_BUILTIN_TOOLS (empty
  until the user profile and delegation tools land) never reach other bots.
  applyTool refuses any tool the run did not expose, and an empty tool list
  now means no tools for the Pi runtime and its subagents.
- A bot spawned by a restricted bot inherits the restriction and a duplicate
  keeps it, so neither path widens a bot's tools.
- bots.create and bots.update accept tags, restrictBuiltinTools and
  allowedBuiltinTools; the router rejects names that are not builtin tools.
  bots.builtinTools lists the names a bot's allowlist can use.
- Bot settings get a Tags field and a switch with a tool checklist under
  Advanced.
- The main bot's schedule_create takes an optional bot: one of the user's
  bots in any space the user still belongs to. The routine belongs to that
  bot in its space and wakes in the main conversation when the bot is a
  member there, otherwise in its 1:1 thread. Routines record the bot that
  scheduled them (additive migration), so schedule_list and schedule_cancel
  also cover exactly the routines a bot scheduled for others. Cancelling by
  a name that matches several routines is refused.

Tested with unit tests for the per-bot filter, the applyTool guard, the empty
tool list, and on-behalf resolution, creation, listing and cancelling; with
Postgres journeys for on-behalf routines waking across spaces and in the main
conversation and for allowlist enforcement through the scripted runtime; and
with a web E2E for the settings section.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* test(adapters): give the consolidation unit tests the profile lock

The write transaction now takes the per-user profile lock, so the mocked
client answers the lock query, and the first case checks the lock is taken.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* feat(adapters): run profile consolidation on the fast tier when one is mapped

Fact extraction is short structured work, so consolidation asks the model
resolver for the fast tier. The resolver takes a per-call tier and, when the
space has not mapped it, keeps the bot's own tier or model as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

* feat: land in the main conversation, led by the main bot

After onboarding the user ended up in a 1:1 chat with "Chief", and the
"Hauptthread" was a group the web client created and found by name. The
main bot had no conversation it actually led, and addressing another bot
there did nothing unless the user had added it as a member first.

Now the main conversation is a real place:

- bots.ensureMain creates or returns the main bot. Bootstrap and space
  navigation return `main` ({ botId, groupId, spaceId }) once the main
  bot exists; reading navigation never creates a bot.
- The main bot leads the main conversation and answers when nobody is
  addressed: message routing, follow-ups, reactions and clearing the
  thread fall back to the group's lead instead of its first member.
- Addressing a same-space bot that is not a member yet, by @Name or a
  mention chip, makes it join before the message is routed, so it
  answers in the conversation. Specialists from other spaces do not join.
- The main bot cannot be archived or deleted, the main conversation
  cannot be archived or deleted or have its members edited, and child
  bots never dissolve it. Renaming the main bot renames the conversation.
- Web: onboarding uses bots.ensureMain and finishes in the main
  conversation. The main conversation is the first sidebar entry in every
  space, shown with the main bot's avatar and name; from another space it
  switches back to the home space. The main bot is not listed again among
  the bots, its 1:1 thread stays reachable by URL. The client no longer
  creates or detects the "Hauptthread" by name, refetches a group when it
  changes, and shows the speaker of any of the user's bots in a group.
- Onboarding no longer resets the step when its bootstrap resolves after
  the user has already moved on, and new spaces open in the app instead
  of walking onboarding again.

Tests: group mention routing with a default responder, lead follow-ups,
child-bot guards, a journey for the main conversation (lead answers,
addressed bot joins, guards, rename), authorization for bots.ensureMain,
and an E2E spec that lands in the main conversation, gets an answer from
the lead, sees an addressed bot join, and reaches the conversation from
another space. Existing E2E specs start in the main bot's thread through
a helper or use the main conversation where that is what they test.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u

---------

Co-authored-by: cynarAI <cynarAI@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-03 06:44:20 +02:00

1016 lines
35 KiB
TypeScript

import { randomUUID } from "node:crypto";
import { rm } from "node:fs/promises";
import { ORPCError, onError } from "@orpc/server";
import { RPCHandler } from "@orpc/server/fetch";
import type {
AgentRuntime,
JobPublisher,
ManagedConnectorProvider,
MessagingSurface,
RealtimeFanout,
SandboxProvider,
TransactionalEmailProvider,
} from "@rakazo/adapter-kit";
import type {
ComposioProvider,
ConnectorRegistry,
DestinationEmulator,
RemoteConnectorDependencies,
} from "@rakazo/adapters";
import {
applyMessagingOutboundStatus,
ChatSdkMessagingSurface,
ComposioConnector,
createBackgroundJobHandlers,
createCloudAgentConnection,
createConnectorStack,
createJobReconciler,
createMessagingContextLoader,
createMessagingTeamChatSender,
createProfileConsolidationScheduler,
createRunExecutor,
createRunSandbox,
createRunSecretWriter,
createWebProvider,
destroyBot,
EmailEmulator,
EncryptedSecretStore,
ExpoPushProvider,
GraphileJobPublisher,
GraphileJobWorkerHost,
InMemoryJobQueue,
InMemoryRealtimeFanout,
InstalledConnectorProvider,
IntegrationProviderSettings,
isComposioEnabled,
isMessagingSurfaceEnabled,
isPipedreamEnabled,
LocalAgentHomeStore,
LocalArtifactStore,
McpConnector,
McpOAuthBroker,
messagingPlatformsFromEnv,
PiAgentRuntime,
PiOAuthLogins,
PipedreamConnector,
PostgresRealtimeFanout,
pipedreamConfigFromEnv,
piSessionsRoot,
pushTokenPath,
reconcileCloudAgents,
reconcileComputerUpdates,
reconcileDelegatedTasks,
removePiUserSessions,
ScriptedAgentRuntime,
SmtpEmailProvider,
SpaceMemoryProviderResolver,
toTeamChatInbound,
} from "@rakazo/adapters";
import { blockedAuthPaths, createAuth } from "@rakazo/auth";
import { signupPolicyFromEnv } from "@rakazo/core";
import type { Pool, PrismaClient } from "@rakazo/db";
import {
createDb,
createPool,
createThreadEvents,
parsePositiveInteger,
provisionMessagingIdentity,
requireMembership,
} from "@rakazo/db";
import type { Logger } from "@rakazo/logging";
import {
createServiceLogger,
enrichLogContext,
getLogger,
installLogger,
SERVICE_NAMES,
} from "@rakazo/logging";
import { requestLogging } from "@rakazo/logging/hono";
import { MarkdownMemoryStore } from "@rakazo/memory";
import { Hono } from "hono";
import { cors } from "hono/cors";
import type { AppEnv } from "./env.js";
import { loadEnv } from "./env.js";
import { mountLocalSettings } from "./local-settings.js";
import {
createMessagingInboundHandler,
teamChatSenderCanWakeMessageRoutines,
wakeMessageRoutines,
} from "./messaging-inbound.js";
import { mountMessagingWebhookRoutes } from "./messaging-webhook.js";
import { mountApiRequestBodyLimits } from "./request-body-limit.js";
import { createRouter } from "./router.js";
import { mountScreenTarget } from "./screen-proxy.js";
import { isDeferredReservationLost, TeamChatBridge } from "./team-chat-bridge.js";
import { ModelTeamChatEngagementJudge } from "./team-chat-judge.js";
import {
PendingTeamChatInbound,
prefersTeamChatSurface,
settleWithTimeout,
TEAM_CHAT_STARTUP_SHUTDOWN_MS,
} from "./team-chat-startup.js";
import { mountTradingBotStatus } from "./trading-bot-proxy.js";
import { mountVoiceHttpRoutes } from "./voice.js";
import { mountWebhookHttpRoutes } from "./webhook.js";
export interface AppHandles {
app: Hono;
prisma: PrismaClient;
jobs: JobPublisher;
sandbox: SandboxProvider;
connector: DestinationEmulator;
composio?: ComposioProvider;
connectors: ConnectorRegistry;
messaging?: MessagingSurface;
email?: TransactionalEmailProvider;
executor: ReturnType<typeof createRunExecutor>;
runtime: AgentRuntime;
stop: () => Promise<void>;
}
export async function createApp(
overrides: Partial<AppEnv> & {
prisma?: PrismaClient;
realtime?: RealtimeFanout;
sandbox?: SandboxProvider;
composio?: ComposioProvider;
pipedream?: ManagedConnectorProvider;
messaging?: MessagingSurface;
email?: TransactionalEmailProvider;
remoteConnectors?: RemoteConnectorDependencies;
logger?: Logger;
} = {},
): Promise<AppHandles> {
const {
prisma: prismaOverride,
realtime: realtimeOverride,
sandbox: sandboxOverride,
composio: composioOverride,
pipedream: pipedreamOverride,
messaging: messagingOverride,
email: emailOverride,
remoteConnectors,
logger: loggerOverride,
...envOverrides
} = overrides;
const env = { ...loadEnv(process.env), ...envOverrides };
const logger = loggerOverride ?? createServiceLogger({ service: SERVICE_NAMES.api });
installLogger(logger);
const created = prismaOverride
? { prisma: prismaOverride, pool: undefined }
: createDb(env.databaseUrl, {
poolMax: parsePositiveInteger(process.env.DB_POOL_MAX, 4),
applicationName: "rakazo-api",
});
const { prisma } = created;
const realtime =
realtimeOverride ??
(created.pool
? new PostgresRealtimeFanout({
connectionString: env.realtimeDatabaseUrl,
publisher: created.pool,
})
: new InMemoryRealtimeFanout());
const secrets = new EncryptedSecretStore(env.encryptionKey);
const events = createThreadEvents(prisma, realtime, {
runSecretWriter: createRunSecretWriter(secrets),
});
const environmentSignupPolicy = signupPolicyFromEnv(env);
const deploymentSettings = await prisma.deploymentSettings.upsert({
where: { id: "default" },
create: {
id: "default",
signupsEnabled: environmentSignupPolicy.enabled,
signupAllowlist: environmentSignupPolicy.allowlist.join(","),
signupPolicyInitialized: true,
},
update: {},
});
if (!deploymentSettings.signupPolicyInitialized) {
// Older versions created this row with schema defaults even though auth
// still enforced the environment policy. Copy that effective policy once
// so upgrades preserve behavior before Settings becomes authoritative.
await prisma.deploymentSettings.updateMany({
where: { id: "default", signupPolicyInitialized: false },
data: {
signupsEnabled: environmentSignupPolicy.enabled,
signupAllowlist: environmentSignupPolicy.allowlist.join(","),
signupPolicyInitialized: true,
},
});
}
const jobKind = env.wakeupDriver;
const inMemoryJobs = jobKind === "memory" ? new InMemoryJobQueue() : undefined;
// prismaOverride skips createDb, so there is no shared pool. The previous
// GraphileJobPublisher(databaseUrl) path opened its own connections; keep a
// bounded pool for that override path instead of passing undefined.
let ownedJobPool: Pool | undefined;
if (!inMemoryJobs && !created.pool) {
ownedJobPool = createPool(env.databaseUrl, {
poolMax: parsePositiveInteger(process.env.DB_POOL_MAX, 4),
applicationName: "rakazo-api-jobs",
});
}
const jobPool = created.pool ?? ownedJobPool;
const jobs = inMemoryJobs
? inMemoryJobs
: new GraphileJobPublisher(
jobPool ??
(() => {
throw new Error("Graphile job publisher requires a PostgreSQL pool");
})(),
);
const sandbox: SandboxProvider =
sandboxOverride ??
createRunSandbox(env.sandboxProvider, {
supervisorUrl: env.sandboxSupervisorUrl,
supervisorToken: env.sandboxSupervisorToken,
e2bApiKey: env.e2bApiKey,
daytonaApiKey: env.daytonaApiKey,
daytonaApiUrl: env.daytonaApiUrl,
daytonaTarget: env.daytonaTarget,
boxApiKey: env.boxApiKey,
boxApiUrl: env.boxApiUrl,
dataDir: env.dataDir,
prisma,
});
const mcpOAuth = new McpOAuthBroker(prisma, secrets, remoteConnectors);
const memoryProviders = new SpaceMemoryProviderResolver(prisma, secrets);
const oauthLogins = new PiOAuthLogins();
const home = new LocalAgentHomeStore(env.dataDir);
const artifacts = new LocalArtifactStore(env.dataDir);
const memory = new MarkdownMemoryStore(prisma);
const mcp = new McpConnector(
prisma,
secrets,
{
stdioEnabled: env.mcpStdioEnabled,
allowedCommands: env.mcpStdioAllowedCommands,
network: remoteConnectors,
},
mcpOAuth,
);
const pipedreamConfig = pipedreamConfigFromEnv(env);
const pipedream =
pipedreamOverride ??
(isPipedreamEnabled(pipedreamConfig) ? new PipedreamConnector(pipedreamConfig) : undefined);
// This process registers the inbound sink (messaging.onInbound below),
// so it's the one that must hold Telegram's live getUpdates connection —
// see messagingPlatformsFromEnv's docstring for why a second poller
// elsewhere (e.g. the worker) would actively break this.
const messagingPlatforms = messagingPlatformsFromEnv(env, { pollInboundMessages: true });
const messaging =
messagingOverride ??
(isMessagingSurfaceEnabled(messagingPlatforms, {
deploymentModelKey: env.deploymentModelKey,
openSignup: env.messagingOpenSignup,
})
? new ChatSdkMessagingSurface(messagingPlatforms)
: undefined);
const localEmailEmulator =
!emailOverride && !env.smtpUrl && env.emailEmulator
? new EmailEmulator((message) => {
getLogger().info("email emulator captured message", {
"email.subject": message.subject,
});
})
: undefined;
if (localEmailEmulator && !isLoopbackHost(env.apiHost)) {
throw new Error("EMAIL_EMULATOR requires API_HOST to be a loopback host");
}
const email: TransactionalEmailProvider | undefined =
emailOverride ??
(env.smtpUrl
? new SmtpEmailProvider({ url: env.smtpUrl, from: env.emailFrom ?? "" })
: localEmailEmulator);
const installed = new InstalledConnectorProvider(prisma, secrets, remoteConnectors);
const integrationSettings = new IntegrationProviderSettings(prisma, secrets, env.encryptionKey, {
composio:
composioOverride ??
(isComposioEnabled(env.composioApiKey)
? new ComposioConnector(env.composioApiKey)
: undefined),
pipedream,
});
const stack = createConnectorStack(false, composioOverride, [
installed,
...integrationSettings
.providers()
.filter((provider) => !composioOverride || provider.describe().id !== "composio"),
mcp,
]);
const connector = stack.destination;
await connector.start();
integrationSettings.warmDirectories();
const runtime =
env.agentRuntime === "scripted"
? new ScriptedAgentRuntime()
: new PiAgentRuntime({
sessionRoot: env.piSessionRecording ? piSessionsRoot(env.dataDir) : undefined,
});
const notifications = new ExpoPushProvider(env.dataDir);
const auth = createAuth(prisma, {
secret: env.authSecret,
baseURL: env.authUrl,
webOrigin: env.webOrigin,
signupsEnabled: env.signupsEnabled,
signupAllowlist: env.signupAllowlist,
email,
onEmailError: (error) => getLogger().error("transactional email delivery failed", error),
extraOrigins: [
"rakazo://",
"exp://",
"exp://*",
"http://localhost:8081",
"http://127.0.0.1:8081",
"http://localhost:19006",
"http://127.0.0.1:19006",
"http://*:5173",
"http://*:3100",
"https://*:5173",
"https://*:3100",
"http://192.168.*:*",
"https://192.168.*:*",
"http://100.*:*",
"https://100.*:*",
"http://10.*:*",
"https://10.*:*",
"http://172.*:*",
"https://172.*:*",
"http://*.local:*",
"https://*.local:*",
...(process.env.EXTRA_TRUSTED_ORIGINS?.split(",").map((s) => s.trim()) ?? []),
],
beforeDeleteUser: async (userId) => {
const bots = await prisma.bot.findMany({
where: { userId },
select: { id: true, userId: true, spaceId: true, name: true, archivedAt: true },
});
await Promise.all(
bots.map((bot) =>
destroyBot(
{ prisma, sandbox, home, jobs, artifacts, dataDir: env.dataDir },
bot,
{
operationId: `account-delete:${userId}`,
traceId: `account-delete:${userId}`,
spaceId: bot.spaceId,
userId,
botId: bot.id,
signal: new AbortController().signal,
},
{ deleteMemories: true },
),
),
);
await removePiUserSessions(env.dataDir, userId);
await rm(pushTokenPath(env.dataDir, userId), { force: true }).catch(() => undefined);
},
});
// One provider instance so emulator launches and polls share the same Map.
const cloudAgent = createCloudAgentConnection({
CLOUD_AGENT_PROVIDER: env.cloudAgentProvider,
CURSOR_API_KEY: env.cursorApiKey,
CLOUD_AGENT_SPACE_ID: env.cloudAgentSpaceId,
});
const shutdown = new AbortController();
const executor = createRunExecutor({
prisma,
runtime,
sandbox,
memory,
memoryProviders,
home,
artifacts,
connector: stack.connector,
connectors: stack.connector,
listConnectedPluginSlugs: async (userId) => {
const provider = await integrationSettings.resolve("composio");
if (!provider) return [];
return provider.listConnectedExternalIds({
userId,
spaceId: "",
operationId: "connections.sync",
traceId: "connections.sync",
signal: AbortSignal.timeout(15_000),
});
},
secrets: [
env.deploymentModelKey ?? "",
env.composioApiKey ?? "",
env.cursorApiKey ?? "",
].filter(Boolean),
secretStore: secrets,
secretHttp: remoteConnectors,
deploymentModelKey: env.deploymentModelKey,
dataDir: env.dataDir,
notifications,
jobs,
events,
messaging: messaging ? createMessagingContextLoader(prisma) : undefined,
web: createWebProvider(),
cloudAgent,
shutdownSignal: shutdown.signal,
});
const jobHandlers = createBackgroundJobHandlers({
executor,
prisma,
sandbox,
home,
jobs,
events,
workerId: "api",
runtime,
secretStore: secrets,
memoryProviders,
deploymentModelKey: env.deploymentModelKey,
messaging,
cloudAgent,
});
if (inMemoryJobs) {
await inMemoryJobs.start(jobHandlers);
} else if (jobPool) {
const graphileWorkerHost = new GraphileJobWorkerHost(jobPool, {
concurrency: 4,
pollInterval: 500,
});
await graphileWorkerHost.start(jobHandlers);
}
const reconciler = inMemoryJobs
? createJobReconciler({
prisma,
jobs,
reconcileCloudAgents: () => reconcileCloudAgents({ prisma, jobs, cloudAgent }),
reconcileComputerUpdates: () => reconcileComputerUpdates({ prisma, jobs }),
reconcileProfileConsolidation: createProfileConsolidationScheduler({ prisma, jobs }),
reconcileDelegatedTasks: () => reconcileDelegatedTasks({ prisma, jobs, events }),
})
: undefined;
reconciler?.start();
const router = createRouter({
cloudAgent,
prisma,
events,
auth,
jobs,
sandbox,
memory,
memoryProviders,
home,
secrets,
oauthLogins,
integrationSettings,
mcpOAuth,
composio: stack.composio,
connectors: stack.connector,
remoteConnectors,
artifacts,
dataDir: env.dataDir,
messaging: {
enabled: Boolean(messaging),
providers: messaging?.platforms().map((platform) => platform.provider) ?? [],
openSignup: env.messagingOpenSignup,
},
env: {
agentRuntime: env.agentRuntime,
defaultProvider: env.defaultProvider,
defaultModel: env.defaultModel,
teamChatJudgeProvider: env.teamChatJudgeProvider,
teamChatJudgeModel: env.teamChatJudgeModel,
onboardingScanHome: env.onboardingScanHome,
deploymentModelKey: env.deploymentModelKey,
webOrigin: env.webOrigin,
privacyPolicyUrl: env.privacyPolicyUrl,
screenProxySecret: env.screenProxySecret,
sandboxProvider: env.sandboxProvider,
gitSha: env.gitSha,
updaterUrl: env.updaterUrl,
updaterToken: env.updaterToken,
imageTag: env.imageTag,
integrationsCatalogUrl: env.integrationsCatalogUrl,
},
});
const rpc = new RPCHandler(router, {
clientInterceptors: [onError((error, { path }) => logUnexpectedRpcError(error, path))],
});
const app = new Hono();
app.use("*", requestLogging(logger));
app.use(
"*",
cors({
origin: (origin) => {
if (!origin) return env.webOrigin;
return isTrustedOrigin(origin, env) ? origin : "";
},
credentials: true,
}),
);
// Security headers
app.use("*", async (c, next) => {
await next();
c.res.headers.set(
"Content-Security-Policy",
"default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self'; connect-src 'self' ws:; frame-ancestors 'none'; base-uri 'self'; form-action 'self'",
);
c.res.headers.set("Strict-Transport-Security", "max-age=31536000; includeSubDomains");
c.res.headers.set("X-Frame-Options", "DENY");
c.res.headers.set("X-Content-Type-Options", "nosniff");
c.res.headers.set("Referrer-Policy", "strict-origin-when-cross-origin");
c.res.headers.set(
"Permissions-Policy",
"camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=()",
);
});
app.get("/api/auth/capabilities", (c) =>
c.json({
passwordReset: Boolean(email),
resetUrl: email ? new URL("/reset-password", env.webOrigin).href : null,
}),
);
mountTradingBotStatus(app, {
baseUrl: env.tradingBotUrl,
authorize: async (request) => {
const session = await auth.api.getSession({ headers: sessionHeaders(request) });
return Boolean(session?.user);
},
});
if (localEmailEmulator && env.nodeEnv === "development") {
app.get(
"/api/dev/emails",
() =>
new Response(JSON.stringify(localEmailEmulator.sent), {
headers: { "cache-control": "no-store", "content-type": "application/json" },
}),
);
}
mountApiRequestBodyLimits(app);
mountScreenTarget(app, prisma, env.screenProxySecret);
app.on(["GET", "POST"], "/api/auth/*", async (c) => {
const path = new URL(c.req.url).pathname.replace("/api/auth", "");
if (blockedAuthPaths.some((blocked) => path.startsWith(blocked))) {
return c.json({ error: "Not available in version 1" }, 404);
}
return auth.handler(c.req.raw);
});
mountLocalSettings(app, { token: env.desktopStackToken, prisma, rpc });
app.use("/rpc/*", async (c, next) => {
const session = await auth.api.getSession({ headers: sessionHeaders(c.req.raw) });
const requestedSpaceId = c.req.header("x-rakazo-space-id");
const actor = session?.user
? await requireMembership(prisma, session.user.id, requestedSpaceId).catch(() => null)
: null;
if (actor) {
enrichLogContext({ "user.id": actor.userId, "space.id": actor.spaceId });
}
const { matched, response } = await rpc.handle(c.req.raw, {
prefix: "/rpc",
context: { actor, signal: c.req.raw.signal },
});
if (matched) return c.newResponse(response.body, response);
await next();
});
mountVoiceHttpRoutes(app, { prisma, secrets }, async (c) => {
const session = await auth.api.getSession({ headers: sessionHeaders(c.req.raw) });
if (!session?.user) return null;
const actor = await requireMembership(
prisma,
session.user.id,
c.req.header("x-rakazo-space-id"),
).catch(() => null);
if (actor) enrichLogContext({ "user.id": actor.userId, "space.id": actor.spaceId });
return actor;
});
mountWebhookHttpRoutes(app, { prisma, secrets, events, jobs });
// Shared with stop so a shutdown during retry delays does not restart polling.
let messagingStopped = false;
let clearMessagingRetryDelay: (() => void) | undefined;
let messagingInitTask: Promise<void> | undefined;
let clearTeamChatRetryDelay: (() => void) | undefined;
let teamChatInitTask: Promise<void> | undefined;
// Messaging webhooks only exist when the surface is enabled.
let teamChatBridge: TeamChatBridge | undefined;
/** Constructed even before start() succeeds so stop() can cancel in-flight startup. */
let teamChatBridgeInstance: TeamChatBridge | undefined;
const pendingTeamChatInbound = new PendingTeamChatInbound();
if (messaging) {
const inboundDeps = {
prisma,
events,
jobs,
provision: (request, policyEnv) => provisionMessagingIdentity(prisma, request, policyEnv),
openSignup: env.messagingOpenSignup,
signupPolicy: {
signupsEnabled: env.signupsEnabled,
signupAllowlist: env.signupAllowlist,
},
typing: (threadId) => {
// Keep conversation addresses out of trace ids — those reach logs
// and telemetry, a different trust boundary than the database.
const operationId = `messaging.typing:${randomUUID()}`;
return messaging.sendTyping(threadId, {
operationId,
traceId: operationId,
spaceId: "",
userId: "",
// Cosmetic side call: the wait is bounded so a stalled vendor
// response never holds our callback chain (the Chat SDK adapter
// API cannot cancel the underlying request itself).
signal: AbortSignal.timeout(2000),
});
},
} satisfies Parameters<typeof createMessagingInboundHandler>[0];
const inbound = createMessagingInboundHandler(inboundDeps);
const handleTeamChatInbound = async (
bridge: TeamChatBridge,
event: Parameters<typeof wakeMessageRoutines>[2],
) => {
const mapped = toTeamChatInbound(event);
if (!mapped) {
await inbound(event);
return;
}
const canWake = await teamChatSenderCanWakeMessageRoutines(inboundDeps, event);
if (!canWake) {
await bridge.receive(mapped);
return;
}
// Persist a non-reconcilable row until routine routing owns or releases
// the message, so the timer cannot start a second TeamChat run.
const target = await bridge.receive(mapped, { queueAgent: false });
if (!target.deferred) return;
const leaseHeartbeat = await bridge.startDeferredReservationHeartbeat(
target.externalMessageId,
);
let woken = false;
bridge.markRoutineWakeInFlight(target.externalMessageId);
try {
const wakePromise = wakeMessageRoutines(inboundDeps, target, event, {
// Must match TeamChatBridge ExternalConversation / recovery provider.
deliveryProvider: bridge.providerId,
externalMessageId: target.externalMessageId,
});
try {
woken = await Promise.race([wakePromise, leaseHeartbeat.lost]);
} catch (error) {
if (isDeferredReservationLost(error)) {
// Lease loss must not start a fallback agent beside an in-flight
// wake: re-hold exclusive ownership while awaiting that wake, then
// resolve from its settled result.
let hold: { stop: () => void } | undefined;
try {
hold = await bridge.startDeferredReservationHeartbeat(target.externalMessageId);
} catch {
// Row already left deferred; wake CAS / resolve decide the winner.
}
try {
try {
woken = await wakePromise;
} catch (wakeError) {
const released = await bridge.resolveDeferredMessage(
target.externalMessageId,
"agent",
mapped.kind,
);
if (!released) {
throw new Error("Team chat deferred message ownership conflict", {
cause: wakeError,
});
}
await bridge.reconcileOnce();
getLogger().error(
"team chat routine wake failed after deferred lease loss",
wakeError,
);
return;
}
} finally {
hold?.stop();
}
} else {
await bridge.resolveDeferredMessage(target.externalMessageId, "agent", mapped.kind);
await bridge.reconcileOnce();
throw error;
}
}
const resolved = await bridge.resolveDeferredMessage(
target.externalMessageId,
woken ? "routine" : "agent",
mapped.kind,
);
if (!resolved) {
throw new Error("Team chat deferred message ownership conflict");
}
if (!woken) await bridge.reconcileOnce();
} finally {
bridge.clearRoutineWakeInFlight(target.externalMessageId);
leaseHeartbeat.stop();
}
};
const flushPendingTeamChatInbound = (bridge: TeamChatBridge) => {
pendingTeamChatInbound.flush((event) => handleTeamChatInbound(bridge, event));
};
if (env.teamChatBotId) {
const judge =
env.teamChatJudgeProvider && env.teamChatJudgeModel
? new ModelTeamChatEngagementJudge({
prisma,
runtime,
secrets,
deploymentProvider: env.defaultProvider,
deploymentModel: env.defaultModel,
deploymentModelKey: env.deploymentModelKey,
providerOverride: env.teamChatJudgeProvider,
modelOverride: env.teamChatJudgeModel,
})
: new ModelTeamChatEngagementJudge({
prisma,
runtime,
secrets,
deploymentProvider: env.defaultProvider,
deploymentModel: env.defaultModel,
deploymentModelKey: env.deploymentModelKey,
});
const bridge = new TeamChatBridge({
prisma,
events,
jobs,
send: createMessagingTeamChatSender(messaging),
providerId: "slack",
botId: env.teamChatBotId,
judge,
});
teamChatBridgeInstance = bridge;
try {
await bridge.start();
teamChatBridge = bridge;
} catch (error) {
getLogger().error("team chat bridge failed to start; retrying", error);
teamChatInitTask = (async () => {
let delayMs = 2_000;
while (!messagingStopped) {
await new Promise<void>((resolve) => {
const timer = setTimeout(resolve, delayMs);
clearTeamChatRetryDelay = () => {
clearTimeout(timer);
clearTeamChatRetryDelay = undefined;
resolve();
};
});
clearTeamChatRetryDelay = undefined;
if (messagingStopped) return;
try {
await bridge.start();
if (messagingStopped) {
await bridge.stop();
return;
}
teamChatBridge = bridge;
flushPendingTeamChatInbound(bridge);
return;
} catch (retryError) {
if (
retryError instanceof Error &&
retryError.message === "Team chat bridge start cancelled"
) {
return;
}
getLogger().error("team chat bridge failed to start; retrying", retryError);
delayMs = Math.min(delayMs * 5, 30_000);
}
}
})();
}
}
messaging.onInbound(async (event) => {
if (event.type !== "message") {
await applyMessagingOutboundStatus(prisma, event);
return;
}
if (prefersTeamChatSurface(event, env.teamChatBotId)) {
const bridge = teamChatBridge;
if (bridge) {
await handleTeamChatInbound(bridge, event);
return;
}
// Bridge is still starting (or retrying). Do not fall through to the
// personal-line inbound path — that bypasses externalMessage ownership
// and can wake routines for unlinked TeamChat senders.
if (teamChatInitTask) {
const pending = pendingTeamChatInbound.enqueue(event);
if (!pending) {
throw new Error("Team chat inbound buffer is full");
}
await pending;
return;
}
throw new Error("Team chat bridge is unavailable");
}
await inbound(event);
});
mountMessagingWebhookRoutes(app, { messaging });
// Start polling-mode adapters (e.g. Telegram with no public webhook URL
// registered) immediately rather than waiting for the first webhook
// POST or outbound send to lazily trigger it. This is the process that
// owns the inbound sink registered just above, so it must be the one
// holding the live connection — a second poller elsewhere (e.g. the
// worker) would only fight this one for Telegram's single getUpdates
// slot without ever seeing the messages itself.
// Bounded retries cover transient Telegram startup failures; polling-only
// bots otherwise stay dark until an unrelated outbound send re-inits.
messagingInitTask = (async () => {
const delayMs = [0, 2_000, 10_000];
for (let attempt = 0; attempt < delayMs.length; attempt += 1) {
if (messagingStopped) return;
if (delayMs[attempt]! > 0) {
await new Promise<void>((resolve) => {
const timer = setTimeout(resolve, delayMs[attempt]);
clearMessagingRetryDelay = () => {
clearTimeout(timer);
clearMessagingRetryDelay = undefined;
resolve();
};
});
clearMessagingRetryDelay = undefined;
}
if (messagingStopped) return;
try {
await messaging.initialize?.();
return;
} catch (error) {
getLogger().error(
attempt === delayMs.length - 1
? "messaging surface initialize failed"
: "messaging surface initialize failed; retrying",
error,
);
}
}
})();
}
// Data export endpoint — user downloads all their data as JSON
app.get("/api/data/export", async (c) => {
const session = await auth.api.getSession({ headers: sessionHeaders(c.req.raw) });
if (!session?.user) return c.json({ error: "Unauthorized" }, 401);
const userId = session.user.id;
const user = await prisma.user.findUnique({
where: { id: userId },
select: {
id: true,
name: true,
email: true,
emailVerified: true,
createdAt: true,
updatedAt: true,
},
});
const bots = await prisma.bot.findMany({
where: { userId },
select: { id: true, name: true, createdAt: true, archivedAt: true },
});
const botIds = bots.map((b) => b.id);
const runs = await prisma.run.findMany({
where: { botId: { in: botIds } },
select: { id: true, status: true, createdAt: true, updatedAt: true },
});
const consents = await prisma.aiDataConsent.findMany({
where: { userId },
select: { recipientKey: true, version: true, grantedAt: true },
});
const exportData = {
exportedAt: new Date().toISOString(),
user,
bots,
runs,
aiDataConsents: consents,
note: "Alle Daten werden lokal auf Ihrem Server gespeichert. Keine externen Dienste.",
};
const json = JSON.stringify(exportData, null, 2);
const filename = `evo-data-export-${new Date().toISOString().split("T")[0]}.json`;
return c.newResponse(json, 200, {
"Content-Type": "application/json",
"Content-Disposition": `attachment; filename="${filename}"`,
});
});
app.get("/health", (c) =>
c.json({
ok: true,
runtime: env.agentRuntime,
sandbox: env.sandboxProvider,
composio: Boolean(stack.composio),
pipedream: Boolean(pipedream),
messaging: Boolean(messaging),
email: email?.describe().id ?? null,
jobs: jobKind,
realtime: realtime.describe().id,
revision: env.gitSha ?? null,
}),
);
return {
app,
prisma,
jobs,
sandbox,
connector,
composio: stack.composio,
connectors: stack.connector,
messaging,
email,
executor,
runtime,
stop: async () => {
// Abort in-flight continueRun boot waits before draining jobs so stop() cannot sit
// on waitForComputerReady for the full boot-wait window during shared Postgres journeys.
shutdown.abort();
oauthLogins.abortAll();
messagingStopped = true;
clearMessagingRetryDelay?.();
clearTeamChatRetryDelay?.();
pendingTeamChatInbound.reject(new Error("Team chat bridge stopped before startup"));
// Cancel in-flight start() before awaiting the retry task so stop() cannot
// sit on DB/reconcile work that bridge.start() is still running.
await settleWithTimeout(
teamChatBridgeInstance ? teamChatBridgeInstance.stop().catch(() => undefined) : undefined,
TEAM_CHAT_STARTUP_SHUTDOWN_MS,
);
await messagingInitTask?.catch(() => undefined);
await settleWithTimeout(teamChatInitTask, TEAM_CHAT_STARTUP_SHUTDOWN_MS);
await messaging?.shutdown?.();
await teamChatBridge?.stop();
await email?.drain?.();
await reconciler?.stop();
await jobs.close();
await realtime.close();
await connector.stop();
await mcp.close();
await prisma.$disconnect().catch(() => undefined);
await created.pool?.end().catch(() => undefined);
await ownedJobPool?.end().catch(() => undefined);
await logger.flush({ timeoutMs: 2_000 });
},
};
}
function isTrustedOrigin(origin: string, env: AppEnv) {
if (!origin) return true;
if (origin === env.webOrigin || origin === env.apiUrl || origin === env.authUrl) return true;
if (origin.startsWith("rakazo://") || origin.startsWith("exp://")) return true;
try {
const host = new URL(origin).hostname;
return isPrivateOrLocalHost(host);
} catch {
return false;
}
}
function isPrivateOrLocalHost(host: string): boolean {
if (isLoopbackHost(host)) return true;
if (host.endsWith(".local")) return true;
if (/^192\.168\.\d{1,3}\.\d{1,3}$/.test(host)) return true;
if (/^10\.\d{1,3}\.\d{1,3}\.\d{1,3}$/.test(host)) return true;
if (/^172\.(1[6-9]|2\d|3[01])\.\d{1,3}\.\d{1,3}$/.test(host)) return true;
if (/^100\.(6[4-9]|[7-9]\d|1[01]\d|12[0-7])\.\d{1,3}\.\d{1,3}$/.test(host)) return true;
return false;
}
function isLoopbackHost(host: string): boolean {
return host === "localhost" || host === "127.0.0.1" || host === "::1" || host === "[::1]";
}
function sessionHeaders(request: Request) {
const headers = new Headers(request.headers);
const authz = headers.get("authorization");
if (authz?.toLowerCase().startsWith("bearer ") && !headers.get("cookie")) {
headers.set("cookie", `better-auth.session_token=${authz.slice(7).trim()}`);
}
return headers;
}
/**
* An ORPCError is a decision the router made (BAD_REQUEST, UNAUTHORIZED, ...) and reaches the
* caller intact. Everything else is flattened into an opaque "Internal server error", so
* unless it is logged here the only record of what actually broke is gone.
*
* The cause chain matters as much as the message: undici and most SDKs report a bare
* "fetch failed" and keep the host and errno one level down.
*/
export function logUnexpectedRpcError(error: unknown, path: readonly string[]): void {
if (error instanceof ORPCError) return;
const where = `rpc ${path.join("/")} failed`;
getLogger().error(where, error);
}