Publish expert projects as StaffCreate persistent, resumable instances

Turn expert workflows into reusable AI Staff.

CurvePulse is more than another chat interface. Publish proven Claude Code and Codex projects with their skills as Staff templates for your team. Every launch creates a member-isolated, persistent project instance; leave at any time and return to the same context.

Publish projects and skills togetherMember runtimes stay isolatedWorkspaces and conversations persist
Onboarding flowFrom onboarding brief to reviewable result
  1. Onboarding brief

    Turn this week's work notes into a concise weekly report.

  2. They're working in a dedicated workspace. You can close this page without interrupting them; return at any time to check their status.

  3. Result for review

    Weekly report draft

    • Completed work
    • Work in progress
    • Decisions needed
You write the onboarding brief, they work in their own workspace, and you review the structured result.
Skill examples

Different skills, different results

These are examples. Your admin configures the skills available on your organization's servers. Pick one or more and write an onboarding brief; they start work right away.

Community operations
Onboarding brief

“Identify the community posts that warrant a reply this week.”

Result
Draft reply set

Highlights the relevant posts and prepares a draft reply for each, ready for your review.

Code review
Onboarding brief

“Review this code change and flag material issues.”

Result
Review findings

Identifies each issue, where it appears, and why it matters.

Weekly report
Onboarding brief

“Turn this week's work notes into a concise weekly report.”

Result
Weekly report draft

Organizes completed work, current progress, and decisions that need your attention.

Isolation boundary

Member isolation, staff partitioning

Members use separate runtimes, sign-in configurations, and persistent directories; Admins and Owners retain maintenance access.

When one member has several staff on duty, each staff member keeps a separate project directory and conversation context for independent pause and resume.

Staff member 1
Separate project directorySeparate conversation context
Staff member 2
Separate project directorySeparate conversation context
Staff member 3
Separate project directorySeparate conversation context

Members use separate runtimes. A single member's staff are partitioned by project and conversation, but are not a security boundary against that member's terminal access.

Status transparency

Clear status, without false certainty

Most products emphasize what they can do.
We make the limits equally clear: when something goes wrong, you can see whether they stopped working or only the connection was interrupted.

“Stopped, please review the result.”

The system reports that they have stopped; it does not determine that the work is done. Only you can decide whether the result is good enough.

“Disconnected, reconnecting (they're still working)”

A lost connection does not mean they stopped working. The interface keeps the two states distinct.

The same standard applies in administration: if a staff member is not using the identity configured for them, the interface flags the mismatch instead of displaying the intended state.

Pick the skills. Hire someone.

Your admin publishes the skills available on your organization's servers. Pick one or more and write an onboarding brief; CurvePulse creates a separate project and conversation context for them, and you can return at any time to check their status and result.

CurvePulse