Domu · Task agent
Clementino
A general-purpose 'AI colleague' spanning sales, finance, client ops, engineering, and recruitment, later split into a reusable toolkit plus Slack and desktop surfaces.
- Approach type
- Task agent
- Work
- Support, Finance ops, Coding, Recruitment, Customer success
- Human involvement
- Human in loop
- Invocation
- Interactive
- Interfaces
- Slack, Desktop
- Deployment stage
- Deployed
- Evidence strength
- Detailed primary
- Entry reviewed
How it works
The workflow the sources report for this implementation.
Transient conversation, persistent facts, knowledge RAG, and live system state; kept separate
Capabilities separated from the interface layer so they power multiple surfaces
Where people stay involved
- employee request → approved customer-impacting actionWork product review · Level 3
Level 3 for employee request → approved customer-impacting action; human attention boundary: work-product-review.
- Observation date
- 2026
Implementation details
Claude/Anthropic SDK wrapper; a reusable tool/skill/memory layer separated from the Slack and desktop interfaces
Claude (Anthropic SDK)
slack, desktop
~35 integrations organized into skills; specialist delegates per domain
Four memory layers: conversation context, persistent facts, knowledge RAG, and live system state
Customer-impacting actions gated behind team-visible Slack approvals
Four-layer memory separation; prompt size dropped substantially after splitting capabilities from the Slack layer
Reported results and limitations
The catalog records what the sources report, with the scope and the denominator of every figure. A qualification below limits the figure it sits under.
Reported metrics
~35 integrations organized into skills
The source does not report the denominator of this figure.
- Reported by
- Domu
- Scope
- Clementino toolkit integration modules organized into skills
~35 integrations organized into skills
The source does not report the denominator of this figure.
- Reported by
- Domu
- Scope
- Clementino toolkit integration modules organized into skills
Lessons and interpretation
Separate reusable capabilities (tools/skills/memory) from the interface layer; prompt size drops while capability is preserved
Model memory explicitly: conversation context, persistent facts, RAG, and live state have different lifecycles
Gate customer-impacting actions behind human approvals rather than trusting the model
Sources and research details
Citations link to the original publisher. Each source also keeps a preserved copy in the repository, so a changed or removed page stays checkable.
Research details for every claim on this page
- Summary
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Headline claim
- Statement type
- Metric
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Reported by
- Domu
- Scope
- Clementino toolkit integration modules organized into skills
- Denominator
- Not reported
- Method
- Not reported
- Observation date
- Not reported
- SupportsWhy we split our internal agent in twoPreserved content.md, lines 58–60
- Harness
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Model
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Interfaces
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Tool access
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Knowledge
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Credentials
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Context management
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Supporting component
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Supporting component
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Key observation
- Statement type
- Metric
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Reported by
- Domu
- Scope
- Clementino toolkit integration modules organized into skills
- Denominator
- Not reported
- Method
- Not reported
- Observation date
- Not reported
- SupportsWhy we split our internal agent in twoPreserved content.md, lines 58–60
- Lesson
- Statement type
- Inference
- Provenance
- Catalog judgment
- Confidence
- Medium
- Confidence reason
- The catalog derives this observation from the linked sources.
- Lesson
- Statement type
- Inference
- Provenance
- Catalog judgment
- Confidence
- Medium
- Confidence reason
- The catalog derives this observation from the linked sources.
- Lesson
- Statement type
- Inference
- Provenance
- Catalog judgment
- Confidence
- Medium
- Confidence reason
- The catalog derives this observation from the linked sources.
- Operating model assessment
- Statement type
- Inference
- Provenance
- Catalog judgment
- Confidence
- High
- Confidence reason
- The source documents explicit human approval for customer-impacting actions.
- Observation date
- 2026