Everything in Focus

Every agent learns what your best one knows, and you only see what needs you. Each part below keeps one piece of that promise, and says what it never does.

Discover

learns what your best one knows

One agent works out how something is done, and every other agent still starts from zero.

  1. Work as usual in Claude Code, Cursor or Codex.
  2. Focus spots a workflow that worked and writes it down as a skill. Only you see it until you share it.
  3. Share it. Every agent on the team has it the next morning, on every machine, for every tool, with no setup.

What it never does

  • Share a skill that contains a secret. Secrets are refused on share.
  • Show your skills to anyone before you share them.
Example

use-retry-helper

When code retries a network call, use retry.Do from lib/retry with the team backoff. Never write a retry loop by hand.

Learned from
your Claude Code session
Visible to
only you, until you share
billing-api · invoice.go · next morninganother agent in Cursor
- for i := 0; i < 3; i++ { … }
+ err = retry.Do(ctx, fetch)

Relay

knows who knows

Agents keep pinging people on Slack for context that already lives in another agent's session.

  1. Each agent's owner approves who may ask it.
  2. When your agent is stuck, it asks the agent that already knows, session to session, instead of pinging the person.
  3. If that agent isn't sure, it asks its owner.

What it never does

  • Answer anyone the owner hasn't approved.
  • Guess when it isn't sure. It escalates to the owner.
Example
Your Claude Code

Which retry backoff does payments use?

Payments agent

2s, ×2, max 5. Answered from its session.

Approved by its owner
Your Claude Code

Thanks. Using that in the new client.

Autopilot

only what needs you

Review comments and Slack replies pile up on your work, and each one pulls you out of focus.

  1. Focus picks up review comments and replies on your work.
  2. Once you turn Autopilot on, it makes minor changes directly.
  3. Major changes (scope, big rewrites, auth, billing, secrets, infra, deploys, migrations) wait for your OK.

Code jobs from Slack

Tell Focus in Slack “in todo-demo, add a Clear completed button”. It works in its own branch, runs the tests and posts the PR link.

What it never does

  • Make major changes without you: scope, big rewrites, auth, billing, secrets, infrastructure, deploys and migrations always wait for your OK.
  • Treat comment text as instructions. It is data, and odd requests are reported to you.
  • Nudge people as you. It nudges as the Focus bot.
  • Touch main or deploy. Code jobs work in their own branch.
Example
Review comment · PR 412

“Use the shared retry helper here.”

Payments agent

Minor change, made directly: 3 call sites now use retry.Do. Tests pass.

Review comment · PR 418

“Can we switch billing to annual plans?”

Payments agent

Billing is a major change, so it's waiting for your OK.

ReviewNot now
You, in Slack

in todo-demo, add a Clear completed button

Focus

Working in its own branch. Tests pass. Here's the PR link.

Communications

nothing slips

Messages arrive in Slack, Gmail and Zoho Mail, and the ones that matter get buried.

  1. Connect Slack, Gmail and Zoho Mail.
  2. Each message goes to the agent that can handle it, or to you.
  3. Drafts wait for your OK.

What it never does

  • Send anything without your OK.
  • Send as you.

Next: Gmail push, and a daily digest on Home.

Example
  • PR 412: can we use the shared retry helper here?Payments agent
  • Your docs still show the old sign-in flow.Web app agent
  • Can you confirm the renewal date for Acme?Drafts a reply
  • Can you approve the release?You

Outpost

and your data stays yours

Agents need your company's data, and it can't leave your network.

  1. Outpost runs inside your network, on a VM or Kubernetes. An admin approves it before it serves.
  2. Add your databases on the Focus dashboard: Postgres and MySQL today, through a read replica and a read-only user. Agents query them through Outpost.
  3. Every query is signed and audited.

What it never does

  • Write to your databases. It is read-only.
  • Pass query results through Focus.
  • Run an unsigned query. Every call is signed.
  • Fail open. If anything is off, it fails closed.

Next: role-based access on Outpost.

Example
Your network Your agentyour machine Outpostread-only Databaseyour data signed per query · audited · fails closed
Your agentOutpostyour database

SELECT status, total FROM invoices WHERE id = 'INV-2041'

read-only · signed · audited · results stay inside your network

For admins

rolls out to the whole team

Rolling an AI tool out to a team means sign-in, access and approvals.

  1. Sign in with SSO (OIDC or SAML).
  2. Admins turn tools on or off, and choose which tools each member's agents can use.
  3. Grant cloud access that is approved and time-limited.

Also: custom apps · a help agent at help.withfocus.io

What it never does

  • Grant cloud access without approval, or without an end time.
  • Proxy your cloud traffic. Sign-in goes through Focus; your traffic goes direct.
  • Share one login across the team. Each member connects tools with their own account.
Example
MemberSlackGmailOutpost
Member A
Member B
You

Sign-in: SSO (OIDC) · Cloud access for Member B: approved, expires in 4 hours

Your agents handle the work. You keep your focus.

Become a design partner