reckon

Introduction

One workspace for running several businesses with a coding agent, through the tools each business already uses.

reckon is one workspace for running several businesses with a coding agent.

Each business is an org. An org has its own environments (prod, uat, dev by default), tool connections, company knowledge and saved work. You open one org in one environment, and Claude Code or Codex works on that business through the tools you already use: development, product, growth and operations.

Reckon is the reckon command plus one folder per org. Your data lives under ~/.reckon, never in the Reckon checkout.

The model

ConceptMeaning
OrgOne business. Has a name, environments, connections, knowledge and saved work.
EnvironmentPer org, for example prod, uat, dev. Environments named prod or production are marked production by default.
ConnectionOne configured account of one tool: a Jenkins server, a CubeAPM tenant, a Search Console login.
ContextThe org and environment an agent works in. Pinned when the agent starts.
WorkspaceThe folder the agent runs in for an org. Holds knowledge and saved work.

A connection is tied to one environment, or shared by all of them:

reckon org add acme --envs prod,uat,dev
reckon connect jenkins-prod --org acme --provider jenkins --for-env prod     # one server per environment
reckon connect jenkins-uat  --org acme --provider jenkins --for-env uat
reckon connect cubeapm      --org acme --provider cubeapm --label prod=PROD --label uat=UAT   # one server, all environments
reckon connect gsc          --org acme --provider gsc                         # no environments at all
reckon use acme/prod
reckon verify            # one live read per connection
reckon open              # starts Claude Code (or Codex) in acme's folder, pinned to prod

Inside the agent, every tool goes through Reckon:

reckon run jenkins -- build list deploy-api -o json      # the prod Jenkins, read-only
reckon run gsc -- top queries --site sc-domain:acme.com --last 28d -o json

Safety

  • The agent never holds credentials. reckon run loads one connection's settings into one command. reckon open strips tool credentials from the agent's environment.
  • Reads are read-only. Reckon forces each CLI's read-only and no-prompt modes, allows only read commands for CLIs that have no such mode, and refuses flags that would change the target or switch safety off. Databases, caches and queues ask you before every run.
  • The context is pinned. An agent starts on one org and environment. A connection from another environment is refused, and so is another environment's label on a shared server like CubeAPM.
  • Each org has its own folder (~/.reckon/orgs/<org>/workspace), so Claude Code and Codex keep each business's memory and conversations apart.

These rules stop mistakes, not a hostile process running as your user. Database roles must still be read-only on the server. Reckon does not perform writes yet: when a change is needed, the agent describes it and you make it. Prepared writes that you approve are the next milestone.

Areas and tools

AreaConnection providers
Developmentjenkins, github, kubernetes, aws
Operationscubeapm, grafana, elasticsearch, nginxpm, plus postgres, mysql, mongodb, clickhouse, redis, kafka, kafka-rpk (each run asks you first)
Productjira, clarity
Growthgsc (Google Search Console), bing (Bing Webmaster Tools)

Saved work

Work that matters gets a session. Sessions keep every read with its command, connection, time and hashes, plus the findings and hypotheses drawn from them. Incident investigations add mapped services, typed collection and promotion to an RCA. For operations, the bundled reckon skill routes incident work into three modes: investigate a specific fault, monitor for problems, or analyze behaviour over time. Try one offline with reckon demo.

Independent project. Not affiliated with the vendors of the connected tools; all trademarks belong to their owners.