FAQ
Agent Tick is intentionally narrow: it routes bounded approvals for local coding agents. It is not a remote shell, not permission skipping, and not a broad agent control plane.
Comparisons
Agent Tick is easiest to understand by comparing categories. The useful distinction is whether a remote surface can execute arbitrary work or only answer the bounded request created by a local agent.
Remote shells and remote-control tools move broad execution authority to another device. Agent Tick keeps execution in the Local Agent Interface and lets the remote surface approve, deny, or choose only from the response options the local agent supplied.
Permission skipping removes the review point so an agent can continue without waiting. Agent Tick preserves the review point and makes it reachable from a Native App or Personal Console, so the human still decides.
Generic HITL tools can model many business approvals. Agent Tick is narrower: it is built for coding-agent Status Updates, Steering choices, and Sanction requests from local developer workflows.
Hosted-only products can be convenient but may require trusting an opaque service boundary. Agent Tick is source-available and self-hostable, while hosted Agent Tick remains available for teams that prefer managed routing.
Use Agent Tick when a local coding agent needs to send a Status Update, ask a bounded Steering question, or request a Sanction for one specific action while you are away from the terminal. Agent Tick is for least-permission approvals, not broad remote control.
Yes. Agent Tick supports Self-Hosted Deployments. The Business Source License 1.1 Additional Use Grant permits any use except offering Agent Tick to third parties as a hosted or managed service, so internal commercial self-hosting is allowed. Direct license: https://github.com/self-deprecated/agent-tick/blob/main/LICENSE.
No. Agent Tick does not run commands on your machine. A local agent or CLI creates the bounded request and remains responsible for local execution. Agent Tick routes the human decision and returns only the allowed response.
The technically correct phrase is source-available. Agent Tick uses the Business Source License 1.1. The LICENSE file states Change Date 2028-05-31, Change License Apache License, Version 2.0, and an Additional Use Grant permitting any use except offering Agent Tick to third parties as a hosted or managed service. Direct license: https://github.com/self-deprecated/agent-tick/blob/main/LICENSE.
A remote shell or remote-control app lets another device operate the environment directly. Agent Tick does not expose a terminal or arbitrary prompt channel. The Native App and Personal Console can only answer the bounded request that the Local Agent Interface already created.
Skipping permissions removes a safety stop. Agent Tick keeps the stop and makes it easier to answer from a phone or browser. Denying a Sanction tells the local agent not to run that requested action.
Agent Tick is not a general workflow-approval suite. It focuses on local coding-agent workflows: Status Updates, Steering choices, and Sanction requests with bounded responses that preserve the local execution boundary.
Hosted Agent Tick sells convenience: managed routing, push delivery, auth setup, updates, backups, monitoring, and uptime. Self-hosting is available for operators who want control and are willing to run the service themselves.
No. The mobile app cannot invent a new command or prompt. It can approve, deny, or select from the options that the local agent supplied in the original Agent Tick request.
The denial returns to the Local Agent Interface. For a Sanction, the requested action should not run, and the local agent must stop or choose a safer path.
No. Shared Workspace hosted plans use simple flat tiers. Agent Tick routes bounded agent activity; the pricing should stay predictable instead of turning every member into a metered seat.
Agent Tick is built by Self-Deprecated ApS. It is a practical developer tool built for real local coding-agent workflows where bounded approval is safer than remote control or silent permission bypasses.
