roboport@0.9.1

Patch Changes

• #81 e2616b2 Thanks @Destiner! - Resolve claudeCode file-tool paths against the session cwd. Read, Edit, and Write passed file_path straight to the filesystem, so a relative path resolved against process.cwd() and escaped the directory the session was scoped to — the pi harness already resolved against ctx.cwd. Their schemas demanded absolute paths, which masked the bug with models that reliably send them; models that send ./note.txt wrote to the wrong directory. Absolute paths are unaffected.

roboport@0.9.0

Minor Changes

• #79 5152918 Thanks @Destiner! - Add an OpenRouter model adapter (roboport/models), reaching OpenRouter's full catalogue behind one OPENROUTER_API_KEY. All six thinking levels map onto reasoning.effort without clamping, searchWeb uses the server-side web plugin, and reasoning_details are replayed verbatim on later turns so reasoning models stay coherent across tool calls.

  OpenAICompatible grows three protected seams for subclasses: extraHeaders(), createReasoningAccumulator() for providers that don't use reasoning_content, and an optional second thinking argument to adaptAssistantWire().

roboport@0.8.1

Patch Changes

• #77 4573baf Thanks @Destiner! - Recover the text of a replied-to rich message. A message sent with sendRichMessage carries no text — its content is a block tree under rich_message — so replyTo.text was empty whenever a user replied to one of the agent's own replies, which is the common case. TelegramMessage now models rich_message, and the new richMessageText helper (exported from roboport/triggers) flattens the block tree into plain text.

roboport@0.8.0

Minor Changes

• #75 9d33ca2 Thanks @Destiner! - Carry the replied-to message through to inbound channel messages. InboundMessage.replyToId is replaced by replyTo, a ReplyContext with the parent message's id, text, user, whether it was the agent's own message (isBot), and the fragment the sender highlighted (quote) — Telegram delivers the parent inline, so nothing is looked up. The Telegram channel now types its inbound messages as TelegramInboundMessage, narrowing raw to TelegramMessage across serve's seams. serve's default prompt is still message.text; use the prompt seam to fold the reply into what the agent sees.

roboport@0.7.1

Patch Changes

• #71 e939e52 Thanks @Destiner! - Add OpenTelemetry instrumentation. Emits GenAI-convention traces (agent.turn, chat.model, tool.execute, mcp.connect/mcp.request, channel.receive/channel.send, trigger.receive/trigger.send) and metrics (token counter, turn-duration histogram, tool-error counter) against the global @opentelemetry/api. Bring your own SDK and exporter; no-op when none is registered. Set OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT=true to attach prompt/completion and tool content to spans.

roboport@0.7.0

Minor Changes

• #69 dd90f29 Thanks @Destiner! - Rename the gateways concept to channels. The roboport/gateways subpath is now roboport/channels, telegramGateway is telegramChannel, and the Gateway/Channel pair is renamed to Channel/Conversation (GatewayHandler → ChannelHandler, GatewayRuntime → ChannelRuntime, TelegramGateway → TelegramChannel, TelegramGatewayOptions → TelegramChannelOptions, the per-conversation reply handle TelegramChannel → TelegramConversation).

roboport@0.6.0

Minor Changes

• #67 cbd913a Thanks @Destiner! - Telegram replies are now sent as rich messages, rendering Markdown (headings, lists, tables, code, math) instead of plain text.