Ottto for teams

Share the evidence. Keep ownership clear.

Invite teammates, share selected reports read-only, and investigate repeated agent work—without turning team membership into blanket access.

Request team access → Book a walkthrough

Guided early access. We’ll map Ottto to the agent sources and workflows your team already uses.

Agent operations Example only
Agent family

Release validation

Trace one run’s observed branches, with model, token, and cost evidence where available.

Recurring group
Dependency review Schedule evidence
Coverage
Source attached Freshness recorded
Team access, explicit by design

Invite teammates. Share only what you choose.

Each organization has admins and members. Saved reports stay private to their owner until that owner grants read-only access to a named teammate in the same organization.

  • Invite with a clear role.

    Admins add teammates as admins or members.

  • Grant one person access.

    The report owner chooses a named recipient in the same organization.

  • Stay in control.

    The grant is read-only and can be revoked or set to expire.

SAVED REPORT

Weekly agent review

Example only
Report ownerKeeps the saved definition and data scope Owner
Named teammateRead-only access from this owner Read only
Other organization memberMembership alone grants nothing No access

A grant opens this owner’s report. It does not create an organization-wide view.

Two views of agent work

Separate recurring jobs from one run’s fan-out.

Recurring groups connect repeated instances of one job. Agent families trace the work a single run started. Review either pattern without conflating them.

01
RECURRING GROUPS

Same job, across runs.

Ottto groups runs only when evidence shows a proven schedule, a matching prompt template, or a repeated title. Review cadence, history, and observed cost together.

02
AGENT FAMILIES

One run, across agents.

Move between Map, Timeline, List, and Details to inspect evidence-derived parent-child links. Model, token, cost, machine, and active-time fields appear only when the source supports them.

Compare repository context

See which repositories start with more context.

Compare each repository’s median first measured prompt in the selected scope. Then inspect peak fill by session—against that session’s resolved model window—when the evidence supports it.

  • Side-by-side rows when two or more repositories are measured
  • Machine and repository filters for a tighter scope
  • Measured differences without an invented cause
STARTUP DEPTH BY REPOSITORY

Median first measured prompt

Example only

Investigate the difference. Check repository instructions, loaded files, and repeated context before changing the workflow.

Coverage before conclusions

Know what each number can prove.

Ottto keeps source, freshness, and evidence state beside the analysis, so teammates can tell what is observed, estimated, incomplete, or unavailable before acting.

01

Source stays attached

Agent history, billing data, and other connected evidence remain labeled by source class.

Observed
02

Freshness stays visible

See when a source last reconciled before treating its values as current.

As of
03

Missing stays missing

Estimated, incomplete, and unavailable states remain explicit instead of becoming false precision.

Gap
Team early access

Give the right teammate the right evidence.

Tell us which agent tools, repositories, and recurring workflows you need to review. We’ll confirm fit and help connect the first sources.

Request team access → Book a walkthrough