commons() creates an ellmer::Chat subclass with tools for a semantic
layer, context search, table inspection, and SQL queries.
Usage
commons(
client,
data_sources,
semantic_layer = NULL,
context_layer = NULL,
...,
instructions = NULL,
network = c("none", "full"),
log = FALSE,
share_with = NULL
)Arguments
- client
An ellmer::Chat giving the provider and model to use, e.g.
ellmer::chat_anthropic(). A system prompt already set on the client is ignored, with a warning; useinstructionsto add to commons' prompt.- data_sources
A
data_source(), or a named list of them. Measures can take a source's connection as an argument named after the source; seesemantic_layer(). When there are several sources, therun_sqlanddescribe_tabletools take a source's name as asourceargument.- semantic_layer
An optional
semantic_layer().- context_layer
An optional
context_layer().- ...
These dots are for future extensions and must be empty.
- instructions
Optional instructions placed under an
## Additional instructionsheading at the end of commons' built-in system prompt, as a single string or the path to a text or Markdown file.commons( # ... instructions = "Use the organization's fiscal-year conventions." )- network
Whether the
run_rsession has network access. One of"none"(the default) or"full". The session uses OS sandboxing on Linux and macOS. On unsupported hosts, local development can opt in to best-effort R guardrails withoptions(commons.allow_unsafe_fallback = TRUE). These guardrails are not a security boundary.- log
Whether to capture conversation trajectories with OpenTelemetry (default
FALSE). WhenTRUE, commons enables GenAI message-content capture in ellmer and tags each turn's spans with a conversation id; the spans go wherever OTel is configured to export. On Posit Connect, traces land in Connect's observability store (browsable in its Trace Viewer); commons switches on the content's Content Observability setting itself when needed, though capture only starts once the content restarts. Locally, commons configures otelsdk's file exporter automatically when no exporter is set up. Read trajectories back withtrajectory_read().An optional character vector of Connect usernames granted access to this content's trajectories when running on Posit Connect. Reading traces requires editor-level access, so named users are added as collaborators on the content. Note that users whose Connect account role is viewer cannot read traces even when named here; trace readers need at least a publisher account.
Value
An ellmer::Chat subclass.
Details
The provider and model come from client; commons sets its own system prompt
and tools. Use agent$chat() to ask questions, commons_ui() and
commons_server() to embed the agent in Shiny, and vitals::generate()
to use the agent as a vitals solver.
Examples
if (FALSE) { # \dontrun{
# A measure over local data computes directly in R.
sem <- semantic_layer(
measure(
"order_count",
"Count of orders.",
function() nrow(my_sales),
arguments = list()
)
)
agent <- commons(
ellmer::chat_anthropic(),
data_sources = data_source(sales = my_sales),
semantic_layer = sem
)
agent$chat("How many orders are there?")
# A measure takes a connection as an argument named after a data source.
# `warehouse` isn't in `arguments`, so the model never sees it; commons
# supplies it when the measure runs. Interpolate model-supplied arguments
# with glue::glue_sql() so they're quoted safely.
con <- DBI::dbConnect(duckdb::duckdb())
sem <- semantic_layer(
measure(
"revenue_by_region",
"Total revenue for a region.",
function(region, warehouse) {
DBI::dbGetQuery(
warehouse,
glue::glue_sql(
"SELECT sum(revenue) AS revenue FROM sales WHERE region = {region}",
.con = warehouse
)
)
},
arguments = list(region = ellmer::type_string("Sales region."))
)
)
agent <- commons(
ellmer::chat_anthropic(),
data_sources = list(warehouse = data_source(con)),
semantic_layer = sem
)
# Objects that aren't data sources (a pins board, an API client) come from
# argument defaults in the measure, e.g. `board = pins::board_connect()`.
# See ?semantic_layer.
} # }
