Integrations

Keito integrations all write to the same workspace, permission model, project list, task list, and approval workflow. Choose the install path that matches how work is created.

IntegrationBest forFirst command
Keito CLIHumans, agents, scripts, and CI jobs that can run terminal commandsbrew install osodevops/tap/keito
Agent SkillCodex and Claude Code sessions that should be logged automatically per repositorykeito skill install
XeroSyncing invoices to accountingConnect in Keito settings
QuickBooksSyncing invoices to accountingConnect in Keito settings
StripeAccepting invoice payments onlineConnect in Keito settings

CLI or Skill?

Use the CLI when you want explicit commands:

keito time start --project "Acme Website" --task "Development"
keito time stop --notes "Implemented OAuth flow"

Use the Agent Skill when you want Codex or Claude Code to log local coding sessions automatically. The skill uses the CLI under the hood, so authentication, permissions, project access, and API writes stay in one place.

keito auth login
keito skill install
cd ~/work/acme-project
# In Codex or Claude Code:
/track-time-keito

The Agent Skill is installed from the GitHub skill repo. It is not published as an npm package; npx only runs the pinned skills@1.5.6 installer.

Data Boundaries

The CLI authenticates as the current Keito user or API key. It can only access the company, clients, projects, and tasks allowed by that credential.

The Agent Skill adds one repo-local file, .keito/config.yml, after you run the setup wizard in that repository. Each repository chooses its own company, client, project, and task. The hooks search upward from the active working directory and do not reuse another repository’s config.

See Also