Changelog

You can now connect X (Twitter) as an event source and trigger agent workflows from real-time events.

What's new

• X webhook integration in the integrations catalog. Provide your X app credentials (Bearer Token + Consumer Secret) and Orqestr registers a per-connection webhook automatically.
• Event triggers for X — create triggers for tweet events, follows, DMs, favorites, and more. Use filters to narrow which events create tasks.
• Per-connection CRC validation — each connection handles X's challenge-response checks independently using its own credentials.

How it works

1. Add the X integration from the Integrations page
2. Enter your X app Bearer Token and Consumer Secret
3. Create an Event Trigger under Tasks > Triggers and select your X connection
4. Pick the events you care about (tweets, follows, DMs) or enter a custom event type
5. Matching events automatically create tasks and route them to the right agent

After months of building, testing, and iterating with early users — Orqestr is now publicly available.

What's in 1.0

• Full agent orchestration — define specialized agents, connect them to tools, and let the orchestrator assign, sequence, and coordinate work across your team.
• 2,500+ integrations — MCP servers, managed app connections, native connectors. Your agents work with the tools you already use.
• Approval workflows — review agent output before it goes live. Approve, request changes, or cancel from the task board.
• Schedules and event triggers — automate work on a cron or in response to webhooks from GitHub, X, and any service.
• Knowledge system — project docs and task artifacts that agents read, write, and share automatically across workflows.
• MCP OAuth auto-detection — custom MCP servers with standard OAuth support are detected and connected automatically. No catalog entry needed.

Also shipping with 1.0

• Billing and plans — Free, Starter, Builder, Pro, and Enterprise tiers with metered AI usage and overage billing.
• Team workspaces — invite members, assign roles, and manage access across projects.
• API access — create API keys and trigger tasks programmatically via the external API.
• Activity log — every event across your projects is recorded and visible in the Activity page.

What's next

We're shipping weekly. Expect deeper integration support, more agent tools, and collaboration improvements in the coming weeks.

Agents can now build on each other's work. The knowledge system gives agents persistent context that flows across tasks and collaborations.

Two types of knowledge

• Project knowledge — long-living documents scoped to the entire project. Create markdown or text docs that are automatically injected into agent runs as context. Control which agents see which docs via access modes.
• Task artifacts — short-living outputs attached to a task tree. When an agent writes an artifact, every other agent working on sibling or child tasks receives it automatically.

Agent tools

• write_artifact — agents write artifacts during execution. A spec agent writes a spec, and the dev agent receives it when implementing.
• promote_to_project_knowledge — when an artifact is valuable beyond the current task, agents can promote it to project-wide knowledge. The original stays in the task tree; a copy becomes permanent project context.

Knowledge page

A new "Knowledge" section in the sidebar with two tabs: Project Knowledge (CRUD for docs) and Task Artifacts (timeline view grouped by task tree, with agent attribution and markdown rendering).