Manage Wakers

Open any Waker’s detail page to view and adjust everything about that Waker: check how it’s running, bind the projects it works on, manage memory, skills, and connectors, and set its permission boundaries.

​

Overview

​

Memory

Each Waker maintains its own long-term memory, accumulating knowledge about you and the project over time. Memory comes from three sources:

• Auto-capture — information the Waker considers worth remembering is written during conversations.
• Manual edits — open the Memory page and add or edit entries directly.
• System cleanup — the system periodically organizes and deduplicates entries on the Waker’s behalf.

Go to Waker details → Memory to browse, search, and edit all memory entries.

​

Skills

Skills are specialized capability packages the Waker can invoke during conversations or triggered tasks.

• Skill Marketplace — install from the official Qoder Skills Marketplace.
• Upload a Skill — import custom skill packages from your local machine.
• Built-in skills — included by default and cannot be uninstalled.

Go to Waker details → Skills to view installed skills, browse the marketplace, or upload your own.

​

Connectors

Connectors are bridges between the Waker and external tools or services, such as GitHub, Jira, and GitLab. Go to Waker details → Connectors to add connectors manually.

​

Projects

Projects define the workspace the Waker operates in. Go to Waker details → Projects to:

• Bind local directories or Git repositories.
• Add multiple sources to a single project (multiple directories or repositories).
• Use project-level memory, kept separate from the Waker’s personal memory.

​

Permissions

Permissions control exactly what a Waker can and cannot do. Go to Waker details → Permissions, which covers two main areas plus built-in tool policies. Tool protection validates tool parameters against built-in security rules and triggers an approval request when a high-risk action is detected. Rule categories include:

• Command injection — detects destructive operations like rm, mv.
• Resource abuse — detects fork bombs, system restarts, and similar.
• Code execution — detects remote-execution patterns like curl | bash.
• Network abuse — detects reverse shells, localhost tunneling.
• Sensitive file access — detects access to critical system files.
• Privilege escalation — detects sudo and similar operations.

File protection controls the Waker’s read and write access to local files. Built-in tools lets you set allow / ask / disable policies per built-in tool available to the Waker.