GeniusTasker agent tools

Keep project progress, collaborators and your own AI agents in one place. This repository contains the public CLI, local MCP server and agent skills. The GeniusTasker application and service implementation are separate. Canonical repository: PulsarInteractive/geniustasker-agent-tools.

Install · Codex and Claude · CLI reference · OpenAI plugin · Releases

Install and connect

Requires Node.js 22.13+ and an account admitted to the development beta. Installing the client does not enable access to the service.

npm install -g @pulsarinteractive/geniustasker@beta
geniustasker auth login --context work
geniustasker projects list --context work --json

A browser opens: sign in, select projects and independent memories, choose permissions, then approve. The terminal finishes automatically. No token to copy. For Chrome use --browser chrome; remote shells can use --flow device --no-browser. Production agent access is not open in this beta.

Related MCP server: Coding Tools MCP

Connect an agent

After logging in with the work context:

codex mcp add geniustasker -- npx -y @pulsarinteractive/geniustasker@0.1.0-beta.4 mcp --context work

Other stdio MCP hosts can use examples/mcp.json. The published beta.3 MCP exposes 16 tools for identity, capabilities, projects, memories, bounded reads, profiles and journaled changes. It uses the session you explicitly approved. GeniusTasker records work; your agent chooses and executes its own workflow.

Skills

• GeniusTasker: project work, tickets and useful handoffs.

• GeniusTasker Memory: independent knowledge, focused reads, stable blocks and resumable imports.

Install the skill folders in your agent's supported skill directory, or use the plugin bundle described in Integrations. npm installation alone does not register skills or MCP servers in your agent host.

Plugin readiness

plugin.json, mcp.json, skills/ and the local marketplace catalog form a portable local plugin bundle. This is not an approved public ChatGPT-directory plugin. The hosted HTTPS MCP/OAuth integration remains a separate milestone in OpenAI integration.

Development

npm ci
npm run verify

Tests use synthetic fixtures and local mock servers. CI has no production credentials. npm run check checks the public file boundary, package contents and plugin schema. See Contributing, Architecture, Testing and Release process.

Privacy and source boundary

No application source, backend, account exports, infrastructure credentials or private product documents belong here. Only the agent client and its public interface contract are included. Credentials stay in the user's private local store; never paste them into an issue. See Security.

License

The CLI, MCP server, skills and documentation are available under the MIT license. See third-party notices for vendor components. The separately hosted GeniusTasker application and backend are not part of this repository.

Memory and Graph (next beta)

Memory stores structured documents independently of projects. Graph connects nodes and links them to a page or a stable document block. These commands require the matching deployed service capabilities; they are not in the published beta.3.

geniustasker memory search --scope memory:ID --query "release checklist" --json
geniustasker graph explore --scope memory:ID --center NODE_ID --depth 2 --json
geniustasker memory resolve --scope memory:ID --page PAGE_ID --block BLOCK_ID --json

The matching MCP tools are tasker_search, tasker_graph and tasker_reference. Search is paginated; Graph returns a bounded neighborhood and reports truncation. Use resources list for complete selected records and commands describe for contract-derived node/edge write fields. Writes keep the same immutable journal.

References recheck current access. If a friend withdraws access, the content becomes unavailable while the node and its own text remain intact. A new grant restores resolution; a link never grants access by itself. The client does not cache resolved content. Discover capabilities before selecting a workflow.

Private attachments (next beta)

Discover mediaUploadAvailable and maxUploadBytes first. Prepare one explicitly selected file with media prepare --scope memory:ID --epoch EPOCH --file diagram.png --content-type image/png, then media upload --operation UUID. Keep that operation ID after a timeout: retries verify the same bytes and do not create a second file. Use the returned assetId in an image or attachment block. Images, PDF and plain text are supported up to 15 MB; storage is charged to the Memory owner.

MCP equivalents are tasker_media_prepare, tasker_media_upload, tasker_media_action and tasker_media_download. Downloads require an explicit new local path and fresh read access. Removal leaves document blocks in place so people can see and repair the unavailable attachment. No credentials, URLs with public access tokens or file bytes are embedded in documents.