Skip to content

feat: add ATLAS knowledge base integration#114

Closed
chipoto69 wants to merge 2 commits intoopenclaw:mainfrom
chipoto69:feat/atlas-integration
Closed

feat: add ATLAS knowledge base integration#114
chipoto69 wants to merge 2 commits intoopenclaw:mainfrom
chipoto69:feat/atlas-integration

Conversation

@chipoto69
Copy link

@chipoto69 chipoto69 commented Jan 2, 2026

Summary

  • Add atlas_query tool with 5 actions: search, concept, insights, actions, stats
  • Register tool in clawdis-tools.ts
  • Add ATLAS skill documentation for agent usage
  • Add ATLAS Bridge Guide for Phase 2 preparation (Push Path)

Phase 1: Pull Path (This PR)

Enables Clawdis agent to query the user's ATLAS personal knowledge base via HTTP API.

New Files

File Description
src/agents/atlas-tool.ts ATLAS query tool implementation
skills/atlas/SKILL.md Agent documentation for ATLAS usage
docs/ATLAS_BRIDGE_GUIDE.md Guide for ATLAS team to prepare Phase 2

Tool Actions

Action Description Required Params
search Semantic search across knowledge query
concept Get concept details concept_name or query
insights Get curated insights query (optional)
actions Get pending action items none
stats Get knowledge base overview none

Phase 2: Push Path (Future)

The included docs/ATLAS_BRIDGE_GUIDE.md documents how the ATLAS team should prepare for webhook-based event notifications (new insights, notes, content ingested, agent finished).

Testing

  1. Start ATLAS: atlas serve (port 8888)
  2. Start Clawdis gateway
  3. Ask agent: "What do I know about [topic]?"

Environment Variables

ATLAS_URL=http://localhost:8888  # Default, configurable

feat: add ATLAS knowledge base integration
7655f35 
- Add atlas_query tool with 5 actions: search, concept, insights, actions, stats
- Register tool in clawdis-tools.ts
- Add ATLAS skill documentation for agent usage
- Add ATLAS Bridge Guide for Phase 2 preparation

This implements Phase 1 (Pull Path) of the ATLAS integration.
Phase 2 (Push Path via webhooks) is documented in docs/ATLAS_BRIDGE_GUIDE.md
@chatgpt-codex-connector
Copy link

chatgpt-codex-connector bot commented Jan 2, 2026

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@steipete
Copy link
Contributor

steipete commented Jan 3, 2026

🦞 Codex Review

Findings

  • ⚠️ Medium: No request timeout/abort; a stalled ATLAS call can hang the agent tool indefinitely. Recommend AbortSignal.timeout/AbortController with a default (match gateway 10s). (src/agents/atlas-tool.ts:71)
  • ℹ️ Low: ATLAS_URL not trimmed/normalized; trailing slash/whitespace yields //api/... or invalid URL. Normalize once (trim + strip trailing /).
  • ℹ️ Low: limit not sanitized; NaN/negative/float flows into query/body. Clamp + floor like other gateway option parsing.

Open Questions

  • Do ATLAS endpoints accept limit on /api/actions and /api/search/insights? Guide lists bare endpoints.

Summary
Adds atlas_query tool, registers it in createClawdisTools, plus new skill and bridge guide.

Review by Clawd 🦞 via Codex

@steipete
Copy link
Contributor

steipete commented Jan 3, 2026 •
edited
Loading

Thanks Rudlord! Not quite sure about this yet, need to spend more time researching atlas. Something local like the QMD system we already have would be nicer, or sth that can extend clawdis via hooks so this is user-addable.

pi has a great plugin system, might steal from that.

@steipete
Copy link
Contributor

steipete commented Jan 3, 2026

Wait I can't even sign up for this service? only book a call?

@steipete steipete closed this Jan 4, 2026
@steipete
Copy link
Contributor

steipete commented Jan 4, 2026

Thank you! This is better served as skill + cli for https://clawdhub.com/

@steipete steipete added the r: skill Clawdhub skill catalog label Jan 4, 2026
dgarson referenced this pull request in dgarson/clawdbot Feb 7, 2026
@dgarson
Merge pull request #114 from dgarson/feature/meridia-pluggable-backend
e774a24 
feat(meridia): pluggable DB backend interface (M2.5)
slathrop referenced this pull request in slathrop/openclaw-js Feb 11, 2026
@slathrop
docs(12-09): complete QMD remaining commits plan
576d5db 
Tasks completed: 2/2
- Task 1: Port commits #87 and #88 (cache eviction + SQLITE_BUSY regression test)
- Task 2: Port commits #114 and #149 (scope warning + model cache reuse)

SUMMARY: .planning/phases/12-memory-qmd-hardening/12-09-SUMMARY.md
slathrop referenced this pull request in slathrop/openclaw-js Feb 11, 2026
@slathrop
docs(16-10): complete cron flat params recovery + schedule fix plan
d12fc02 
Tasks completed: 1/1
- Port cron flat params recovery + schedule fix (commit #114, CRON-03)

SUMMARY: .planning/phases/16-gateway-cron-ios/16-10-SUMMARY.md
@gabrielbernal
Copy link

gabrielbernal commented Mar 3, 2026

Valid concern in theory. In practice it's a non-issue:

  1. Fallback is valid and proven — openai/gpt-5.2 is configured with a working API key and has 21/21 success rate in production today.

  2. Same end result with invalid fallbacks — with or without the fix, an invalid fallback model fails identically:

    • OLD: rate_limit → rotate 3 profiles (all rate limited, ~25s) → FailoverError → model-fallback → invalid fallback → fail
    • NEW: rate_limit → FailoverError → model-fallback → invalid fallback → fail

  3. Profile rotation was not helping — production logs confirm all 3-4 rotations returned rate_limit before fallback triggered. Rate limits are per-org on Anthropic, not per-API-key.

The only scenario where rotation would help is if a profile maps to a different org with separate rate limits. This is a niche config better served by the model-fallback chain (which already tries different providers).

@Peleke Peleke mentioned this pull request Mar 8, 2026
Open
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

r: skill Clawdhub skill catalog

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@chipoto69 @steipete @gabrielbernal