Managing Wakers

Create and configure Wakers, manage the Waker list, detail-page configuration items, project context, and permission settings.

This chapter explains how to create and configure Wakers.

3.1 Waker management list

Entry point: Left navigation sidebar → “Waker Management”.

The page displays Waker cards showing name, description, runtime environment, online status, and task entry points.

You can switch between “My Wakers / My Groups” and filter by status, environment, or name. If no results appear, clear the filter conditions first.

Card entry	Purpose	Post-action check
Create chat task	Immediately start a new conversation with this Waker	Chat header shows the target Waker
Create automated task	Configure a background task for this Waker	Enters the automated task creation page with the correct target Waker
Click card body	Open Waker details	Configuration menu appears on the left
More actions	Share or delete	Confirm dependencies and impact before proceeding

Before starting a task, confirm the local/remote indicator and online status. Do not rely solely on the name to determine where execution takes place.

3.2 Creating a Waker

When creating a Waker, select a role template and fill in basic information. Projects, skills, and connectors can be configured after creation.

3.2.1 Creating with a preset role template

Entry point: Waker Management → “New Waker” button in the top-right corner.

Steps:

1. Select the template closest to the target responsibilities.
2. Fill in the name, avatar, and description. The description should clearly state responsibilities, inputs, outputs, and boundaries.
3. When the page displays the runtime environment, select a device that has the required projects and dependencies.
4. Click “Save and Enable”.

Completion criteria:

• The new Waker appears in the management list with correct name, description, and runtime environment.
• The configuration menu is visible after entering the detail page.

Templates may include default capabilities. After creation, enter the detail page to review and supplement the configuration.

3.2.2 Creating a custom role template

Use case: Preset roles do not match long-term responsibilities, and you need to save a reusable role configuration.

Entry point: “New Waker” dialog → “Custom Role”.

Steps:

1. Fill in the role name, description, and avatar.
2. Configure core responsibilities (IDENTITY.md), work style (PERSONA.md), and work guidelines (BIBLE.md).
3. Optionally select Skills or MCP services. Credentials should only be configured through the secure authorization entry.
4. Save the template, return to the role list, select that template, and then create the Waker.

Completion criteria: The custom template appears in the role list. Wakers created from it inherit the role context and selected capabilities. Modifying the template does not automatically update existing Wakers.

3.3 Viewing Waker details and selecting configuration items

Entry point: Waker Management → click the target Waker card.

First confirm the page displays the target Waker, then select the left-side menu based on the operation you want to perform:

Configuration item	What you accomplish here	Post-completion check
Home	View running status; modify name, avatar, and description	Home page matches the management list information
Projects	Create or select reusable work contexts	Target project is selectable; work path and runtime device are correct
Automated tasks	Create or manage scheduled, event-driven, and API-triggered tasks	Workspace, trigger method, and enabled state are correct
Chat tasks	View message history, execution process, and artifacts; continue or start new sessions	Waker, work directory, and task content are correct
Workflows	View WakerFlows this Waker participates in and their run records	Target workflow, run status, and returned results are correct
Memory	View or edit Waker profile, project memory, and versions	After starting a new conversation, memory takes effect as expected
Skills	Install or manage Skills related to the Waker’s responsibilities	After starting a new conversation, target capabilities are available
Connectors	Add and authorize applications or MCP services	Connection status is normal; verify reads first, then open writes as needed
IM	View channels and sessions managed by this Waker	Channel, session target, status, and responding Waker are correct
Permissions	Configure tool, file, built-in tool, and model security scopes	Regular tasks can execute; out-of-scope or high-risk operations are blocked or require confirmation

IM channel creation, pairing approval, and global configuration are done in the main navigation under “IM”. IM messages may come from real business groups or external users. Configure the responding Waker, model, work directory, and permissions with minimum scope, and verify in a test session first.

3.4 Viewing status and maintaining basic information

1. Go to Waker details → “Home” and verify the name, ID, local/remote indicator, and online status.
2. Click “Edit” to modify the name, avatar, or description. The description should clearly state responsibilities, inputs, outputs, and boundaries.
3. After saving, return to the home page and management list to confirm the display has been updated.

Completion criteria: The page shows the target Waker, the status matches the actual environment, and changes have been saved.

Before sharing or deleting, check for private projects, automated tasks, connectors, as well as workflow, group, and IM references. Before deleting, first pause any external triggers.

3.5 Configuring reusable work contexts

Projects are used to save reusable work contexts. “Public projects” can be used by multiple Wakers. Private projects within Waker details are only available to the current Waker.

Scope	Creation entry point
Reused by multiple Wakers	Main navigation “Public Projects” → “Create Public Project”
Current Waker only	Target Waker details → “Projects”, create or select a private project

1. Choose the public project or private project entry based on the intended scope.
2. Fill in the name and description, and add the work path.
3. Confirm the device and environment are correct, save, and select the project in the target Waker.

Completion criteria: Public projects appear in the public project list; private projects appear on the target Waker’s “Projects” page. Both can be found in the workspace selector of the corresponding Waker or Chat.

When using a project, select or create it in Waker details → “Projects”. When starting a task, select the project again and verify the path with a read-only task first. Creating a project does not automatically apply it to subsequent tasks.

3.6 Configuring permissions

Entry point: Waker details → “Permissions”.

The permissions page currently includes:

• Tool Guard
• File Guard
• Built-in Tools
• Model Security

Recommended configuration order:

1. First clarify the Waker’s responsibilities and the operations it must perform.
2. In File Guard, only open the directory scope required by tasks.
3. In Tool Guard and Built-in Tools, only keep the necessary tools.
4. In Model Security, configure the available scope per organizational requirements.
5. After saving, run a read-only test task.
6. Then run an operation that requires authorization to confirm that high-risk actions are blocked or prompt for user confirmation.

Completion criteria: Tasks within the normal authorization scope can be completed. Out-of-scope access, high-risk tools, or restricted operations are blocked or require confirmation per the configured rules.

Production directories, sensitive data, and external write operations should follow the principle of least privilege. When a task fails, do not disable all guards first. Instead, based on the failure message, add only the minimum permissions needed to complete the task.