Slaunt - The Best Way to Cowork with AI

· Slaunt

2 min read Original article ↗

Deploy Claude Code safely

Slaunt gives agents context and controls what they can see, so your team can deploy code with confidence.

Decisions, surfaced in seconds

Designed to unify the workspace

Built with security from the ground up

Your data is encrypted, never used to train AI models, and protected by independently audited controls.

Full audit trail

Every agent action is recorded to an immutable, queryable log — so you can see exactly what ran, when, and why.

Least-privilege access

Every agent runs with scoped, tenant-isolated permissions — you decide exactly what each one can see, write, and run.

No training on your data

Your workspace data is never used to train models.

Slaunt Chatthread · #login-issue

Chris L.

Chris L. 10:02

Users are reporting long loading times during login. Can anyone read logs?

Jack A.

Jack A. 10:04

Looks like it's oAuth — nothing is printing to Sentry.

Raj B.

Raj B. 10:05

Cool. Can I push a fix?

Jakob H.

Jakob H. 10:07

Hold off on pushing anything — let legal approve first.

Claude Coderun #2041

> fix oAuth telemetry to Sentry

Reading workspace context before touching anything…

Read the GitHub issue+3 updates

Read the #login-issue thread+1 update

Read payments-v2 decisions2m ago

Jakob asked to hold off until legal approves. Continue anyway?

HoldContinue

OAuth not logging data to Sentry

Open

Kerode M.Opened May 20BugCriticalLoginTelemetry

Problem

OAuth failures happen without enough observability. When a user fails to authenticate we don't reliably get Sentry events with provider, callback route, error type, or request state — so auth failures look like silent failures during onboarding and demos.

Agent notes

Inspect the OAuth callback handler, current Sentry setup, environment config, and error boundaries. Prioritize safe observability over verbose logging.

Done when

  • Callback failures appear in Sentry
  • Token exchange errors appear in Sentry
  • Events include provider, route, and sanitized error type

avataravataravatar

Angela, Christoper P., Michael V. and 3 more are watching

Auto-routed68%

Median wait42s

Handoffs today143

SLA met99%

Refund flow — legal sign-offpayments-v2

Quaero Agent

Sandra L.

Handed off

INC-207 · checkout latencyincident

Triage

On-call

Escalated

PR #412 review commentsbilling-service

George P.

Claude Code

Auto-routed

Acme renewal follow-upcustomer

Inbox

CS team

Queued · 42s

oAuth Tasked AgentLIVElaunched by Kerode M. · 3m 12s

Guardrails

  • Tool access · Railway logs only
  • Approval required for writes
  • Sentry views · declined by Sandra L.

Kill oAuth Tasked Agent?

The run stops immediately. $3.96 of the $4.50 cap has been used.

CancelKill agent

oAuth Tasked AgentKerode M.$3.96Waiting for approval

Quaero Research #2041Sandra L.$1.12Running

Refund AgentGeorge P.$0.48Running

Sentry TriageMichael V.$4.50Blocked · cap reached

Docs SyncAngela$0.22Idle

Audit trail

0432 Kerode M. approved Railway log view

0431 Spend guard capped Sentry Triage at $4.50

0430 Sandra L. declined Sentry views for run #2041

Make your agents smarter