wdevs/amcs
5
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Create a practical OpenClaw integration package for AMCS #5

New Issue
Open
opened 2026-04-01 19:44:57 +00:00 by sam · 3 comments
sam commented 2026-04-01 19:44:57 +00:00
Member
Copy Link

Summary

Create a practical OpenClaw integration package for AMCS so OpenClaw agents can use AMCS consistently as structured memory and project context without drifting into stale instructions or ad-hoc usage.

Why

This issue is still valid, but parts of the original idea are already present inside AMCS itself:

  • describe_tools exposes the live tool list
  • annotate_tool persists usage notes
  • project skills/guardrails already exist
  • llm/memory.md already documents a project startup flow

So this issue should now focus on the OpenClaw-side integration work, not on re-planning features AMCS already has.

Recommended scope

1. OpenClaw skill/package for AMCS usage

Create one or more OpenClaw-facing skills or instruction packages that teach agents to:

  • prefer AMCS when durable structured memory is appropriate
  • use project tools early in project-scoped work
  • load project context / skills / guardrails before implementation
  • use domain-specific AMCS tools when available instead of stuffing everything into generic notes

2. Practical startup pattern for AMCS-backed projects

Standardize an OpenClaw-side project startup pattern such as:

  1. identify or set project
  2. call describe_tools
  3. load project context
  4. load project skills
  5. load project guardrails
  6. then plan or implement

3. Storage-boundary guidance

Document when OpenClaw should prefer:

  • local workspace memory
  • AMCS thoughts
  • AMCS structured domain tools
  • AMCS skills/guardrails

4. Lightweight sync/check support

If needed, add a small helper or maintenance step for OpenClaw skill authors so AMCS guidance can be refreshed against the live AMCS tool list.

Out of scope

  • redesigning AMCS tool discovery from scratch
  • duplicating functionality that describe_tools and annotate_tool already provide
  • solving every integration surface beyond OpenClaw

Acceptance criteria

  • At least one OpenClaw-facing AMCS skill/package exists
  • There is a documented AMCS project startup flow for OpenClaw agents
  • Guidance clearly separates local memory vs AMCS thoughts vs structured AMCS tools
  • The integration uses the live AMCS tool surface instead of assuming a frozen tool list
  • The resulting guidance is small and maintainable

Notes

This issue now intentionally overlaps less with the old discovery/sync ticket, because the core runtime discovery problem is already largely addressed inside AMCS.

## Summary Create a practical OpenClaw integration package for AMCS so OpenClaw agents can use AMCS consistently as structured memory and project context without drifting into stale instructions or ad-hoc usage. ## Why This issue is still valid, but parts of the original idea are already present inside AMCS itself: - `describe_tools` exposes the live tool list - `annotate_tool` persists usage notes - project skills/guardrails already exist - `llm/memory.md` already documents a project startup flow So this issue should now focus on the **OpenClaw-side integration work**, not on re-planning features AMCS already has. ## Recommended scope ### 1. OpenClaw skill/package for AMCS usage Create one or more OpenClaw-facing skills or instruction packages that teach agents to: - prefer AMCS when durable structured memory is appropriate - use project tools early in project-scoped work - load project context / skills / guardrails before implementation - use domain-specific AMCS tools when available instead of stuffing everything into generic notes ### 2. Practical startup pattern for AMCS-backed projects Standardize an OpenClaw-side project startup pattern such as: 1. identify or set project 2. call `describe_tools` 3. load project context 4. load project skills 5. load project guardrails 6. then plan or implement ### 3. Storage-boundary guidance Document when OpenClaw should prefer: - local workspace memory - AMCS thoughts - AMCS structured domain tools - AMCS skills/guardrails ### 4. Lightweight sync/check support If needed, add a small helper or maintenance step for OpenClaw skill authors so AMCS guidance can be refreshed against the live AMCS tool list. ## Out of scope - redesigning AMCS tool discovery from scratch - duplicating functionality that `describe_tools` and `annotate_tool` already provide - solving every integration surface beyond OpenClaw ## Acceptance criteria - [ ] At least one OpenClaw-facing AMCS skill/package exists - [ ] There is a documented AMCS project startup flow for OpenClaw agents - [ ] Guidance clearly separates local memory vs AMCS thoughts vs structured AMCS tools - [ ] The integration uses the live AMCS tool surface instead of assuming a frozen tool list - [ ] The resulting guidance is small and maintainable ## Notes This issue now intentionally overlaps less with the old discovery/sync ticket, because the core runtime discovery problem is already largely addressed inside AMCS.
warkanum commented 2026-04-01 19:47:17 +00:00
Owner
Copy Link

If the project being worked on can be identified, try to fetch/add it and set it as the active project.

If the project being worked on can be identified, try to fetch/add it and set it as the active project.
warkanum commented 2026-04-01 19:47:57 +00:00
Owner
Copy Link

Another requirement is that we add sessions on all the tools to be able to be compatible with Openclaw sessions etc.

Another requirement is that we add sessions on all the tools to be able to be compatible with Openclaw sessions etc.
hein was assigned by warkanum 2026-04-01 19:48:13 +00:00
sam was assigned by warkanum 2026-04-01 19:48:13 +00:00
hein was unassigned by warkanum 2026-04-01 19:48:17 +00:00
warkanum self-assigned this 2026-04-01 19:48:17 +00:00
warkanum added the Kind/Enhancement
Priority
High
2
 labels 2026-04-01 19:49:22 +00:00
sam changed title from Plan better OpenClaw integration for AMCS with skill-driven and tool-aware workflows to Create a practical OpenClaw integration package for AMCS 2026-04-03 12:02:00 +00:00
warkanum commented 2026-04-11 22:04:03 +00:00
Owner
Copy Link

Not sure if we need to do anything on openclaw. Much better projects out there.
Might just build a few usable skills and make recommendations for your AGENTS.MD

Not sure if we need to do anything on openclaw. Much better projects out there. Might just build a few usable skills and make recommendations for your AGENTS.MD
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
debugging
integration
planned
ux
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label Kind/Enhancement
Priority
High
2
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hein root sam sgcommand warkanum
No Assignees sam warkanum
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wdevs/amcs#5
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?