Assess
Check Grafana alerts, Jenkins build status, and the CubeAPM service inventory.
grafana alert rule list -o jsonOne agent workspace for everybusiness you run.
Reckon gives a coding agent one org at a time: its environments, tool connections, knowledge and saved work. Every tool call goes through Reckon, with the right account and read-only.
read-only, always
Speaks the language of your stack
GrafanaJenkinsCubeAPMAWSGitHub ActionsKafkaKubernetesRedisMongoDBPostgreSQLMySQLClickHouseElasticsearchJiraNginx Proxy ManagerSearch ConsoleBing Webmaster ToolsMicrosoft Clarity
How an investigation flows
start broad, then narrow
Investigate errors
Search error traces and related logs, then open the trace waterfall for the affected service.
cubeapm traces search --status error --last 1hCheck metrics
Compare error rate, latency, and service health across the incident window.
cubeapm metrics query 'error_rate' --last 1hCheck deployments
Review deploy annotations, recent Jenkins builds, build logs, merged pull requests, and releases.
jenkins build list checkout/deploy --limit 5Map dependencies
Trace error propagation through the dependency graph and check the supporting infrastructure.
cubeapm traces get <trace-id> -o jsonCorrelate
Match deployment timestamps with error spikes, Grafana annotations, and cluster events.
kubectl get events -n checkout --sort-by=.lastTimestampEverything, in one workspace
Development, operations, product and growth tools for a coding agent, one business at a time.
01
Orgs and environments
Each business keeps its own environments, connections, knowledge and sessions. An agent opens one org in one environment and cannot step outside it.
02
Every tool through one command
Jenkins, CubeAPM, Grafana, GitHub, Jira, Search Console, Bing, Clarity and more through reckon run, each with the connection that matches the environment.
03
Read-only by construction
Reckon forces each CLI's read-only mode and refuses arguments that change the target, the credentials or the environment. Database runs ask you first.
04
Credential isolation
Each connection keeps its credentials and CLI profile under ~/.reckon, apart from your global configuration and out of the agent's environment.
05
Saved work
Sessions keep every read with its command, connection and hashes. Findings cite evidence, and the work survives the conversation.
06
Incident investigations
Move from an alert to traces, metrics, logs, deployment history and infrastructure state with a disciplined RCA workflow.
Correlate the timeline
Reach every connected tool through reckon run, with the active environment's credentials, so a coding agent can correlate signals across systems in one session.
correlate the timestamps
incident / checkout correlation view
01Grafana alert
grafana alert rule list -o jsonEstablish the active alert window.
02Jenkins build
jenkins job list --recursive --status FAILURE -o jsonCompare build start and completion times.
03CubeAPM error rate
cubeapm metrics query 'rate(http_requests_total{status=~"5.."}[5m])' -o jsonLocate the error spike.
04Kubernetes event
kubectl get events -n checkout --sort-by=.lastTimestamp | tail -30Check whether the failure lines up with cluster events.