eve 0.44.3 → 0.44.4

package/docs/channels/linq.mdx

@@ -16,7 +16,7 @@ export default linqChannel({
 });
 ```
 
-The default webhook route is `/eve/v1/linq`. The channel verifies forwarded webhooks with same-project Vercel OIDC by default, marks accepted messages as read, and continues the same eve session for every message in a Linq conversation. A new accepted message cooperatively cancels an active turn and steers its replacement turn.
+The default webhook route is `/eve/v1/linq`. The channel verifies forwarded webhooks with same-project Vercel OIDC by default, derives user auth from each message author, marks accepted messages as read, and continues the same eve session for every message in a Linq conversation. A new accepted message cooperatively cancels an active turn and steers its replacement turn.
 
 Set `turnPolicy: "queue"` when every response should finish before Linq starts the next message.
 

package/docs/channels/photon.mdx

@@ -22,10 +22,10 @@ export default photonIMessageChannel({
 ```
 
 The default webhook route is `/eve/v1/photon`. The channel verifies forwarded
-webhooks with same-project Vercel OIDC by default, marks accepted messages as
-read, and continues the same eve session for every message in an iMessage
-conversation. A new accepted message cooperatively cancels an active turn and
-steers its replacement turn.
+webhooks with same-project Vercel OIDC by default, derives user auth from each
+message author, marks accepted messages as read, and continues the same eve
+session for every message in an iMessage conversation. A new accepted message
+cooperatively cancels an active turn and steers its replacement turn.
 
 Set `turnPolicy: "queue"` when every response should finish before Photon starts the next message.
 

package/docs/channels/slack.mdx

@@ -33,6 +33,20 @@ export default slackChannel({
 
 `connectSlackCredentials` returns `{ botToken, webhookVerifier }`, keeping token rotation, multi-workspace tenancy, and request verification inside Connect rather than your code.
 
+Function-form bot tokens receive `{ teamId }` when Slack supplies the app installation workspace. Use it to select an installation in a self-managed multi-workspace app. The id can differ from the actor or content workspace for Slack Connect events:
+
+```ts title="agent/channels/slack.ts"
+import { slackChannel } from "eve/channels/slack";
+
+export default slackChannel({
+  credentials: {
+    botToken: ({ teamId }) => loadInstallationToken(teamId),
+  },
+});
+```
+
+Literal tokens and zero-argument token functions remain supported. A multi-workspace provider should reject a missing `teamId` instead of selecting a default installation.
+
 ### Manage Slack credentials yourself
 
 Use this fallback when the agent does not run on Vercel or Vercel Connect is unavailable. In the setup command, **Use portable credentials** is the environment-variable option; eve adds `SLACK_BOT_TOKEN` and `SLACK_SIGNING_SECRET` to `.env.example`.
@@ -357,6 +371,7 @@ import { connectSlackCredentials } from "@vercel/connect/eve";
 const { botToken } = connectSlackCredentials("slack/my-agent");
 const response = await callSlackApi({
   botToken,
+  context: { teamId: "T0123456789" },
   operation: "reactions.get",
   body: { channel: "C0123456789", timestamp: "1712345678.000100", full: true },
 });
@@ -364,7 +379,7 @@ if (!response.ok) throw new Error(String(response.error));
 ```
 
 `callSlackApi` resolves function-form tokens (secret managers, Connect
-rotation) at call time and form-encodes the body — the only safe default,
+rotation) with the supplied `context` at call time and form-encodes the body — the only safe default,
 since Slack's JSON support is partial (`conversations.replies` rejects
 JSON). `resolveSlackBotToken` materializes a `SlackBotToken` to a string
 when you need the bearer token itself.
@@ -414,7 +429,7 @@ events: {
 
 ### Proactive sessions
 
-Start a session without an inbound message through `ctx.to(slack, target).send(message, { auth })` from another channel, or `to(slack, target).send(message, { auth })` from a schedule `run` handler. The proactive target shape is `{ channelId, threadTs?, initialMessage? }`. This sends turn input to the agent; it is not a direct Slack post.
+Start a session without an inbound message through `ctx.to(slack, target).send(message, { auth })` from another channel, or `to(slack, target).send(message, { auth })` from a schedule `run` handler. The proactive target shape is `{ channelId, installationTeamId?, threadTs?, initialMessage? }`. Set `installationTeamId` to the app installation workspace when a function-form bot token must select an installation. This sends turn input to the agent; it is not a direct Slack post.
 
 To post without invoking the model, use `ctx.thread.post(...)` in an inbound Slack handler or `channel.thread.post(...)` in an `events` handler. Use `callSlackApi(...)` where no Slack channel context exists. For application-managed retries and deduplication, see [Durable cross-channel notifications](../patterns/durable-cross-channel-notifications).
 
@@ -422,7 +437,7 @@ To post without invoking the model, use `ctx.thread.post(...)` in an inbound Sla
 
 Inbound files behind authenticated Slack URLs are staged with `fetchFile`. See [File uploads](./custom#file-uploads) for the `fetchFile` contract.
 
-Private file downloads require the Slack bot token's `files:read` scope. Add the scope and reinstall the Slack app before sending attachments.
+Private file downloads resolve credentials from the session's app installation workspace and require the Slack bot token's `files:read` scope. Add the scope and reinstall the Slack app before sending attachments.
 
 Staged files live in the session sandbox under `/workspace/attachments`. Session history keeps a reference to that path, not a second copy of the Slack file. If the backend can no longer reattach the original sandbox, eve cannot restore the attachment bytes from history; later turns receive a missing-file result. Store files outside the sandbox when the agent must retain them independently of sandbox availability.
 

package/docs/concepts/built-in-tools.md

@@ -32,6 +32,7 @@ Notes:
 - **`load_skill`** only pulls instructions into context. It adds no new execution surface, because behavior still comes from the tools the agent already has.
 - **`connection_search`** surfaces a connection's tools by their qualified name (e.g. `linear__list_issues`), which the model can then call directly. It's registered only when the agent has connections.
 - **`web_search`** has no local executor; the provider runs it. AI Gateway models use Exa by default. To use Parallel instead, export `webSearch({ provider: "parallel" })` from `agent/tools/web_search.ts`. Direct provider models continue to use their native search implementation. To supply your own implementation, override it with `defineTool()`.
+- **`web_fetch`** follows up to ten redirects, rechecking every destination for SSRF safety. Non-success HTTP responses return a plain-text failure result with the response body when available instead of failing the tool call.
 
 Review these default tools before production use. Disable, wrap, restrict, or require approval for any tool that can access the filesystem, network, shell, or sensitive data.
 

package/docs/getting-started.mdx

@@ -75,6 +75,7 @@ A minimal agent needs `instructions.md`; `agent.ts` is optional when the default
 
 ```text
 my-agent/
+├── README.md
 ├── package.json
 ├── tsconfig.json
 ├── agent/

package/docs/guides/dev-tui.md

@@ -13,24 +13,35 @@ The transcript remains in your terminal scrollback after you exit. Run `/help` i
 
 ## Commands
 
-| Command       | Description                                                                                           |
-| ------------- | ----------------------------------------------------------------------------------------------------- |
-| `/model`      | Configure the model and its provider. Pass a model ID to set it directly: `/model provider/model-id`. |
-| `/add`        | Browse and install channels, MCP connections, extensions, and observability integrations.             |
-| `/deploy`     | Deploy the agent to Vercel production. Links the directory first if needed.                           |
-| `/vc:install` | Install the Vercel CLI.                                                                               |
-| `/vc:login`   | Log in to Vercel or restore access to a remote deployment.                                            |
-| `/loglevel`   | Choose which server and agent logs appear in the transcript.                                          |
-| `/traces`     | Open the local trace viewer. Pass a trace ID prefix to open a specific trace.                         |
-| `/reset`      | Start a fresh session.                                                                                |
-| `/cancel`     | Cancel the current turn without discarding settled context.                                           |
-| `/clear`      | Clear the session's model-message history. `/new` is an alias.                                        |
-| `/compact`    | Compact the current session's context.                                                                |
-| `/exit`       | Quit the UI.                                                                                          |
-| `/help`       | List available commands.                                                                              |
+| Command       | Description                                                                                                                                               |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `/model`      | Configure the model and its provider. Pass a model ID to set it directly: `/model provider/model-id`.                                                     |
+| `/add`        | Browse and install channels, MCP connections, extensions, and observability integrations. Pass an item address to open it directly: `/add channel/slack`. |
+| `/deploy`     | Deploy the agent to Vercel production. Links the directory first if needed.                                                                               |
+| `/vc:install` | Install the Vercel CLI.                                                                                                                                   |
+| `/vc:login`   | Log in to Vercel or restore access to a remote deployment.                                                                                                |
+| `/loglevel`   | Choose which server and agent logs appear in the transcript.                                                                                              |
+| `/traces`     | Open the local trace viewer. Pass a trace ID prefix to open a specific trace.                                                                             |
+| `/reset`      | Start a fresh session.                                                                                                                                    |
+| `/cancel`     | Cancel the current turn without discarding settled context.                                                                                               |
+| `/clear`      | Clear the session's model-message history. `/new` is an alias.                                                                                            |
+| `/compact`    | Compact the current session's context.                                                                                                                    |
+| `/exit`       | Quit the UI.                                                                                                                                              |
+| `/help`       | List available commands.                                                                                                                                  |
 
 `/model`, `/add`, `/deploy`, and `/traces` are available when `eve dev` runs locally. They are unavailable when the UI connects to a server with `--url`.
 
+## Add an integration
+
+Bare `/add` opens the categorized registry browser. Pass an item address — `<category>/<name>`, where category is `channel`, `connection`, `extension`, or `instrumentation` — to skip the category and search screens and open that item directly:
+
+```text
+/add channel/slack
+/add extension/agent-browser
+```
+
+Either way the UI shows the item's details and asks to confirm before installing, then runs the same installation and setup prompts. Choosing **Back** on a directly addressed item returns to the registry browser.
+
 ## Work with the agent
 
 Type a message and press `Enter` to send it. When the agent asks a question or requests tool approval, respond in the prompt shown by the UI. Connection authorization can open a browser; keep local `eve dev` running until the browser returns to it.

package/docs/meta.json

@@ -34,6 +34,6 @@
     "patterns",
     "...reference",
     "responsible-use",
-    "[Benchmarks](/evals)"
+    "[Benchmarks](/benchmarks)"
   ]
 }

package/docs/sandbox.mdx

@@ -182,6 +182,26 @@ export default defineSandbox({
 
 `justbash()` needs no daemon or VM, but commands run in a simulated bash with a virtual filesystem under `.eve/sandbox-cache/`, with no real binaries (`git`, `node`, package managers) and no network isolation. The `just-bash` package is an optional peer dependency, so `eve dev` installs it into your application automatically when missing (disable with `autoInstall: false`); production processes fail with an actionable install error instead.
 
+Pass `customCommands` to expose a `just-bash` `CustomCommand` inside each live sandbox session. The command participates in shell pipelines, redirections, and exit-code handling like a built-in command:
+
+```ts title="agent/sandbox.ts"
+import { defineSandbox } from "eve/sandbox";
+import { justbash } from "eve/sandbox/just-bash";
+import { decodeBytesToUtf8, defineCommand } from "just-bash";
+
+const uppercase = defineCommand("uppercase", async (_args, context) => ({
+  stdout: decodeBytesToUtf8(context.stdin).toUpperCase(),
+  stderr: "",
+  exitCode: 0,
+}));
+
+export default defineSandbox({
+  backend: justbash({ customCommands: [uppercase] }),
+});
+```
+
+Custom commands are registered on live and reopened sessions, not during template prewarming. They run trusted host application code and create an explicit bridge from the sandbox to that code. Adapters can use this extension point to expose application APIs such as a Capable App's CLI; the outer eve `bash` tool does not automatically provide per-command Capable approvals.
+
 You can also write your own backend. A `SandboxBackend` is an adapter object with a `name`, a `create`, and an optional `prewarm`. It can point at your own container runner, VM pool, internal sandbox service, or another isolation layer, as long as it returns the `SandboxSession` operations eve needs. Handles returned by `create` implement `shutdown()`, which stops the underlying compute at server shutdown. See the `SandboxBackend*` types on `eve/sandbox`.
 
 ## Lifecycle

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eve",
-  "version": "0.44.3",
+  "version": "0.44.4",
   "private": false,
   "description": "Filesystem-first framework for durable backend AI agents that run anywhere.",
   "keywords": [
@@ -381,7 +381,7 @@
     "@opentelemetry/api": "^1.0.0",
     "ai": "^7.0.58",
     "braintrust": "^3.0.0",
-    "just-bash": "^3.0.0",
+    "just-bash": "^3.1.0",
     "microsandbox": "^0.5.0"
   },
   "peerDependenciesMeta": {