
Show HN: Qitt – An agent that triages my Slack and Jira and drafts my replies
A proactive chief of staff that lives inside T3 Code.
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
A proactive chief of staff that lives inside T3 Code.
docs/architecture.md describes each part and how a request travels through them. Planned, not in this repo yet: an interval supervision pass and a JQL backstop.
Path What
agents/ The two agents qitt is made of, qitt and worker. For each, a charter (AGENTS.md) with the rules that hold for every source, and .claude/settings.json (for qitt a 150k auto-compact window: every call re-reads the whole thread, and its durable state lives in the threads, not its context).
input-sources/ One folder per input source, a place requests come from: its charter sections, its webhook task's prompt, the send tools to deny, and a bridge if it needs one. slack/ and jira/ ship here; _template/ is a skeleton for your own.
bin/ install-agents assembles each agent's T3 project root from its charter, the enabled sources and your local context.md (re-run it after editing any of them); qitt-filter and qitt-bridge keep the filter and the Slack bridge running; qitt-mute mutes Slack conversations for the bridge.
docs/ architecture.md: the parts and how a request travels. input-sources.md: what a source is made of and how to add one. setup.md: how the thread, intake tasks, and endpoint are wired, and every config key.
filter/ Path filter that exposes only the T3 webhook routes, with optional HMAC signature checks (bin/qitt-filter runs it). Shared by every source that calls a webhook.
config/example/ Placeholder versions of the local config files.
Dependencies
A T3 Code server, with the qitt and worker projects registered (see docs/setup.md).
Node.js 22.19 or later for the installer, the bridge and the filter.
What each source you enable needs:
Slack: a Slack app for the bridge, a Slack MCP server for the agents (reading Slack, saving drafts; its send tools are denied), and the slack skill.
JIRA: something that turns JIRA events into signed webhook calls, and the jira skill.
Skills and MCP servers come from your own agent setup, not from this repo. context.md names the ones workers use for evidence, documents and ticket playbooks.
Local data
The repo holds code and generic templates only. Everything specific to a workplace or a person (names, timezone, people, Slack and JIRA IDs, hostnames, tokens) stays on the machine and is never committed:
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。