How To Use Smith

What Smith Does

Smith is your workspace assistant for operations tasks like saving secrets, sharing access safely, managing browser contexts, and running recurring jobs.

Primary workflow stays in Slack. Everything here is doable via messages, and the web app is optional when you want a visual management view.

1) Start With Messages

1. Tell Smith what you want in plain language.
2. On the first message in a Slack thread, Smith captures thread metadata (channel and thread identifiers).
3. Smith guides you and performs the action in-thread.
4. For sensitive actions, Smith asks for the right checks before changes are made.

2) Store And Share Secrets Safely

• Use messages to create, update, or check secrets.
• When you prefer a dashboard, open /secrets.
• Use the secret edit page to control who can access each secret.

3) Manage Browser Contexts

• Ask Smith to create a named browser context before any authenticated browser work.
• Authenticate through the link Smith gives you, then reply done so Smith can continue.
• Smith only starts live browser automation when you explicitly ask it to use the browser.
• If a shared context loses auth, Smith can DM the owner a fresh reauthentication link.
• Delete contexts from messages or the /contexts page when they are no longer needed.
• Open /contexts when you want a web view of accessible contexts.

4) Set Up Recurring Tasks

• Ask Smith by message to run something on a schedule.
• Or manage schedules in /cronjobs if you want more control in UI.
• Run-result Slack updates are off by default; ask explicitly if you want DM/thread/channel updates.
• Check recent runs from each cronjob page.

5) What To Expect

• Message-first: you do not need the web UI for core tasks.
• Web changes require sign-in.
• Use /settings for timezone, default chat model/provider preferences, and GitHub account linking (OAuth or PAT).
• When GitHub is linked, Smith can use gh and commit/push under your GitHub identity during agent execution.
• Secrets stay encrypted and are not stored in plain text logs.
• Model/provider overrides are optional. If none are set, Smith uses the system default model.

6) API And MCP

• Programmatic API message endpoint: POST /api/message.
• POST /api/message accepts optional modelSelection for per-request model/provider/auth override.
• For subscription auth mode (Claude), provide oauthToken (starts with sk-ant-oat) or oauthTokenSecretName.
• User chat default model settings: GET/PUT /api/user/chat-model.
• OpenAPI reference document: GET /api/reference.
• Remote MCP endpoint: /mcp with OAuth discovery under /.well-known/*.
• API keys are accepted on POST /api/message and GET /api/reference.

Back to home