Open coding harness

One harness.
Any model.
Your rules.

An open coding harness for the terminal and desktop. Bring your own keys, connect tools through MCP, and scale from one developer to a team.

CLI + desktopBYOK or PAYGOpenAI-compatible API
sofia · ruut/chat-service
sofia/deepseek-v4.1connected
Refactor the request wrapper without changing its public API.

I’ll trace the call path first, then isolate retry and auth behavior behind the existing interface.

grep · request wrapperdone
app/lib/request.ts
app/lib/retry.ts
test/request.test.ts
3 relevant files
Patch prepared

Retry state is now request-scoped; auth refresh no longer mutates the shared client.

Ask Sofia to change, explain, test, or ship…
Cloud policy$18.42 / $100 team budget
Route the model that fits the work
AnthropicDeepSeekGeminiOpenRouterLocalSofia Hosted
The harness

A coding environment, not a chat window.

Sofia keeps agentic coding close to the code: sessions, tools, steering, approvals, and reusable capabilities across CLI and desktop. The cloud layer stays optional.

01 / runtime

CLI when you want speed.

Work directly in the terminal with repository context, tools, streaming output, and the same provider configuration used everywhere else.

02 / desktop

Desktop when context gets visual.

Keep sessions, file changes, tools, model state, and longer-running work visible without turning the harness into a browser IDE.

03 / models

Provider choice is a runtime setting.

Use your key, Sofia PAYG, your organization’s managed provider, or local inference. Stable Sofia model IDs hide routing complexity.

04 / capabilities

MCP without connector sprawl.

Sofia exposes one capability gateway to the harness and other clients, while teams decide which skills, plugins, and connections are available.

05 / safety

Rules live beside execution.

Approval gates, model grants, spend limits, desktop policies, and audit events are runtime controls—not settings that only affect a dashboard.

06 / openness

Cloud is additive.

Local workflows and BYOK remain first-class. Sofia Cloud adds managed inference, teams, shared capabilities, and enterprise governance when you need them.

Start where you are

Use Sofia without moving your stack.

Use your own keys, Sofia-hosted models, or both. A depleted balance never blocks a working organization key.

terminalsofia
$ sofia

› model sofia/deepseek-v4.1
  route organization key → Sofia PAYG fallback

› fix the flaky webhook spec and explain the root cause

reading  app/controllers/webhooks/clover_controller.rb
reading  test/controllers/webhooks/clover_controller_test.rb
✓ isolated signature timestamp drift
✓ patched verifier + regression test
✓ 14 tests passed
Local and cloud

Keep the coding loop local.

Sofia Cloud is a control plane for identity, models, pricing, and policy — not the place where every shell command or file edit happens.

On your machine

The working loop

Repository context, terminal tools, file edits, approvals, local models, and interactive sessions stay close to the developer.

repo→sofia→tools→changes
Sofia Cloud

The shared control plane

Teams, hosted inference, spend controls, SSO/SCIM, MCP authorization, audit, pricing, and shared provider access.

identity→policy→models→billing
“The model is a dependency. The harness is the product you should be able to keep.”
Sofia design principle

Start local. Add the cloud later.

Download Sofia, bring a provider key, and keep the same workflow when you add hosted models, budgets, and enterprise controls.